Databricks Spark Developer Associate exam-day guide
Databricks Spark Developer Associate · Prepare for the day ahead.
Your checklist
Government-issued photo ID
The name on the ID must match your registration exactly. Acceptable ID types (passport vs. driver's licence vs. national ID) vary by proctoring vendor - confirm the accepted list with the provider before exam day.
Testing-platform login and confirmation email
Have the scheduling confirmation, your candidate/account username, and password ready before you launch the session. Know the exam start time in your local time zone and in the provider's stated time zone.
Reliable internet connection
Wired ethernet is safer than Wi-Fi. Have a hotspot or phone-based backup plan, but note that switching networks mid-session may require re-verification by the proctor.
Working webcam, microphone, and speakers/headset
Run the provider's system/equipment check days in advance, not minutes before. Headphones are often restricted during proctored exams - confirm the audio policy with the provider (needs_review).
Quiet, private, well-lit room with a clear desk
Remove papers, books, sticky notes, second monitors, and any device not explicitly permitted. You will typically be asked to do a 360-degree room scan - confirm the exact procedure with the provider.
Close all other applications and silence notifications
Quit chat apps, email, music, and background sync tools. Disable OS notification pop-ups; an unexpected pop-up or window switch can be flagged as a policy violation.
Laptop power and a charged backup
Plug the machine in for the whole session and disable sleep/hibernate. A mid-exam power loss costs time you will not get back unless the provider grants an exception.
Scratch paper / whiteboard policy
Many proctored exams permit only an erasable whiteboard or a provided on-screen notepad, and some permit nothing. Do not assume - confirm with the provider what (if anything) is allowed (needs_review).
Water / snack policy
Rules on drinks and breaks differ by provider and are often tied to the scheduled break policy. Confirm in advance rather than discovering it during check-in (needs_review).
PySpark syntax reference in memory, not on paper
Since notes are typically prohibited, mentally rehearse the column-API idioms you will type: col(), lit(), when()/otherwise(), cast(), withColumn(), groupBy().agg(), join(), window functions, and reading/writing with schema definitions.
A one-page topic triage list (read before check-in, then put away)
List your weakest areas - narrow vs. wide transformations, shuffle behavior, partitioning, AQE, caching, Spark UI interpretation - and skim them in the hour before the exam. Do not keep it at the desk during the session.
Confirm the exam format details (question count, time limit, scoring, retake policy)
These specifics change between exam versions and are published on the certification provider's page. Read them yourself the week of the exam rather than relying on secondhand reports (needs_review).
Plan the day
Switch from learning to retrieval practice. Work through timed sets of PySpark API questions and, for every miss, write down the concept (not the answer). Stop adding new topics after this point.
Re-read the official exam guide's topic breakdown and score your confidence per section (1–5). Spend remaining study time only on sections scoring 1–2.
Run the proctoring system check and test your webcam, mic, and network at the same time of day as your scheduled slot, so you hit the same bandwidth conditions.
Do one final light pass over high-yield mechanics: transformations vs. actions and laziness, narrow vs. wide and shuffle triggers, repartition vs. coalesce, broadcast join thresholds, caching/persistence levels, and how to read a Spark UI stage's shuffle read/write numbers.
Stop studying by early evening. Confirm your ID is out, the room is set up, the confirmation email is findable, and you know the exact start time in your local zone.
Get a full night's sleep. Cramming the morning of a proctored exam raises the odds of a check-in mistake more than it raises your score.
Eat, hydrate, and clear the desk and room. Restart the computer to kill background processes, then launch only the proctoring/launch link.
Begin check-in early. ID verification and room scan can take longer than expected, and late starts usually are not compensated with extra time.
First pass: answer everything you know quickly and flag anything that requires reasoning through code semantics. Second pass: return to flagged items. Never leave a question blank if there is no penalty for guessing.
Read code questions carefully for what is actually returned: is the code lazy or does an action force evaluation, does it error at definition or at execution, and is the output a DataFrame or a Python object? Many items hinge on that distinction.
Budget the clock: divide remaining minutes by remaining questions every 20 minutes. If a single question costs more than ~2 minutes, flag it and move on.
Confirm no flagged questions remain unanswered, then submit. Note whether your provider displays a provisional or final score, and keep the completion confirmation.
Rules to check
Bring the exact government-issued photo ID required by the proctoring vendor, with a name matching your registration. If your legal name differs from your registration name, resolve it with the provider before exam day.
Assume the exam is closed-book: no notes, textbooks, phone, smartwatch, second screen, or unapproved software. Confirm in writing what, if anything, is permitted for scratch work.
Stay in the camera's view for the entire session. Leaving the frame, covering the camera, or having another person enter the room is typically treated as a violation - confirm the provider's specific rules on bathroom breaks and whether they are permitted at all.
Do not switch windows, open a terminal or REPL to test code, or use an AI assistant. Most proctoring tools record the session and flag window focus changes.
Follow the provider's check-in sequence (ID capture, room scan, environment questions) without shortcuts; a failed check-in can delay or void your attempt.
Scores are usually reported on a scaled basis with a set passing threshold rather than a raw percentage - confirm the current passing score, score report timing, and retake/waiting-period policy with the provider instead of assuming (needs_review).
If something breaks mid-exam (disconnection, crash, proctor interruption), stop and contact the proctor or provider support immediately and get an incident reference. Do not attempt to restart the exam on your own.
Read the provider's cancellation and rescheduling policy now; last-minute reschedules usually carry a fee or forfeiture, and the exact window is provider-specific.