AZ-204 Develop for Azure storage Practice Question
You are a developer at a global e-commerce company. The company uses Azure Blob Storage to store product images and customer uploads. The application is deployed in the East US region. You need to design a solution that meets the following requirements: - Customers upload images (up to 10 MB) that must be immediately accessible worldwide after upload. - You must minimize egress costs for data transfer from Azure to customers. - The solution must be resilient to regional outages. - You must not use any custom caching logic. Which approach should you implement?
⚠ Common exam trap
The trap here is that candidates often overcomplicate the solution by choosing geo-replication or multiple storage accounts, when a single storage account with a global caching layer like Azure Front Door is simpler, cheaper, and meets all requirements without custom logic.
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 Azure Front Door with caching enabled, and point it to a single Blob Storage account in East US.
Azure Front Door with caching enabled provides global HTTP caching at Microsoft edge nodes, which minimizes egress costs by serving cached content from the edge closest to the user. It also offers built-in regional failover for resilience, and requires no custom caching logic. This meets all requirements: immediate global accessibility, minimized egress costs, regional outage resilience, and no custom caching.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use read-access geo-redundant storage (RA-GRS) and direct customers to the secondary endpoint for reads.
Why it's wrong here
Using read-access geo-redundant storage (RA-GRS) allows data redundancy and read access from a secondary region, but it does not provide content caching at edge locations. Directing customers to the secondary endpoint for reads means all requests still hit a storage account directly, incurring egress costs from that region and failing to reduce latency for geographically dispersed users through edge caching. This approach does not optimize for performance or cost by eliminating caching benefits.
- ✗
Use Premium Block Blob storage in multiple regions and use Traffic Manager for routing.
Why it's wrong here
Premium Block Blob storage offers high performance for specific workloads but does not inherently include a caching mechanism for global content delivery. While Azure Traffic Manager can route users to the closest or healthiest storage account endpoint, it operates at the DNS level and does not provide content caching at the edge. This setup would still result in direct hits to storage accounts, leading to higher egress costs and increased latency for users far from the chosen region, without the benefits of a CDN or WAF.
- ✗
Use Azure CDN from Microsoft with the storage account as origin, and enable geo-replication on the storage account.
Why it's wrong here
Azure CDN from Microsoft effectively caches content at edge locations, significantly reducing latency and egress costs from the origin. However, a standard CDN configuration with a single origin does not inherently provide active failover to a geo-replicated secondary storage account in case the primary origin becomes unavailable. While geo-replication ensures data durability, integrating it for active failover with CDN requires additional custom logic or a more advanced service like Front Door, making this solution incomplete for robust global availability.
- ✓
Use Azure Front Door with caching enabled, and point it to a single Blob Storage account in East US.
Why this is correct
Azure Front Door is a global, scalable entry-point that leverages Microsoft's global edge network to deliver web applications and content. With caching enabled, it serves content from edge locations closest to users, significantly reducing latency and egress costs from the origin Blob Storage account. Front Door also inherently provides advanced routing capabilities, including automatic failover to a secondary origin if configured, and Web Application Firewall (WAF) features, making it ideal for global e-commerce scenarios requiring high performance and availability.
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 |
Go deeper
Related to this question
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.