CCIE Enterprise exam-day guide
CCIE Enterprise · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring at least one current, unexpired government-issued photo ID. The name on it must match your registration exactly; contact the provider before exam day if there is any mismatch (e.g., a preferred vs. legal name). Ask the provider whether a second form of ID is required.
Appointment confirmation
Have your appointment confirmation, registration number, and the provider's contact/support number saved offline on your phone and written on paper.
Confirmed logistics
Know exactly where you are testing (a Cisco lab location or an approved remote/proctored setup) and how you will get there. Reconfirm your start time the day before; do not assume the time zone shown on your confirmation is your local one.
Travel and arrival buffer
Plan to arrive well before your scheduled start so you are checked in and settled before the clock starts. Ask the provider what arrival window they recommend.
Full-length timed practice
At least once in the final week, complete a full-length timed mock under exam conditions (same start time, same break pattern, no pausing the clock). The CCIE lab is a long-day endurance test as much as a knowledge test.
Speed drills, not new topics
Drill configuration recall for the blueprint's core areas (switching, routing, SD-WAN/SD-Access, automation, assurance, security) until common configs are typed from memory without hesitation.
Troubleshooting routine
Write a one-page, repeatable isolation method (verify at each layer, compare intended vs. observed state, check control plane before data plane) and rehearse it so you fall back to it under pressure.
Your own condensed notes
Prepare a short personal checklist of gotchas (VRF/address-family context, route redistribution points, NAT ordering, policy application direction). Review it only where the provider permits materials; otherwise use it during preparation and leave it outside the room.
Rest and fuel plan
Lock in a normal sleep schedule for the last three nights, plan a substantial breakfast, and bring water/snacks only if the provider confirms they are allowed in the room.
Accommodations requested in advance
If you need extra time, a separate room, or medical accommodations, request them from the provider well ahead of the exam date - these cannot usually be arranged on the day.
Personal items left behind
Assume phones, smart watches, bags, and study material must be stored outside the testing room. Confirm the provider's secure-storage policy before you travel.
Confirm allowed resources
Ask the provider in advance whether any documentation or command reference is available in the lab environment; do not count on having it.
Plan the day
Stop learning new material. Run one final full-length timed mock and review it the same day. Finalize travel, ID, and appointment details. Shift your sleep schedule so you are awake and sharp at your exam start time.
Target only your two or three weakest blueprint areas with focused labs. Re-read your own condensed gotcha list. No new technologies, no new books.
Light review only, then stop by early evening. Pack ID and confirmation, lay out clothes, confirm the route and start time, and get a full night's sleep. Do not start a long lab the night before.
Eat a real meal, arrive early, complete check-in calmly. Skim your gotcha list once if materials are permitted; otherwise mentally rehearse your time-allocation plan and your troubleshooting routine.
Read the whole task list and blueprint before configuring anything. Note which items are quick wins, which are deep, and which carry the most weight. Write down your time budget per section and a hard stop for each.
Work highest-value items first. Save/commit configuration after every completed task and verify with show commands rather than assuming. Keep a running scratch list of anything deferred.
Cap any single item at a few minutes past your budget, note it, and move on. Return later with fresh eyes; a small misconfiguration that blocks several downstream tasks is worth more than perfecting one isolated item.
Stop adding features. Verify end-to-end reachability across the whole topology, re-check that all configurations are saved, and confirm nothing you deferred is trivially fixable.
Rules to check
Bring valid, unexpired photo ID whose name matches your registration exactly. If your documents do not match, you may be refused entry - resolve it with the provider before exam day.
Treat the exam content as confidential. Do not record, photograph, copy, or discuss specific exam tasks, topologies, or questions with anyone afterward.
Only bring what the provider allows into the testing room. Unauthorized materials or devices can void your exam; ask about storage for your phone and bag in advance.
Break policy, break timing, and whether the clock runs during breaks are provider-specific. Confirm this before exam day and plan your food and water around the answer you get.
Report any environment problem (unreachable device, broken console, session drop) to the proctor immediately and ask for a ticket or incident record rather than silently losing time.
Your result is reported as a pass/fail against a scaled score set by the provider; the passing threshold is not published. Do not count items or assume partial credit - aim to complete every task fully.
If you are testing remotely, complete the provider's system and identity checks well ahead of your slot and have a backup network path available.
Follow the proctor's instructions on identification, room checks, and moving around the facility; they take precedence over anything in your own plan.