Docker Certified Associate (DCA) exam-day guide
DCA · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the exact ID the registration was made under, with a name that matches your registration. If your registration name differs from your ID (for example, a shortened first name), confirm with the provider before test day how to resolve the mismatch; do not assume it will be accepted.
Appointment confirmation and test-provider login
Save the confirmation email or PDF offline and know your test-provider account credentials. Reread the confirmation for arrival time, test-center address or online proctoring link, and any check-in window. Confirm with the provider which of these is required for your delivery format.
Second form of identification
Some providers require a second ID or a signature-bearing card. Confirm with the provider whether a second ID is required and what forms are accepted; carry one if you are unsure.
Know the exam structure and time limit
Write down, from the official exam page, the number of questions, the time limit, and whether the exam is fixed-form or adaptive. Confirm with the provider if the official page does not state this clearly. Knowing the pacing target prevents surprises in the first five minutes.
Confirm allowed reference material
Docker documentation is generally not available during a proctored certification exam, but policies vary by provider and delivery format. Confirm with the provider whether any documentation, notes, or scratch paper are permitted rather than assuming.
Practice the CLI without autocomplete crutches
In the final days, rehearse typing common commands from memory: docker run flags, docker service create flags, docker network create, docker volume create, and docker stack deploy. The exam is command-line oriented, so fluency with flags and short flags matters more than memorizing long explanations.
Rehearse swarm and compose workflows end to end
On a local multi-node or single-node swarm, practice initializing a swarm, creating overlay networks, deploying a stack from a compose file, scaling a service, and inspecting service and task state. Do this without notes so you know which steps you still need to look up.
Prepare a quiet, compliant test environment
For online proctoring, clear the desk, close other applications, and test your camera, microphone, and internet connection in advance. Confirm with the provider the rules on room scans, allowed items on the desk, and whether a wired connection or backup hotspot is acceptable.
Plan arrival and buffer time
Arrive early enough to complete check-in without rushing. For a test center, confirm parking and transit; for online proctoring, start the check-in process before the appointment time. Confirm with the provider how late arrival is handled.
Sleep, food, and hydration plan
Schedule a normal night's sleep and a light meal before the exam. Avoid trying to learn new material in the last hours; fatigue costs more points than one extra fact gains.
Plan the day
Do one full timed practice run under exam-like conditions: no documentation, no autocomplete, single terminal. Score yourself, then spend the remaining time only on the topics that produced errors. Stop broad review; narrow review is more effective at this stage.
Reread the official exam domains and weightings and map each domain to the commands you can execute from memory. For any domain where you cannot name the core objects and commands, do a focused lab rather than rereading prose.
Verify logistics: confirm appointment time, location or proctoring link, ID requirements, and any software that must be installed for online proctoring. Confirm with the provider anything the confirmation does not state explicitly.
Do a light review of command syntax and object relationships only: services, tasks, nodes, overlay networks, volumes, configs, and secrets. Do not start new topics or install new tooling that could destabilize your practice environment.
Prepare your workspace and materials: ID out, confirmation saved offline, desk cleared, devices charged. Check that your practice swarm is stopped so nothing consumes resources during the exam.
Set two alarms, confirm your route or connection, and go to bed at a normal hour. Avoid last-minute cramming late into the night.
Eat a normal meal, hydrate, and do a five-minute warm-up by typing a few familiar commands in a scratch terminal. Keep it short; the goal is to wake up command recall, not to learn anything new.
Join or arrive at check-in early. Have your ID ready, close background applications, and silence notifications. If a technical problem occurs, note the time and contact the provider's support channel immediately rather than troubleshooting silently.
Read each task fully before typing. Identify the exact object and namespace being asked about, then execute the minimal command that satisfies it. Verify the result with an inspect or list command before moving on.
Manage the clock deliberately: note the total time and question count, and set a rough per-question budget. If a task stalls, mark it, move on, and return with remaining time. Do not let one environment issue consume a large block of the exam.
If a task depends on state you cannot reproduce, state your reasoning in the answer if the format allows partial credit, or move on. Confirm with the provider in advance how partial credit and unanswered items are scored.
Note which domains felt weak while the memory is fresh. If you do not pass, use that list to plan a retake rather than repeating the same broad review. Confirm with the provider the retake policy and waiting period.
Rules to check
Bring identification that matches your registration exactly. If there is any mismatch, resolve it with the provider before test day; do not expect an exception at check-in.
Follow the provider's rules on permitted materials. Assume nothing is allowed on the desk or screen unless the provider states otherwise, and confirm with the provider if the rules are unclear.
For online proctoring, expect identity verification and a room or desk scan. Keep the room private, quiet, and free of other people, and follow the proctor's instructions promptly.
Breaks are governed by provider policy and may not be available, or may not stop the clock. Confirm with the provider whether breaks are permitted and how they affect your time.
Do not communicate with anyone other than the proctor during the exam, and do not use unauthorized tools, notes, or AI assistance. Suspected misconduct can void your result.
Scoring rules, passing thresholds, and whether partial credit applies are set by the provider. Read the official exam page and confirm with the provider rather than relying on forum claims.
If a technical failure interrupts the exam, stop and contact provider support immediately, and record the time and details. Do not attempt to restart or reconfigure the environment on your own unless instructed.
Plan for a retake policy you have confirmed in advance. Do not assume a specific waiting period or number of attempts; verify it with the provider before you sit the exam.