5.3 Exam-Day & Retake Strategy
Key Takeaways
DP-600 runs 100 minutes with roughly 40-60 items and may include a case study, drag-and-drop, hot-area, and multi-select questions.
On case studies, skim the question stems first, then read the scenario tabs (requirements, environment, constraints) to find the exact deciding detail.
The passing score is 700 on a scaled 100-1000 model; Microsoft does not publish exam-level pass rates, so ignore any source quoting one.
Retake policy: wait 24 hours after a first failure, then 14 days between subsequent attempts, with a maximum of five attempts per 12 months and the fee (about US$165) due each time.
Passing earns Microsoft Certified: Fabric Analytics Engineer Associate, which renews yearly at no cost via a free Microsoft Learn assessment taken before expiration.
Exam Format Recap
DP-600 is delivered by Pearson VUE, proctored, either online from home or at a test center. The exam allots 100 minutes of working time (the full appointment is longer once you add the agreement, instructions, and an optional survey). Microsoft does not publish a fixed count, but its exam-experience guidance and the live exam put role-based exams in the 40-60 question range.
Expect a mix of item types:
| Item type | What it asks |
|---|---|
| Multiple choice | One correct answer from four |
| Multi-select | Choose all that apply (partial credit is not given — get every box right) |
| Drag-and-drop | Order steps or match items to targets |
| Hot area | Click the correct region/option in an image or dropdown grid |
| Case study | A shared business scenario with several bundled questions |
Microsoft Learn is available during the exam, but the clock does not stop while you browse it. Treat it as a last-resort lookup, not a study session.
Case-Study Technique
Case studies bundle several questions around one detailed business scenario presented across tabs (often Overview, Existing environment, Requirements, and Technical constraints). Work them in a disciplined order:
- Skim the question stems first to learn what the case is actually testing before you read paragraphs of background.
- Read the scenario tabs with those questions in mind, highlighting numbers, must/should language, and explicit constraints.
- Answer each question by returning to the exact tab that holds the deciding fact. Requirements and constraints tabs usually contain the trap that overrides generic best practice.
- Mind the navigation rule: a case study often locks once you advance past it. If your delivery does not allow returning, finish every bundled question before moving on.
The single most common case-study error is answering from general best practice instead of the scenario's stated constraint. If the constraint says "near-real-time KQL telemetry," the answer is an eventhouse even if a lakehouse is the textbook default.
Time Management
With roughly 100 minutes for about 40-60 items plus a case study, pace yourself so the case study never gets rushed.
| Phase | Approx. time | Action |
|---|---|---|
| Standalone questions | First pass | ~1.5 min each; flag anything uncertain and keep moving |
| Case study | Dedicated block | Read the tabs once, then answer all bundled items together |
| Review | Final 8-10 min | Revisit flagged items; change answers only with a concrete reason |
Rules of thumb that prevent timing disasters:
- Never leave a question blank. There is no penalty for guessing, so always commit a best answer before flagging.
- Do not over-edit. First-instinct answers backed by your labs are usually right; only change one if you can name the rule that makes the new choice correct.
- Watch the on-screen timer at the one-third and two-thirds marks. If you are behind, answer-and-flag aggressively to bank coverage, then return.
Scoring and Retake Policy
DP-600 uses scaled scoring out of 1000, and you need 700 to pass. Scaled scoring means raw points are weighted, so 700 is not simply 70% of questions correct. Microsoft does not publish public exam-level pass rates — ignore any 'X% pass rate' claim you see online.
If you do not pass, the Microsoft retake policy is:
- Wait 24 hours before the second attempt.
- After a second failure, wait 14 days between each subsequent attempt.
- A maximum of five attempts is allowed within a 12-month period.
- Each attempt requires paying the exam fee again (about US$165 in the U.S.; the price varies by country and proctoring location).
Use a failed attempt productively: your score report breaks performance down by skill area, so rebuild the weakest domain hands-on in your Fabric trial before rebooking rather than re-reading the same notes.
After You Pass
Passing earns the Microsoft Certified: Fabric Analytics Engineer Associate credential. It renews on a 12-month cycle through a free Microsoft Learn renewal assessment that you take in the six months before your expiration date — there is no retake fee and it is unproctored, but you should still set a reminder roughly six weeks out so it does not lapse.
Renewal is genuinely low-effort but easy to forget: it is a short assessment, you can attempt it more than once if you do not pass the first time, and it costs nothing. The trap is letting the certification expire — if the renewal window closes, you must re-sit the full paid DP-600 exam to regain the credential. Calendar the window the day you pass.
Natural next steps depend on your goals:
| Direction | Recommended next exam |
|---|---|
| Deepen Power BI reporting | PL-300 (Power BI Data Analyst) |
| Broaden Azure data fundamentals | DP-900 (Azure Data Fundamentals) |
| Move toward engineering | DP-700 (Fabric Data Engineer) and Fabric architecture roles |
Keep building in Fabric after you certify. The credential reflects current product behavior, and Fabric ships changes frequently — the same January 2026 outline refresh that reweighted topics will not be the last. Hands-on familiarity is what keeps the certification meaningful on the job.
A candidate fails DP-600 on the first attempt and wants to retake as soon as allowed, and again quickly if needed. What does Microsoft's retake policy require?
Wait 24 hours after the first fail; after a second fail, wait 14 days between further attempts, up to five attempts in 12 months
Wait 14 days after the first fail, with unlimited attempts
No waiting period; retake immediately any number of times
Wait 30 days, and only two attempts are ever allowed
On a DP-600 case study, a question asks which Fabric store to use. General best practice suggests a lakehouse, but the constraints tab states the team must query streaming telemetry with KQL in near real time. What should you select?
Lakehouse, because it is the general best practice
Eventhouse, because the scenario's stated constraint (near-real-time KQL telemetry) overrides generic best practice
Warehouse, because case studies always prefer T-SQL
Whichever store you chose for the previous unrelated question
Sections you finish are checked off in the contents.
You've completed this section
Continue exploring other exams