DP-420 exam-day guide
DP-420 · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the original physical ID (passport or government photo ID), not a photocopy or a photo on your phone. The first and last name on the ID must match your exam registration exactly. If your name differs (e.g., a shortened first name or a missing second surname), contact the certification provider before test day to correct the registration - this is the single most common cause of being turned away.
Appointment confirmation / registration ID
Have your confirmation email or appointment number available on your phone before you enter the testing area, then put the phone away. You should not need it at the desk, but it resolves check-in disputes quickly.
Second form of ID (if required at your location)
Some test centres and some jurisdictions require a second ID or a signature-bearing card. (needs_review - confirm with the provider / your chosen test centre before travelling.)
Arrive early (test centre) or start system check early (online)
Plan to be at the test centre well before your slot - commonly 15–30 minutes early for check-in and locker storage. For online proctoring, begin the system/ID check 30 minutes before your appointment so a failed webcam or bandwidth test does not eat your exam time. (needs_review - the exact recommended lead time is set by the provider; confirm it.)
Online-proctoring environment: quiet private room, closed door, clean desk
Clear the desk of papers, books, phones, smart watches, and any second monitor. The proctor will ask you to pan the webcam around the room. Any screen with notes visible - including sticky notes on a monitor edge - can void the session.
Hardware check: webcam, microphone, speakers/headset, wired-ish stable internet
Run the provider's system test on the same machine and network you will use on exam day, ideally 24 hours ahead. Have a fallback plan (phone hotspot, alternate machine) if your primary connection drops.
Know your permitted scratch materials
Test centres typically issue a whiteboard/laminated sheet and marker; online sessions usually provide an on-screen noteboard. Confirm which applies to you and do not bring your own paper or pen. (needs_review - policy varies by provider and delivery mode.)
Confirm whether the exam contains non-returnable sections or lab items
Microsoft exams sometimes place case studies or interactive/lab sections at the start or end, and you may not be able to return to earlier questions once you move on. Check the current exam details page so the sequencing does not surprise you. (needs_review - confirm the current format for DP-420.)
Refresh the high-weight DP-420 domains the night before
Prioritise, in this order: data modelling and partitioning (hierarchical partition keys, partition key choice, hot-partition avoidance); throughput (manual vs autoscale RU/s, serverless, RU estimation and optimisation); indexing policy (included/excluded paths, composite indexes, IndexingMode); consistency levels (five levels and their trade-offs); global distribution and conflict resolution (LWW, custom, stored procedures); change feed (including change feed processor and the all-versions-and-deletes mode); .NET/Java/Python/JS SDK v3 patterns (CosmosClient lifetime, FeedIterator, transactional batch); stored procedures, triggers and UDFs plus their partitioning constraints; security (account keys, Entra ID RBAC/data-plane roles, network restrictions); integration (Azure Functions bindings/trigger, Synapse Link, Azure Search); monitoring and diagnostics (SDK diagnostics, RU charge, latency, throttling/429 handling with retry-after).
Practise reading SDK code, not just concepts
DP-420 asks you to identify what a code fragment does or what is wrong with it. Be fluent in the shape of CosmosClient/Container/ItemResponse, QueryDefinition with parameters, FeedIterator loops, and TransactionalBatch - recognise them by eye rather than reasoning from first principles under time pressure.
Sleep and food plan
Book the slot at a time when you are normally sharp; a ~100-minute proctored session with no scheduled break is harder than it looks. Eat beforehand, and hydrate moderately rather than heavily.
Plan the day
Do one full timed practice run under exam conditions (no notes, no pausing). Use the result to pick your two weakest DP-420 domains and spend the remaining study time only there. Stop trying to learn new topics after this point; consolidate instead.
Re-verify the logistics that are not in your control: appointment date, time, and time zone; test centre address and travel time, or online-proctoring system requirements; ID name match. Fix any mismatch now, not on the day.
Write a one-page cheat sheet from memory covering partition key selection heuristics, consistency level trade-offs, indexing policy defaults, and RU/s modes. Rewriting it from memory is the exercise; do not bring it into the exam.
Light review only: re-read your cheat sheet and skim the SDK patterns (client lifetime, batch, change feed processor, retry-after on 429). Then stop. Cramming new material the night before reliably costs more in fatigue than it gains.
Run the online-proctoring system test if you are testing remotely, and charge/position your equipment. Confirm the room you will use is free of clutter and that nobody else will enter it during your slot.
Lay out ID, confirmation, and (if travelling) your route and backup route. Set two alarms. Get a full night's sleep - this matters more than one more hour of revision.
Eat properly, avoid heavy caffeine if you are already anxious, and re-read only your cheat sheet. Do not start a new practice test - a bad score an hour before the exam changes nothing except your confidence.
Arrive at the centre or launch the proctoring app early. Complete ID verification and the room scan with time to spare; keep your phone off and out of the room once check-in begins.
Read the whole question stem before the answer choices; DP-420 questions are often decided by a single qualifier ('minimal cost', 'minimal development effort', 'must not require code changes'). Answer easy items immediately and flag anything requiring more than about 90 seconds of reasoning.
For code fragments, identify the object types and the call being made before evaluating the options; eliminate answers that use APIs or modes that do not exist. For architecture scenarios, eliminate options that require redeploying data or changing the partition key when the question constrains you against it.
Track roughly one question per minute to one and a half minutes and keep a buffer for flagged items. Reserve the last several minutes to revisit flags and confirm you have answered every item - unanswered items score as incorrect.
If a case study or non-returnable section is presented, read the whole scenario once before answering and note that you cannot come back to it. Submit deliberately: confirm the final review screen rather than closing the window.
Take the score report (printed or on screen) with the section-level breakdown. If you did not pass, note which domain dragged the score down and use that to target the retake; the report is your best diagnostic.
Rules to check
Bring original government-issued photo ID whose name matches your registration exactly. Copies, expired documents, and digital images are not accepted; if you have any doubt about your ID or name match, confirm with the provider before test day.
Personal items - phone, smart watch, notes, bags, and any second screen - must be stowed or out of the room for the entire session. Do not touch your phone during a proctored break; doing so can invalidate the attempt.
Do not reproduce, discuss, or record exam content. Sharing questions or answers, in any form and on any platform, breaches the certification agreement and can result in score cancellation and a ban.
Scheduled breaks are generally not offered on exams of this length; if you are entitled to an accommodation, apply for it well in advance through the provider's process rather than raising it at the desk. (needs_review - confirm current break policy with the provider.)
Passing is normally a scaled score rather than a raw percentage - commonly 700 on a 1000-point scale for Microsoft role-based exams - so do not try to count questions to guess your standing mid-exam. (needs_review - confirm the current passing score on the official exam details page.)
Partial credit is not available: unanswered questions count as wrong. Always guess rather than leave an item blank, and always return to flagged items before submitting.
Some sections cannot be revisited once submitted (case studies, labs, or interactive items). Read the on-screen instructions at the start of each section so you know whether backward navigation is permitted.
If your session fails - connection drop, proctor issue, machine crash - stop and contact the provider's support immediately during the session window. Do not open a ticket days later; timely reporting is what supports a reschedule or retake voucher.