Q31-Q35

Q31. What is Azure service bus?

Q32. What are Azure Durable functions?

Q33. What are azure orchestrator functions?

Q34. What are the various Azure services you have used in your project?

Q35. What is the difference between triggers and binders in azure functions?

------------------------------------------------------------------------------------------------------------------------------

Q31. What is Azure service bus?

Answer:

Azure Service bus is of two types 

1) Azure Service bus Message Queues and

2) Azure Service Bus Topics

Message Queues:

>> Supports FiFo, Duplication detection, Long Pooling service

Topics:

>> Pub/Sub model

------------------------------------------------------------------------------------------------------------------------------

Q32. What are Azure Durable functions?

Answer:

Azure Durable Functions is an extension of Azure Functions that allows you to write stateful functions in a serverless compute environment. This means you can define workflows that maintain their state even after the function execution is paused or restarted

Key Features:

1. Orchestrator Functions: These functions define the workflows using code. They can call other functions, wait for their results, and manage the state of the workflows. Can be used for Function Chaining

2. Stateful Entities: These are functions that manage state explicitly, allowing you to build applications that require stateful interactions

3. Patterns: Supports various application patterns such as function chaining, fan-out/fan-in, async HTTP APIs, monitoring, human interaction, and aggregators1

------------------------------------------------------------------------------------------------------------------------------

Q33. What are azure orchestrator functions?

Answer:

Azure Durable Functions. 

------------------------------------------------------------------------------------------------------------------------------

Q34. What are the various Azure services you have used in your project?

Answer:

Now, during an interview, you can answer with this neat flow:

1. Hosting/Compute → Where apps live.
2. API Management & Integration Services → How apps talk to each other.
3. Networking/Delivery → How users reach apps.
4. Storage → Where data lives.
5. Security → How apps & users are secured.
6. Monitoring → How we track and improve.

1. Application Hosting & Compute

App Service

• Azure Web Apps – Hosting web applications.
• Azure Logic Apps – Workflow automation and integration.
• Azure Functions – Serverless compute for event-driven task

IAAS Solutions

• ARM Templates – Infrastructure as code.
• Docker Images – Containerized application packaging.
• ACI, Azure Container Instances – Lightweight container hosting.
• ACR, Azure Container Registry – Container image storage and management.
• AKS, Azure Kubernetes services.

2. API Management & Integration Services.

 API Management

• API Gateways – Authentication, policies, rate limiting, throttling for APIs.

Integration Services

• Azure Event Grid – Event routing service.
• Azure Event Hubs – Big data streaming platform. Event Ingestion service.
• Azure Service Bus – Enterprise messaging with topics and queues.
• Azure Queue Storage – Simple queue-based messaging.
• Azure Notification Hubs – Push notifications to mobile devices. 

3.     Networking & Deliver
Azure CDN (Content Delivery Network) – Caching and global content delivery.
 WAF
Azure Redis Cache – In-memory data store for fast access.
Azure Front Door – Global load balancing and web application firewall.

 4.     Storage Solutions
o   Disk Storage – Managed disks for VMs.
o   Cosmos DB – Globally distributed NoSQL database.
·       Azure Storage
o   Blob Storage (unstructured data, images, video)
o   File Storage (SMB-based file shares)
o   Table Storage (key-value store)
o   Queue Storage (simple message queue)

5.     Security
o   AAD, Entra ID, Azure Active Directory (SSO, MFA)
o   OAuth2 Authentication
o   Shared Access Signature (SAS), limited access to storage blob etc
o   RBAC (Role-Based Access Control)
o   Key Vault – Secure storage for secrets, keys, and certificates.
o   Azure Managed Identities.

6.     Monitoring & Diagnostics

o   Application Insights – Application performance monitoring.
o   Azure Monitor – Infrastructure and resource monitoring.
 

 

------------------------------------------------------------------------------------------------------------------------------

Q35. What is the difference between triggers and binders in azure functions?

Answer:

In Azure Functions, triggers and bindings are concepts that help define how functions are invoked and how they interact with other services.

Triggers:

- Defines how a function is invoked. HTTP triggers, Timer triggers, Blob Storage triggers, Queue Storage triggers, Event Grid triggers

Bindings:

- They can be used to pass data into the function (input bindings) or to send data from the function (output bindings).

- Example: An input binding can read data from a storage account and pass it to the function. An output binding can write data to a storage account after the function processes it.

------------------------------------------------------------------------------------------------------------------------------