JNCIP-SP exam-day guide
JNCIP-SP · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the same ID name that appears on your exam registration; a mismatch can block admission. Confirm with the provider which ID types and second-ID rules apply at your test center or for online proctoring.
Appointment confirmation and exam code
Save the confirmation email and your exam/registration number offline (screenshot or printed). You may not have access to email or your phone once the exam starts.
Provider account credentials
Know the username and password for your testing-account login, and have the password recovery path ready in case you are prompted to re-authenticate on arrival.
Lab environment and device check
If the exam is delivered as a hands-on lab, confirm with the provider in advance which environment you will use (remote lab portal or on-site equipment) and what software you may install or must not install. Do not assume your own laptop is permitted.
Juniper/Junos documentation access policy
Many Juniper lab exams historically allowed limited access to official documentation. Confirm with the provider exactly what reference material, if any, is permitted, and do not bring your own notes unless explicitly allowed.
Break and food/water policy
Confirm with the provider whether breaks are allowed, whether the clock stops, and whether water or snacks are permitted in the room. Plan hydration and meals around the stated policy.
Personal items plan
Expect phones, smartwatches, bags, and notes to be stored outside the testing room. Know where you will leave them and keep your phone silenced before entering.
Study artifacts for the final review
Bring only what the provider allows to the site; keep your condensed command/CLI cheat sheet, topology sketches, and troubleshooting flow at home or in a hotel room for pre-exam review. Do not carry them into the exam room.
Travel and timing buffer
Arrive with a buffer well beyond the provider's stated check-in time; check-in, ID verification, and environment setup can consume part of your appointment. Confirm the required arrival time with the provider.
Rest and logistics
Book lodging near the test center or a quiet space for remote delivery, and protect sleep in the last two nights. Fatigue is a bigger risk on a multi-hour lab than on a written exam.
Scratch-paper and note-taking rules
Confirm with the provider whether scratch paper, whiteboards, or digital notepads are supplied and whether they are collected. Do not bring your own paper unless told it is allowed.
Emergency contact and provider support number
Save the provider's support phone number in case of a scheduling, connectivity, or check-in problem. Report issues before the appointment window closes, and confirm the provider's policy on rescheduling.
Plan the day
Stop learning new topics. Spend the final three days on consolidation: re-read your own summary of service provider–relevant Junos topics (MPLS and RSVP/LDP signaling, BGP and route reflection, IS-IS/OSPF, class of service, policy and firewall filters, multicast, EVPN/VXLAN, and CoS on provider edge). Rehearse the exact CLI workflows you will use: commit confirmed, rollback, show commands for each protocol, and configuration comparison. Time yourself on small end-to-end tasks so you know how long a full configuration-and-verify cycle takes.
Reconfirm logistics with the provider: appointment time, arrival time, delivery format, permitted materials, and ID requirements. Verify travel and lodging. Do not leave these confirmations to the morning of the exam.
Do one timed dry run that mimics exam conditions: no documentation beyond what is permitted, no internet search, and a strict clock. Practice reading a topology description and turning it into an addressing and protocol plan before touching the CLI. Identify your two or three slowest tasks and drill only those.
Light review only: your condensed command reference, common verification commands, and a personal checklist for troubleshooting (check interface state, then IGP adjacency, then BGP session state, then policy, then forwarding). Prepare clothes, ID, confirmation, and travel plan. Confirm the provider's check-in instructions once more. Aim for a full night of sleep rather than late-night cramming.
Eat a real meal and hydrate according to the provider's break policy. Arrive early with your ID and confirmation. Silence and stow your phone before check-in. Do not attempt last-minute study in the waiting area if it will raise anxiety; a brief skim of your own summary is enough.
Read the entire task list and any provided topology or addressing table before configuring anything. Budget time per task and mark low-value or uncertain tasks to revisit. Note the commit/rollback discipline you will follow so you never leave a device in an unreachable state.
Work in dependency order: physical and logical interfaces, then IGP, then BGP and policy, then services and traffic engineering. Verify each layer before moving up. Save configurations frequently and use commit confirmed when a change risks losing management access. If a task stalls, move on and return with remaining time rather than burning the clock on one protocol.
Stop adding features. Run verification commands across all tasks, confirm commits are saved, and check that no device is left with an uncommitted candidate configuration. Re-read the task list to catch anything skipped. Use remaining time for verification, not for new configuration.
Rules to check
Bring valid government-issued photo ID matching your registration name; confirm with the provider which forms of ID and any secondary ID are accepted, and resolve name mismatches before exam day.
Follow the provider's rules on personal items: phones, smartwatches, notes, and bags are typically stored outside the testing area, and unauthorized materials in the room can void your result.
Do not communicate with other candidates during the exam, do not share or receive task information, and do not attempt to access the internet or external systems beyond what the provider explicitly permits.
Confirm with the provider whether breaks are allowed, whether the exam clock pauses, and what happens if you leave the room; assume the clock keeps running unless told otherwise.
Confirm with the provider the scoring model, passing threshold, and whether partial credit is awarded per task, so you can prioritize tasks that carry the most weight.
If you experience a technical failure, connectivity loss, or environment problem, stop and notify the proctor or provider support immediately and follow their instructions; confirm the provider's policy on incident reporting and retakes.
Do not reproduce, photograph, or distribute exam content afterward; exam confidentiality terms apply and violations can lead to score cancellation or certification revocation.
Confirm with the provider the retake policy, score-report timing, and certification validity period rather than relying on secondhand information.