5.1. Exam Strategy
Budget the clock. With roughly 40–60 questions in 120 minutes, you have about two minutes per question — but case studies consume more, so bank time on the short ones. First pass: answer everything you're sure of, flag anything that needs thought, and return. A flagged question answered with ten spare minutes beats the same question rushed at minute 30.
Use the split screen like a scalpel. The Associate-level Microsoft Learn split screen is for verifying a specific fact — an evaluation method's scoring shape, a channel's auth support — not for learning a topic mid-exam. The timer runs while you read. Decide your answer first, verify only if genuinely uncertain, and cap any single lookup at a minute.
Read the last sentence first. Microsoft stems bury the actual question ("What should you do?" / "What should you recommend?") beneath scenario prose. Read the requirement, then read the scenario knowing what you're hunting for. Watch for the qualifiers that flip answers: "minimize administrative effort," "without republishing," "least privilege," "external users."
Eliminate by architecture. Most distractors violate a structural rule you now know: a knowledge source performing an action, computer use where an API exists, a Fabric agent redirected from a topic, no-auth with per-user data, manual import on a pipeline question. Cross out the impossible before weighing the plausible.
Multiple-response discipline. "Select two" answers are two independent correct actions — if your two picks only work together as a sequence, re-read the stem. Drag-and-drop ordering questions reward the canonical orders you've internalized: plan → build → evaluate → deploy; dev → test → approve → prod.
