JNCIE-Cloud exam-day guide
JNCIE-Cloud · Prepare for the day ahead.
Your checklist
Government-issued photo ID matching your registration name
Bring the exact ID type and name spelling your registration requires. If you have any doubt about which documents are accepted or whether a second form is needed, confirm with the provider before booking travel.
Appointment confirmation and testing-center or proctor details
Save the confirmation offline on your phone and print a copy. Note the arrival time, which is usually earlier than the start time, and the exact address or proctor check-in link. Confirm with the provider whether late arrival forfeits the seat.
Know the delivery format and whether lab access is remote or on-site
JNCIE-Cloud is a hands-on lab exam. Confirm with the provider how the environment is delivered, what client software or jump host is used, and whether you may bring your own keyboard or must use provided hardware.
Review the published exam objectives and blueprint
Work from the current official objective list for the exam version you booked. Confirm with the provider which software versions, orchestration platforms, and cloud integrations are in scope, since lab content tracks product releases.
Rehearse the full lab workflow end to end under time pressure
Practice building, verifying, and troubleshooting the topologies you expect: underlay and overlay connectivity, controller or orchestrator deployment, tenant or project provisioning, and policy enforcement. Time yourself against the real exam duration.
Prepare a personal command and configuration reference
Only bring or use materials the provider explicitly permits. Many lab exams restrict notes, so confirm with the provider what reference material, if any, is allowed in the room or on screen. If notes are barred, memorize your key command sequences instead.
Plan your troubleshooting method
Have a repeatable approach ready: check physical or virtual link state, then addressing and routing, then control-plane peering, then overlay or tunnel state, then policy and security layers. Exam scenarios reward systematic isolation over guessing.
Rest, hydration, and food plan for a long session
Lab exams can run for hours. Confirm with the provider the break policy and whether food and drink are allowed at the workstation. Plan a light meal before the start and avoid heavy caffeine if you are already anxious.
Travel and lodging buffer
Arrive the day before if you are traveling. Choose lodging close to the site or with reliable connectivity if the exam is remote. Confirm with the provider the reschedule and cancellation windows in case of disruption.
Backup connectivity for a remote delivery
If the exam is proctored remotely, arrange a wired connection, a charged backup device, and a phone hotspot as fallback. Test the proctoring software and camera and microphone in advance. Confirm with the provider the procedure if your connection drops mid-exam.
Clarify scoring and partial-credit behavior
Understand whether tasks are scored independently or as end-to-end outcomes, and whether partial configurations earn credit. Confirm with the provider rather than assuming, because this changes whether you should attempt every task or secure the ones you know.
Know the result and retake process
Ask when and how results are released and what the retake policy and waiting period are. Confirm with the provider, since certification programs revise these terms periodically.
Plan the day
Stop learning new topics. Spend the time on two or three full timed practice builds of the most likely topology, focusing on speed of verification rather than first-time configuration. Review your own notes on failure modes you have hit before, such as peering mismatches, MTU issues, or policy ordering. Confirm logistics: ID, appointment time, travel, and whether any permitted materials are allowed. Sleep on a normal schedule starting now.
Do a light review of command syntax and verification commands only. Walk through your troubleshooting checklist mentally. Prepare and lay out your ID, confirmation, and any permitted items. If remote, run a final test of the proctoring software, camera, microphone, and network. Set two alarms. Avoid cramming new features the night before; fatigue costs more points than one extra fact gains.
Eat a normal meal and hydrate moderately. Arrive or log in well before the required check-in time, allowing margin for security screening or software setup. Keep your desk clear of anything not permitted. Do a slow, deliberate read of the instructions and note the task count and any stated point values before touching the keyboard.
Read the entire task list or scenario overview before configuring anything. Identify quick wins and high-value items, and note dependencies. Sketch the topology and addressing plan on permitted scratch material. Confirm how to save or commit configurations and how to revert a broken change before you need to.
Work in dependency order: bring up connectivity, verify, then layer services and policy. After each task, verify with show commands rather than assuming success. If a task stalls, time-box it, leave a note, and move on so you can return. Save progress regularly and re-verify after any change that could break earlier tasks. Reserve the final portion of time for a full end-to-end verification pass.
Stop adding new configuration. Run through the verification checklist for every task, confirm all configurations are committed and saved, and check that nothing you changed late broke earlier requirements. Use any remaining time to re-read the task list for anything missed.
Rules to check
Present the exact government-issued photo ID your registration requires, with a name matching your booking. If you are unsure which documents are accepted, confirm with the provider before exam day; candidates without acceptable ID are commonly turned away.
Follow all instructions from the proctor or testing-center staff. Do not communicate with other candidates, and do not bring unauthorized devices, notes, or materials into the testing area. Confirm with the provider what is permitted in advance.
Do not attempt to access the internet, external systems, or any resources outside the provided lab environment unless the exam explicitly allows it. Treat the lab as a closed environment.
Confirm the break policy with the provider before you start. In many lab exams the clock keeps running during breaks, so plan your time accordingly and do not assume paused timing.
Understand the scoring model before you begin: whether tasks are scored independently, whether partial credit exists, and whether an incomplete task blocks later ones. Confirm with the provider rather than guessing, since this affects strategy.
Do not disclose, reproduce, or share exam content, topology details, or task text. Certification agreements typically prohibit this, and violations can void your result.
If you experience a technical failure, stop and notify the proctor immediately rather than improvising. Confirm with the provider the incident-reporting procedure so the disruption can be documented.
Review the reschedule, cancellation, and retake terms at booking time. Confirm with the provider the current windows and fees, since these policies change and are not guaranteed by anything written here.