MongoDB Associate Developer exam-day guide
MongoDB Associate Developer · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Use the original physical document (passport, driver's license, or national ID). The name must match your exam registration exactly, including middle names. Confirm with the provider which ID forms they accept and whether a digital copy is permitted - policies vary by delivery mode and region.
Exam appointment confirmation
Have the confirmation email or portal page open with your appointment time converted to your local time zone. Note whether you may join early or must join at the exact start time; confirm the check-in window with the provider.
MongoDB account / certification portal credentials
Verify you can log in the day before, not on exam morning. If a password reset is needed, do it at least 24 hours ahead so any verification email delay does not cost you your slot.
Reliable internet connection plus a backup
Wired or strong Wi-Fi for the primary connection, and a phone hotspot configured as a fallback. Know how to switch networks quickly if the proctor reports a drop.
Working webcam, microphone, and speakers/headset
Required for online-proctored delivery. Test them in advance. Confirm with the provider whether headsets/earbuds are allowed or prohibited - this differs between providers.
Completed system / equipment check
Run whatever compatibility or browser test the provider offers, on the same machine, browser, and network you will use on exam day. Re-run it the morning of the exam.
Quiet, private, well-lit room with a clear desk
No other people, no notes, no books, no second screen. Remove or cover study materials and wall notes within camera view. Expect a room scan at check-in.
Single monitor and all other applications closed
Disconnect external displays, quit messaging apps, and disable OS notifications. Close background sync tools and anything that could pop up a window mid-exam.
Laptop power adapter plugged in
Do not rely on battery. A shutdown mid-exam is the most avoidable failure mode there is.
Permitted physical items only
Typically nothing beyond ID and the computer. Scratch paper, whiteboards, pens, water, and calculators are commonly restricted or require advance approval - confirm with the provider before assuming anything is allowed.
Accessibility accommodations confirmed in advance
If you need extra time, a screen-reader setup, or breaks, request and confirm the approval in writing well before exam day. Accommodations are usually not granted on the spot.
A one-page topic map for last-minute review
Your own condensed summary of the exam objectives: CRUD, aggregation pipeline stages and operators, indexes and explain output, schema design patterns, transactions, and driver usage patterns. Use it before check-in, never during the exam.
Plan the day
Confirm the appointment, delivery mode (online-proctored vs. test center), and start time in your local time zone. Re-read the provider's rules on ID, permitted items, and breaks so nothing surprises you at check-in.
Run the provider's system/equipment check on your actual exam machine and network. Fix anything that fails now, while you still have time to rebook if needed.
Do a final pass over your weakest areas rather than re-reading everything. Write and practice a few aggregation pipelines and a compound-index/explain question end to end so the syntax is fresh.
Stop learning new material. Verify login credentials, ID document, room setup, and backup internet. Charge the laptop and locate the power adapter.
Confirm the check-in window and what happens if you are late - whether the slot is forfeited and whether a reschedule is possible. Get a full night's sleep; note the exact time you must wake.
Eat, hydrate, and avoid cramming new topics. Re-run the system check, close every non-essential application, clear your desk, and silence your phone (or put it out of reach if the provider requires it).
Open the exam link early, complete ID verification and the room scan, and let the proctor finish their checks without rushing. Have your ID in hand before you click start.
Read the whole question before the options - many items hinge on one word like 'first', 'most efficient', or 'which index'. Answer the ones you know first; flag anything long or ambiguous and return to it.
For code and aggregation questions, reason about execution order and what the server actually returns, not what looks syntactically familiar. Eliminate options that would error or scan more documents than necessary.
Make sure no question is blank - an unanswered item scores the same as a wrong one on most scored exams. Then review flagged items only, and avoid changing answers without a concrete reason.
Note how you were told results would be delivered and roughly when. Do not close your browser or shut the machine down until the proctor confirms the session has ended.
Rules to check
Follow the proctor's instructions at all times. If a proctor asks you to adjust the camera, show your desk, or stop doing something, comply immediately and calmly - a disputed instruction is far easier to resolve than an apparent violation.
Keep your face in frame and your hands visible for the entire session unless the proctor says otherwise. Do not leave the camera view, and do not let anyone else enter the room. If you must leave, raise it with the proctor first.
Do not use unauthorized materials of any kind: no notes, second screens, phones, smart watches, or AI assistants. Whether scrap paper is permitted varies by provider - confirm in advance rather than assuming.
Do not communicate with anyone but the proctor during the exam. Reading questions aloud is generally tolerated, but discussing them with another person is not.
Read the provider's policy on breaks, and confirm whether the clock stops or keeps running during one. Unapproved breaks during a proctored session can void your attempt - ask the proctor instead of stepping away.
Do not share, reproduce, or discuss specific exam questions afterward. Certification agreements typically prohibit disclosing exam content, and violating that can invalidate your result regardless of your score.
Understand the scoring model before you start: confirm with the provider whether questions are weighted, whether there is a penalty for guessing, and what the passing score is. Unless a penalty is explicitly stated, do not leave items unanswered.
If something goes wrong - connection loss, a crashed browser, a proctor dispute - stop and contact the proctor or provider support immediately and get a case or ticket reference. Do not attempt to restart the exam on your own.