AI-200 Event Driven Integration Practice Question
You are designing an asynchronous AI inference processing pipeline using Azure Service Bus Premium. Messages contain large payloads exceeding the standard Service Bus message size limit of 256 KB. You need to store the large payload in Azure Blob Storage while passing a reference in the Service Bus message. Which feature should you implement?
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
✓
Use the Azure Service Bus Claim Check pattern by storing the payload in Azure Blob Storage and sending only the blob URI in the message body.
The Azure Service Bus Message Body Broker does not support large payloads natively beyond limits, but the Azure Service Bus client libraries provide the BrokeredMessage / Message helper pattern known as the Large Message Support pattern via Data Bus or manual blob pointer referencing. Alternatively, the Service Bus .NET SDK provides the ServiceBusPayloadUtilities or claim check pattern libraries.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Enable compression on the Azure Service Bus queue properties to automatically shrink payloads larger than 256 KB before enqueuing.
Why it's wrong here
Service Bus does not provide native automatic payload compression that guarantees fitting 1MB+ payloads into the 256KB/1MB limits.
- ✗
Configure Azure Service Bus auto-forwarding to a secondary queue configured for jumbo messages.
Why it's wrong here
Auto-forwarding does not bypass message size limits; messages exceeding limits will still fail validation.
- ✓
Use the Azure Service Bus Claim Check pattern by storing the payload in Azure Blob Storage and sending only the blob URI in the message body.
Why this is correct
The claim check pattern involves offloading large payloads to an external store (Blob Storage) and sending a lightweight reference token (claim check) through the messaging bus.
- ✗
Upgrade the Service Bus namespace to the Enterprise tier to unlock message payloads up to 100 MB.
Why it's wrong here
There is no Enterprise tier for Service Bus; Premium is the highest tier, with a maximum message size of 1 MB (or 100 MB with specific broker configurations, but Claim Check is the architectural standard pattern).
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
One of 507 original AI-200 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.