Connect to and consume Azure services and third-party services →mediumMultiple ChoiceObjective-mapped
AZ-204 Practice Question: Connect to and consume Azure services and third-party services
An app uses Azure Event Grid to publish events. The events must be delivered to an Azure Function that processes them. Which Event Grid event delivery model should be used?
⚠ Common exam trap
Watch out — candidates often confuse Event Grid's push model with the pull-based consumption patterns of other Azure messaging services (like Event Hubs or Service Bus), leading them to incorrectly select pull or poll delivery.
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
✓
Push delivery
Azure Event Grid uses a push delivery model to send events to subscribers like Azure Functions. When an event occurs, Event Grid automatically forwards (pushes) the event to the configured endpoint via HTTP POST requests. This ensures near-real-time processing without the subscriber needing to poll for new events.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Pull delivery
Why it's wrong here
Azure Event Grid does not utilize a pull delivery model. In a pull model, the subscriber actively initiates requests to the event source or broker to check for and retrieve new events. This approach is characteristic of services like Azure Event Hubs and Azure Service Bus queues or topics, where consumers manage their own consumption rate and state, making it suitable for high-throughput stream processing or message queuing scenarios. Event Grid's design prioritizes immediate notification rather than client-driven retrieval.
- ✓
Push delivery
Why this is correct
Azure Event Grid exclusively employs a push delivery model for event distribution. With push delivery, Event Grid automatically sends events to configured subscriber endpoints as soon as they occur, without the subscriber needing to initiate a request. This server-initiated approach is fundamental to Event Grid's real-time, reactive architecture, enabling immediate invocation of services like Azure Functions, Logic Apps, or webhooks in response to state changes or actions within Azure resources or custom applications.
- ✗
Batch delivery
Why it's wrong here
Batch delivery is not a standalone event delivery model but rather a configurable optimization within Event Grid's push delivery mechanism. It allows subscribers to receive multiple events in a single payload, up to a specified maximum number of events or total payload size. While batching can improve efficiency by reducing the number of network requests and overhead for the subscriber, it remains an aspect of how events are pushed, not an alternative to the push model itself.
- ✗
Poll delivery
Why it's wrong here
Poll delivery, characterized by a subscriber periodically checking an endpoint for new events, is not a native or recommended delivery model for Azure Event Grid. While a subscriber could theoretically implement polling against a custom endpoint that itself receives Event Grid events, Event Grid's core design is to actively push events to subscribers. Polling introduces latency and inefficiency compared to Event Grid's immediate, event-driven push notifications, which are designed for near real-time responsiveness.
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
Azure Event Grid
Azure Event Grid is a fully managed event routing service that allows applications and services to react to events in real time using a publish-subscribe model.
About these practice questions
This AZ-204 question is part of Courseiva's 881-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.