- A
Azure Cosmos DB with multi-region writes enabled on the account, using the SQL (Core) API, and applying strong consistency for the order placement operation via RequestOptions.
Cosmos DB supports multi-region writes with automatic conflict resolution, multiple consistency levels (strong, bounded staleness, session, consistent prefix, eventual), and the SQL API works with JSON documents. Strong consistency can be requested per request.
- B
Azure SQL Database with active geo-replication across two regions and failover groups.
Why wrong: Azure SQL Database active geo-replication only allows one writable primary; the secondaries are read-only. It does not support multi-region writes or automatic conflict resolution.
- C
Azure Cache for Redis with geo-replication.
Why wrong: Azure Cache for Redis is a caching layer, not a durable primary database. It can be used for low-latency reads but does not provide strong consistency or multi-region writes for persistence.
- D
Azure Table Storage with geo-redundant storage (GRS) and read-access (RA-GRS).
Why wrong: Azure Table Storage does not support multi-region writes; only one region can accept writes. It also lacks automatic conflict resolution and offers only strong consistency within a region.
Quick Answer
The answer is Azure Cosmos DB with multi-region writes enabled and the SQL (Core) API, using RequestOptions to enforce strong consistency for critical operations. This configuration directly supports multi-region writes with automatic conflict resolution through last-writer-wins or custom policies, while the SQL API’s flexible JSON schema accommodates the e-commerce platform’s document-based data. The key technical concept here is that Cosmos DB allows mixed consistency at the request level—you can override the default account consistency for a single operation, enabling strong consistency for order placement via RequestOptions while leaving less critical reads eventually consistent, all within the same account. On the AZ-305 exam, this scenario tests your understanding of how to balance global distribution with consistency trade-offs; a common trap is assuming you must choose a single consistency level for the entire account. Memory tip: think “RequestOptions override” for mixed consistency—strong for writes that matter, eventual for reads that don’t.
AZ-305 Design data storage solutions Practice Question
This AZ-305 practice question tests your understanding of design data storage solutions. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A global e-commerce platform requires a database that supports multi-region writes with automatic conflict resolution and single-digit millisecond latency for reads and writes from any region. The application uses a flexible schema with JSON documents. They also need to enforce strong consistency for critical operations (e.g., order placement) while allowing eventual consistency for less critical reads. Which Azure data service and configuration should they choose?
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 Cosmos DB with multi-region writes enabled on the account, using the SQL (Core) API, and applying strong consistency for the order placement operation via RequestOptions.
Azure Cosmos DB with multi-region writes enabled and the SQL (Core) API meets all requirements: it supports multi-region writes with automatic conflict resolution (last-writer-wins or custom), offers single-digit millisecond latency for reads and writes from any region, and uses a flexible JSON document schema. The ability to enforce strong consistency for critical operations like order placement via RequestOptions (using session or strong consistency at the request level) while allowing eventual consistency for less critical reads directly addresses the mixed consistency needs.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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 Cosmos DB with multi-region writes enabled on the account, using the SQL (Core) API, and applying strong consistency for the order placement operation via RequestOptions.
Why this is correct
Cosmos DB supports multi-region writes with automatic conflict resolution, multiple consistency levels (strong, bounded staleness, session, consistent prefix, eventual), and the SQL API works with JSON documents. Strong consistency can be requested per request.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Azure SQL Database with active geo-replication across two regions and failover groups.
Why it's wrong here
Azure SQL Database active geo-replication only allows one writable primary; the secondaries are read-only. It does not support multi-region writes or automatic conflict resolution.
- ✗
Azure Cache for Redis with geo-replication.
Why it's wrong here
Azure Cache for Redis is a caching layer, not a durable primary database. It can be used for low-latency reads but does not provide strong consistency or multi-region writes for persistence.
- ✗
Azure Table Storage with geo-redundant storage (GRS) and read-access (RA-GRS).
Why it's wrong here
Azure Table Storage does not support multi-region writes; only one region can accept writes. It also lacks automatic conflict resolution and offers only strong consistency within a region.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often assume Azure SQL Database's active geo-replication supports multi-region writes, but it only allows writes to a single primary region, making it unsuitable for the multi-region write requirement.
Detailed technical explanation
How to think about this question
Under the hood, Azure Cosmos DB's multi-region writes use a multi-master replication protocol based on a consensus-free approach with conflict resolution policies (e.g., last-writer-wins using a timestamp or custom merge procedures). The SQL (Core) API natively supports JSON documents and allows per-request consistency overrides via the ConsistencyLevel property in RequestOptions, enabling strong consistency for critical operations while defaulting to eventual consistency for others. In real-world scenarios, this pattern is ideal for global e-commerce platforms where order placement requires strong consistency to prevent duplicate orders, while product catalog reads can tolerate eventual consistency for low latency.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Design data storage solutions — study guide chapter
Learn the concepts, then practise the questions
- →
Design data storage solutions practice questions
Targeted practice on this topic area only
- →
All AZ-305 questions
999 questions across all exam domains
- →
Microsoft Azure Solutions Architect Expert AZ-305 study guide
Full concept coverage aligned to exam objectives
- →
AZ-305 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related AZ-305 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design identity, governance, and monitoring solutions practice questions
Practise AZ-305 questions linked to Design identity, governance, and monitoring solutions.
Design data storage solutions practice questions
Practise AZ-305 questions linked to Design data storage solutions.
Design business continuity solutions practice questions
Practise AZ-305 questions linked to Design business continuity solutions.
Design infrastructure solutions practice questions
Practise AZ-305 questions linked to Design infrastructure solutions.
SAA-C03 VPC practice questions
Practise AZ-305 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise AZ-305 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise AZ-305 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise AZ-305 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise AZ-305 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise AZ-305 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise AZ-305 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise AZ-305 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free AZ-305 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this AZ-305 question test?
Design data storage solutions — This question tests Design data storage solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Azure Cosmos DB with multi-region writes enabled on the account, using the SQL (Core) API, and applying strong consistency for the order placement operation via RequestOptions. — Azure Cosmos DB with multi-region writes enabled and the SQL (Core) API meets all requirements: it supports multi-region writes with automatic conflict resolution (last-writer-wins or custom), offers single-digit millisecond latency for reads and writes from any region, and uses a flexible JSON document schema. The ability to enforce strong consistency for critical operations like order placement via RequestOptions (using session or strong consistency at the request level) while allowing eventual consistency for less critical reads directly addresses the mixed consistency needs.
What should I do if I get this AZ-305 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
4 more ways this is tested on AZ-305
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company is designing a data storage solution for a global e-commerce platform that requires low-latency access to product catalog data from multiple Azure regions. The data is read-heavy, with occasional updates. Which Azure data store should they recommend?
medium- A.Azure Cache for Redis
- B.Azure Blob Storage
- C.Azure SQL Database
- ✓ D.Azure Cosmos DB
Why D: Azure Cosmos DB is the correct choice because it provides globally distributed, multi-region writes with tunable consistency levels and single-digit-millisecond latency for read-heavy workloads. Its ability to replicate data across Azure regions and serve reads from the nearest region directly addresses the requirement for low-latency global access to product catalog data with occasional updates.
Variation 2. Your company is designing a data storage solution for a global e-commerce platform. The solution must support high-frequency read and write operations with sub-millisecond latency, and must be able to handle schema-less JSON documents. Which Azure data service should you recommend?
medium- A.Azure SQL Database
- B.Azure Blob Storage
- ✓ C.Azure Cosmos DB
- D.Azure Table Storage
Why C: Azure Cosmos DB is the correct choice because it is a globally distributed, multi-model database service that offers guaranteed single-digit-millisecond latency for both reads and writes at the 99th percentile, making it ideal for high-frequency operations. It natively supports schema-less JSON documents through its SQL API, allowing flexible data models without requiring schema definitions or migrations.
Variation 3. A global e-commerce company needs a database solution that can handle high-velocity writes from user transactions across multiple regions. They require multi-region writes with automatic conflict resolution and single-digit millisecond latency for reads and writes. Which Azure data store should they use?
easy- ✓ A.Azure Cosmos DB
- B.Azure Table Storage
- C.Azure SQL Database
- D.Azure Redis Cache
Why A: Azure Cosmos DB is the correct choice because it offers multi-region writes with automatic conflict resolution using last-writer-wins (LWW) or custom conflict resolution policies, and it guarantees single-digit millisecond latency for both reads and writes at the 99th percentile. Its globally distributed, multi-model design is purpose-built for high-velocity transactional workloads that require active-active replication across regions.
Variation 4. A global company stores customer profile data in JSON format. The application requires low-latency writes and reads from multiple regions. The solution must support multi-region writes with automatic conflict resolution and provide high availability. Which Azure Cosmos DB configuration should they choose?
medium- ✓ A.SQL API with eventual consistency and multi-region writes enabled
- B.MongoDB API with strong consistency and multi-region writes enabled
- C.Table API with consistent prefix consistency and single-region writes
- D.Gremlin API with session consistency and multi-region writes enabled
Why A: The scenario demands low-latency multi-region writes with automatic conflict resolution and high availability. Azure Cosmos DB's SQL API supports multi-region writes with eventual consistency, which is the only consistency level that allows multi-region writes. Eventual consistency provides the lowest latency and highest availability, and Cosmos DB's automatic conflict resolution handles concurrent writes across regions using last-writer-wins (LWW) or custom conflict resolution policies.
Last reviewed: Jun 11, 2026
This AZ-305 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-305 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.