AZ-204 Practice Question: Connect to and consume Azure services and third-party services
A system receives high-volume event notifications from Azure resources and routes them to serverless handlers. Events are lightweight and should use native event routing. Which service should be used? The design must avoid adding custom operational scripts.
⚠ Common exam trap
Test-takers frequently confuse Azure Event Grid with Azure Service Bus, but Event Grid is designed for reactive event routing (push model) with no need for polling or custom scripts, whereas Service Bus is for message queuing with explicit consumer processing.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Azure Event Grid
Azure Event Grid is a fully managed event routing service that uses a publish-subscribe model to deliver lightweight, high-volume events from Azure resources to registered handlers like Azure Functions or webhooks. It supports native event routing without requiring custom polling scripts or infrastructure, making it ideal for serverless event-driven architectures.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Azure DNS
Why it's wrong here
Azure DNS is a hosting service for DNS domains, providing name resolution using Azure infrastructure. Its primary function is to translate human-readable domain names into IP addresses, enabling clients to locate network resources. It is fundamentally a networking service for managing DNS records, not an event-driven architecture component designed to ingest, filter, or route application-level event notifications from Azure services. Therefore, it cannot be used for high-volume event routing.
- ✓
Azure Event Grid
Why this is correct
Azure Event Grid is a highly scalable, fully managed event routing service that enables reactive programming by delivering events from various sources to different handlers. It operates on a publish-subscribe model, allowing applications to subscribe to specific event types from Azure services like Storage Accounts, Resource Groups, or custom topics. Its design specifically caters to high-volume event notifications, providing low-latency delivery and robust filtering capabilities, making it ideal for scenarios requiring immediate processing of discrete events.
- ✗
Azure Files
Why it's wrong here
Azure Files offers fully managed file shares in the cloud, accessible via the Server Message Block (SMB) protocol, Network File System (NFS) protocol, and REST API. It functions as a cloud-based file system, primarily used for storing and sharing files, migrating on-premises file servers, or providing application data storage. It lacks any inherent capabilities for event ingestion, filtering, or routing, making it entirely unsuitable for handling high-volume event notifications.
- ✗
Azure Service Bus queue
Why it's wrong here
Azure Service Bus queues are designed for reliable, asynchronous enterprise messaging, facilitating communication between decoupled applications. They excel in scenarios requiring ordered delivery, duplicate detection, message deferral, and transactional processing, often used for commands or data payloads that require guaranteed delivery and complex workflow orchestration. While it can handle messages, it is generally less efficient and more expensive for simple, high-volume, fire-and-forget event notifications compared to Event Grid, which is optimized for reactive event distribution.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
Learn chapter
Azure Functions Development
Key term
Azure Functions Bindings
Azure Functions Bindings are declarative connections that link your serverless function code to Azure services or external resources, handling input and output data automatically without writing extra networking or authentication code.
Key term
Durable Functions
Durable Functions is an extension of Azure Functions that lets you write stateful workflows in code, managing complex sequences of tasks, retries, and delays automatically.
About these practice questions
Courseiva writes every AZ-204 question from scratch — 881 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This AZ-204 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-204 exam.