CCIE Collaboration exam-day guide
CCIE Collaboration · Prepare for the day ahead.
Your checklist
Photo ID that matches your registration exactly
Bring the government-issued photo ID whose name matches the name on your exam registration. If your ID name differs (middle name, maiden name, transliteration), resolve it with the provider before test day; do not assume the proctor will accept an explanation. For a lab-style practical exam, confirm with the provider which ID types are accepted at the specific delivery location (test center vs. remote proctoring).
Your exam appointment confirmation and candidate/registration number
Have the confirmation email and your candidate ID accessible on paper and on your phone. You will need them at check-in and if any scheduling discrepancy arises. Confirm with the provider whether printed confirmation is required or a digital copy is acceptable.
Review the current official exam blueprint and lab environment documentation
The practical exam tests hands-on configuration and troubleshooting across the published blueprint domains (call control, dial plan, gateways, collaboration applications, mobility, security, QoS, and troubleshooting). Re-read the blueprint's topic list and the provider's published lab-environment notes in the final week so you are not surprised by interface or version differences. Do not rely on third-party dumps or recalled question lists.
Practice the full task loop under time pressure
In your last practice sessions, work realistic multi-step tasks end to end: read the requirement, plan, configure, verify with show/debug commands, and document. Timebox each task. The practical exam rewards completing verified working configurations over partially finished ambitious ones.
Build a personal verification command sheet (from memory, not copied)
Write out, in your own words, the verification commands and expected outputs you rely on for each domain: dial-peer matching, translation and called/calling-number manipulation, registration and call-admission status, SIP and H.323 gateway signaling, and application service health. Practicing recall of verification steps is more valuable than memorizing configuration syntax alone.
Plan your logistics: travel, lodging, arrival buffer
For an in-person lab, arrive with a generous buffer for security screening and check-in. Know the building, floor, and check-in desk in advance. Confirm with the provider the arrival time and late-arrival policy; do not assume a grace period.
Confirm what is and is not permitted in the lab room
Ask the provider in advance about phones, smart watches, notes, printed materials, bags, and food/drink. Policies vary by delivery location. Assume nothing; get the answer in writing before you travel.
Confirm break rules and whether breaks pause the clock
Break policy on timed practical exams differs by provider and format. Ask whether scheduled or unscheduled breaks stop the timer, whether you may leave the room, and whether you can return to unfinished tasks. Confirm with the provider.
Confirm scoring, partial credit, and result timing
Understand whether each task is scored independently, whether partial configurations earn credit, and when results are released. Ask the provider directly; do not infer the scoring model from practice material.
Prepare a reset/rollback habit
Before changing a working configuration, capture the current state (running-config excerpts or saved copies) so you can revert quickly if a change breaks connectivity or call flow. On a timed practical, a fast rollback is often worth more than a clever fix.
Sleep, hydration, and a light meal plan
A multi-hour hands-on exam is an endurance event. Protect sleep in the final two nights, plan a light meal before the start, and confirm with the provider whether water or snacks are allowed at the desk.
Know your weak-domain triage order
Decide in advance the order in which you will attempt tasks: secure quick wins first, then high-value tasks in your strongest domains, leaving the most uncertain domain for last. Write the order down and follow it rather than drifting task to task.
Plan the day
Stop learning new topics. Do a final pass over the blueprint and list the three domains where you are least confident. For each, run one focused hands-on drill and write a short verification checklist from memory. Reconfirm appointment time, location or remote-proctoring setup, and ID requirements with the provider.
Do one full-length timed practice run in conditions close to the real exam: no phone, no browser tabs, single screen if that is what you will have. Afterward, review only where you lost time, not where you lost points on obscure trivia.
Do a logistics audit: travel route, arrival buffer, parking or transit, building access, and check-in desk. Pack your ID and confirmation. If remote, test your camera, microphone, network, and room setup with the provider's system check.
Light review only: your personal verification command sheet, your weak-domain checklists, and your triage order. Do not start new labs. Prepare clothes and items for the morning. Set two alarms. Get a full night's sleep; this matters more than one more practice task.
Eat a light meal, hydrate, and arrive early. Leave your phone and any prohibited items as instructed. At check-in, present your ID and confirmation, listen carefully to the proctor's briefing, and note how to ask questions and how breaks work before the clock starts.
Read the full task list and any environment notes before touching a device. Sketch your triage order and rough time budget on the provided materials or scratch area. Identify tasks that depend on other tasks so you sequence prerequisites first.
Work in verify-as-you-go mode: after each configuration change, confirm the intended behavior with a show or test command before moving on. Save working state before risky changes. If a task stalls, note where you stopped, move to a quick win, and return with remaining time.
Stop starting new work. Verify that every attempted task is in a consistent, saved state, revisit any task you abandoned mid-change, and confirm nothing you configured earlier was broken by a later change. Use remaining time for verification, not new features.
Rules to check
Bring government-issued photo ID whose name matches your registration exactly; resolve any mismatch with the provider before test day rather than at check-in.
Do not bring or use unauthorized materials, notes, phones, smart watches, or recording devices in the lab. Ask the provider in advance what is permitted; policies vary by location and format.
Treat the exam content as confidential. Do not reproduce, photograph, record, or share exam tasks, topologies, or configurations afterward, and do not use recalled-content dumps to prepare.
Follow the proctor's instructions at all times. If you are unsure whether an action is allowed (opening a help page, using a scratchpad, leaving the room), ask before doing it.
Confirm the break policy with the provider before the exam: whether breaks are allowed, whether the clock pauses, and whether you may leave and re-enter the room.
Confirm the scoring model with the provider: whether tasks are scored independently, whether partial configurations earn credit, and when and how results are released.
If you hit a technical failure (device unreachable, console drop, environment error), stop and notify the proctor immediately and note the time; do not silently burn your clock troubleshooting the delivery platform.
Plan to arrive early and confirm the late-arrival policy with the provider; a missed check-in window may end your attempt regardless of preparation.