CCNA Automation exam-day guide
CCNA Automation · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the exact ID name and spelling that matches your registration. If you test at a Pearson VUE center, staff verify identity before seating you; for online proctoring the same ID is shown on camera. If your ID name differs from your registration, contact the provider before test day to correct it - do not assume it can be fixed at check-in.
Second form of identification (confirm with the provider)
Some testing centers require a second ID such as a credit card or employee badge. The exact requirement varies by location and provider, so confirm with the provider in advance rather than guessing on the morning of the exam.
Appointment confirmation and test-center address
Save the confirmation email offline (screenshot or PDF) and confirm the street address and building entrance. Test centers are sometimes inside office parks or shared buildings with slow security lines, so plan to arrive early enough to clear check-in.
Arrival timing plan
Aim to arrive at the center roughly 15–30 minutes before your scheduled start to absorb check-in, locker use, and ID verification. Arriving late can forfeit your seat depending on provider policy - confirm the cutoff with the provider.
Review the current exam blueprint
Confirm the current CCNA 200-301 exam domains and their weightings from the official Cisco exam topics page on the day you schedule, and re-check the week of the exam. Blueprints change; study material can lag. Focus final review on automation and programmability topics (REST APIs, JSON, Ansible/Puppet/Chef concepts, SDN controllers, DNA Center, configuration management) since these are commonly under-practiced.
Know your weak automation subtopics
Write a one-page list of the automation topics you are least confident in - for example, distinguishing REST vs. SOAP, interpreting a JSON snippet, or the role of a controller-based architecture - and review only that list in the final 24 hours. Do not start new topics.
Practice reading JSON and simple API responses
Be able to read a small JSON object and identify keys, values, and nested structures, and to recognize common HTTP methods (GET, POST, PUT, DELETE) and status codes. These appear as straightforward interpretation questions - practice on paper or a scratchpad, not just in a lab.
Confirm online-proctoring system requirements (if testing remotely)
If you chose online proctoring, run the provider's system test in advance, confirm webcam/microphone work, close background applications, and verify your room meets the proctor's requirements (clear desk, no notes, adequate lighting). Requirements vary - confirm with the provider.
Plan for no personal items at the desk
Expect to store phone, watch, notes, and bags in a locker or outside the testing room. Know where you will leave them and avoid bringing valuables you cannot store.
Hydrate and eat before the exam
Eat a normal meal and drink water before arriving. Testing rooms are often warm or cold and the exam is long; being comfortable reduces careless errors on multiple-choice items.
Scratchpad policy (confirm with the provider)
Some providers supply a dry-erase board or paper for scratch work; others prohibit it. Confirm the policy for your delivery method so you are not surprised when you want to sketch a subnet or a JSON structure.
Sleep and a backup plan
Get a full night's sleep and have a backup plan for transportation or internet failure (for remote testing, a phone hotspot and the provider's support number). Know the reschedule policy before test day - confirm with the provider.
Plan the day
Stop broad review. Re-read the official exam topics list and map each domain to your confidence level. Spend the remaining time on automation and programmability, IP connectivity, and security fundamentals - the areas where candidates most often lose easy points. Do one timed practice set of 40–60 questions under exam conditions to calibrate pacing, then review only the explanations for items you missed.
Do a focused pass on automation specifics: what a REST API is and how it differs from SOAP, how JSON represents data, the purpose of configuration-management tools such as Ansible, Puppet, and Chef, the idea of a controller-based network (SDN), and the role of Cisco DNA Center. Write short definitions in your own words; if you cannot explain a term in one sentence, that is your review list.
Light review only. Re-read your one-page weak-topic list, confirm your appointment time, address, and ID, and lay out clothes and ID the night before. Confirm the provider's arrival and reschedule policies. Stop studying by early evening and sleep - a rested candidate reads JSON and subnetting questions more accurately than a tired one.
Eat a normal meal, arrive early, and bring only the required ID and confirmation. At the center, follow check-in instructions, store personal items, and use the restroom before seating. For remote testing, start the check-in process early enough to resolve any proctor or software issues without eating into exam time.
Read each question fully before answering - many misses come from skimming. Flag uncertain items and move on rather than burning minutes; return to them if time permits. For JSON and API questions, identify the key or method being asked about before choosing. For configuration and subnetting questions, use scratch work if allowed. Watch the clock but do not rush the last questions; a steady pace beats a sprint.
Use remaining time to revisit flagged questions. Change an answer only when you can point to a specific reason - second-guessing without evidence usually lowers scores. Submit deliberately and confirm the exam has ended before leaving.
Rules to check
Bring valid, unexpired government-issued photo ID whose name matches your registration exactly; if it does not match, resolve it with the provider before test day.
Follow all proctor and test-center instructions, including locker use, desk clearance, and any prohibition on notes, phones, or smart devices in the testing room.
Do not communicate with other candidates during the exam and do not attempt to copy, record, or share exam content - doing so can void your result and trigger sanctions.
Breaks, if offered, are governed by provider policy and the clock may keep running; confirm the break rules with the provider before you begin.
Scoring is criterion-referenced against the exam blueprint, and results are typically reported as pass/fail with domain-level feedback where provided; do not expect a simple percentage score.
If a technical problem occurs during the exam, stop and notify the proctor or support immediately rather than continuing; document the issue for a possible retake or case.
Rescheduling and cancellation deadlines, fees, and retake waiting periods are set by the provider - confirm them before your appointment so you are not caught by a missed window.
Do not rely on braindumps or recalled questions; they are inaccurate and violate the exam agreement. Study from official documentation and hands-on practice.