DP-203 Design and implement data storage Practice Question
A financial services company needs to store transactional data in Azure Cosmos DB. The data is accessed by multiple applications using different partition keys. The company requires strong consistency for financial transactions and wants to minimize latency for reads and writes. Which consistency level should they choose?
⚠ Common exam trap
The trap here is assuming that lower latency always outweighs consistency, leading to the selection of a weaker consistency level that fails the financial accuracy requirement.
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
✓
Strong
Strong consistency in Azure Cosmos DB ensures that all reads see the most recent committed write, which is essential for financial transactions. Although it may introduce higher latency compared to weaker consistency levels, it provides the required correctness. The scenario prioritizes strong consistency over minimal latency, making Strong the appropriate choice.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Bounded staleness
Why it's wrong here
Bounded staleness offers consistency within a specified lag, which may be acceptable for some financial scenarios but does not guarantee strong consistency. It can introduce stale reads, which might lead to incorrect financial decisions. The requirement explicitly states strong consistency, so this level does not meet the need.
- ✓
Strong
Why this is correct
Strong consistency guarantees linearizability, ensuring reads always return the most recent committed write. This is critical for financial transactions where data accuracy is paramount. While it may increase latency compared to weaker levels, it meets the requirement for strong consistency and is suitable for scenarios where correctness outweighs latency.
- ✗
Eventual
Why it's wrong here
Eventual consistency provides no ordering guarantees and may return stale data. It is the weakest level and is unsuitable for financial transactions where accuracy is critical. While it offers the lowest latency, it fails to meet the strong consistency requirement, making it a poor choice here.
- ✗
Session
Why it's wrong here
Session consistency guarantees monotonic reads and writes within a session but does not provide global strong consistency. Different sessions may see different data, which is unacceptable for financial transactions that require a single, up-to-date view. This level is insufficient for the stated requirement.
About these practice questions
This DP-203 question is part of Courseiva's 509-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 September 2026 · checked against the official Microsoft exam blueprint
This DP-203 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 DP-203 exam.