AI-200 Event Driven Integration Practice Question
You are designing an event-driven AI document processing pipeline. Incoming PDF documents are uploaded to Azure Blob Storage, triggering an Event Grid event. The event triggers an Azure Function that downloads the PDF, processes it with Azure AI Document Intelligence, and saves results to Azure Cosmos DB. Under high load, duplicate events are occasionally received by the function, causing duplicate Cosmos DB records. How should you design the Azure Function to handle idempotency?
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
✓
Implement idempotency in the Azure Function by checking if the document record already exists in Cosmos DB or using an upsert operation with a deterministic ID.
Because event-driven architectures guarantee 'at-least-once' delivery, consumers must be idempotent. The Azure Function should check if the document ID or event ID already exists in Cosmos DB before processing or use an upsert operation.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Implement idempotency in the Azure Function by checking if the document record already exists in Cosmos DB or using an upsert operation with a deterministic ID.
Why this is correct
Upsert operations or existence checks ensure that processing the same event multiple times yields the exact same state without duplication.
- ✗
Set the Event Grid retry count to zero.
Why it's wrong here
Setting retries to zero drops failed events entirely on transient errors, which risks data loss.
- ✗
Deploy an Azure Service Bus queue in front of Blob Storage to serialize all requests into a single partition.
Why it's wrong here
While this serializes processing, it does not prevent duplicate event emissions from Blob Storage or guarantee idempotency.
- ✗
Configure Event Grid delivery mode to 'Exactly-Once' in the subscription settings.
Why it's wrong here
Event Grid provides 'At-Least-Once' delivery semantics; exactly-once delivery across distributed webhooks is not a native protocol feature.
Quick reference
Azure Blob Storage Tier Comparison
| Tier | Storage Cost | Retrieval Cost | Latency | Use Case |
|---|---|---|---|---|
| Hot | Highest | Lowest | Immediate | Active data, frequent reads |
| Cool | Lower | Higher | Immediate | Data accessed < once / month |
| Cold | Lower still | Higher | Immediate | Data accessed < once / quarter |
| Archive | Lowest | Highest + rehydration delay | Hours | Long-term compliance retention |
About these practice questions
This AI-200 question is part of Courseiva's 503-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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed August 2026 · checked against the official Microsoft exam blueprint
This AI-200 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 AI-200 exam.