Unit 2 Roadmap — Design data storage solutions
AZ-305 › Unit 2
Unit 2 Roadmap — data storage solutions
This roadmap turns the unit into a study sequence. The goal is to connect topic decisions, not memorize isolated product facts. The current exam blueprint allocates 20–25% to this domain.
Unit 2 release map
- 20–25%
- 3
- Defensible recommendation
- Checkpoint plus design studio
Unit thesis
Choose data services from workload shape, consistency, scale, recovery, governance, and operating model—not brand familiarity.
Recommended learning sequence
- Classify the data model and query/transaction pattern before selecting a service.
- Design protection, durability, availability, and scale as separate requirements.
- Select batch, streaming, orchestration, and transformation surfaces from latency and control needs.
Text equivalent: study each topic cram sheet, complete the unit checkpoint, then prove synthesis in a design studio.
Topic map
| Topic | Architectural decision | First trap to reject |
|---|---|---|
| 1. Design data storage solutions for relational data | Match engine compatibility, transaction needs, scale topology, administration, and recovery requirements. | Read replicas do not scale writes. |
| 2. Design semi-structured and unstructured data storage | Choose object, file, key-value, document, or analytical storage from access pattern and governance. | A storage tier is not a redundancy option. |
| 3. Design data integration | Separate movement, orchestration, transformation, streaming, and business workflow requirements. | A connector list is not an integration architecture. |
How to work this unit
For each topic, read the linked full lessons first when the service boundary is unfamiliar. Use the cram sheet to compress the decision rules. Then close the notes and answer the retrieval prompts. Finish with scenarios that force two or more topics to interact. A correct product name without a constraint-based explanation is not sufficient evidence of readiness.
When reviewing an answer, write a one-sentence recommendation in this form: Choose X because constraints A and B matter; reject Y because it fails C; accept trade-off D. This structure exposes guesses and makes technical review easier.
Pre-checkpoint checklist
- I can state the decision boundary for every service family in this unit.
- I can distinguish high availability, recovery, security, and governance controls when they appear together.
- I can identify the strongest distractor and the requirement it fails.
- I can draw the major dependency or signal flow without copying a diagram.
- I can explain operational ownership and cost consequences, not only features.
- I have corrected every missed retrieval prompt at least once from memory.
Common failure patterns
- Treating geo-replication as backup or immutable retention.
- Choosing Cosmos DB only because the word global appears in the scenario.
- Confusing an integration workflow with an analytics transformation engine.
Source and freshness
Aligned to the current AZ-305 study guide and grounded in the two attached corpus sources. Product details and limits must be checked against current Microsoft Learn documentation. Reviewed 2026-08-02.