nerdexam
Microsoft

AZ-305 · Question #45

Drag and Drop Question Your company designs an application based on the Azure microservices architecture that will: - Receive up to thousands of events per second from environmental sensors…

The correct answer is Azure Event Hub; Azure Event Hub; Azure Function. Azure Event Hub is the correct choice for both ingesting the high-volume sensor events (receiving thousands of events per second) and for submitting events in real-time for formatting/pre-processing, as it is purpose-built for big data streaming and telemetry ingestion with…

Submitted by jakub_pl· Mar 6, 2026Design Data Storage Solutions / Design Event-Driven and Messaging Solutions in Azure Architecture

Question

Drag and Drop Question Your company designs an application based on the Azure microservices architecture that will: - Receive up to thousands of events per second from environmental sensors. - Submit events in real-time for formatting and pre-processing. - Ignore missed or improperly formatted data without interrupting the stream. - Write formatted event data to a Cosmos DB database. The number of events per second can vary widely. You need to determine which Azure services are necessary to support the solution. You want to keep costs to a minimum. Which Azure services should you include? To answer, drag the appropriate services to the correct answer areas. Each service may be used once, more than once, or not at all. Answer:

Exhibit

AZ-305 question #45 exhibit

Answer Area

Drag items

Azure Event HubAzure FunctionAzure Event GridAzure Logic AppAzure Notification HubAzure Service Bus

Correct arrangement

  • Azure Event Hub
  • Azure Event Hub
  • Azure Function

Explanation

Azure Event Hub is the correct choice for both ingesting the high-volume sensor events (receiving thousands of events per second) and for submitting events in real-time for formatting/pre-processing, as it is purpose-built for big data streaming and telemetry ingestion with high throughput and low latency. Azure Functions is the correct serverless compute option for formatting and pre-processing the event data because it scales automatically with variable event loads (minimizing costs by only charging for executions), can be triggered directly by Event Hub, and can gracefully handle/ignore malformed data without interrupting the stream before writing to Cosmos DB. This combination - Event Hub → Event Hub (stream processing trigger) → Azure Function → Cosmos DB - provides a cost-effective, scalable microservices pipeline.

Topics

#Azure Event Hub#Azure Functions#Microservices Architecture#Event-Driven Design

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full AZ-305 Practice