1. First Principles of Azure Data
Before diving into specific services and exam objectives, we need the mental frameworks that make everything else click. These are not facts to memorise — they are reasoning tools that let you answer questions you have never seen before.
Why this matters: the DP-900 has far more services on it than anyone can hold in memory, and Microsoft renames and adds to them faster than any study guide can track. Candidates who revise by memorising a service list get ambushed the moment a question names something unfamiliar. Candidates who can ask three questions about the data narrow four options to one without recognising the service at all.
💡 The mental model: every Azure data service is the answer to a combination of three questions — what SHAPE is the data, what is your INTENT for it, and at what SCALE. Fix those three and the service almost names itself. The rest of this guide is those three questions applied over and over.
⚠️ The trap this phase defuses: reaching for the service before classifying the problem. When a question mentions a familiar product name, it is tempting to answer from recognition — and the exam writes distractors precisely for that reflex, offering services that are real, popular, and wrong for the stated requirement. Classify first, then choose.
