JNCIE-SP exam-day guide
JNCIE-SP · Prepare for the day ahead.
Your checklist
Valid government-issued photo ID
Bring the exact ID document whose name matches your exam registration. Confirm with the provider which ID types are accepted and whether a second form is required; requirements vary by test center and country.
Exam appointment confirmation and candidate ID number
Have the confirmation email or portal screenshot available (printed or on your phone) so check-in staff can locate your booking quickly. Confirm with the provider whether printed confirmation is mandatory.
Know your Juniper candidate/account credentials
You may need to log in to a lab portal or certification account at the start. Verify the password works the day before; do not rely on a password reset during the exam.
Review the lab topology and technology list the day before
Re-read your own notes on the exam blueprint domains (IGP, BGP, MPLS, L3VPN, EVPN, CoS, multicast, services) so you enter with a mental map rather than discovering scope on the clock.
Practice your CLI muscle memory on Junos
Be fluent in configure/commit/rollback, commit confirmed, show | compare, load replace/merge, and traceoption-style debugging. Speed on basic operations buys time for troubleshooting.
Prepare a personal configuration template and verification habits
Know the interface, protocol, and policy skeletons you will type repeatedly, and the show commands you will use to verify each layer. This is your own preparation material, not exam content.
Confirm test-center logistics or remote-proctoring setup
For a test center, confirm address, parking, and arrival time. For remote proctoring, confirm the software, camera, microphone, room, and network requirements with the provider in advance.
Arrange transport and buffer time
Plan to arrive with margin for traffic and check-in. Late arrival policies are provider-specific; confirm with the provider what happens if you are delayed.
Plan food, water, and medication
Lab exams are long. Confirm with the provider what is allowed at your seat and whether breaks are scheduled; do not assume food or drink is permitted in the exam room.
Sleep and light review only
Do not attempt to learn a new technology in the final 24 hours. Consolidate what you already know and protect your concentration for the exam.
Read the provider's exam-day rules one final time
Rules on personal items, phones, notes, breaks, and restarts change over time. Confirm with the provider rather than relying on forum posts.
Plan the day
Stop broad study. Re-read your condensed notes on each blueprint domain and list the two or three areas where you are weakest. Spend remaining time on targeted CLI drills and verification workflows for those areas, not on new topics.
Do a full timed dry run if you have lab access: build a small topology from scratch, apply IGP/BGP/MPLS/L3VPN, and verify end to end. Time each phase so you know your real pace.
Confirm all logistics: appointment time, location or remote setup, ID, and account credentials. Resolve any uncertainty with the provider now, not on exam morning.
Light review only: your own command cheat sheet, common troubleshooting sequences, and commit/rollback safety habits. Pack ID, confirmation, and any permitted items.
Check the provider's current rules on breaks, personal items, and permitted materials. Note anything you must leave outside the exam room. Confirm with the provider if unclear.
Set two alarms, confirm transport, eat normally, and sleep. Avoid last-minute forum reading that can create doubt or introduce unverified claims.
Eat a proper meal, arrive early, and keep review minimal. At check-in, follow staff instructions, store prohibited items, and verify your workstation or remote setup before the clock starts.
Read the full task list and point values before configuring. Build a rough schedule: which tasks are quick wins, which are interdependent, and where you will return if time runs short.
Work in dependency order (addressing and IGP before BGP and MPLS, then services and policy). Commit incrementally with commit confirmed where appropriate, and verify each layer before moving on.
Reserve the final portion of time for verification and cleanup: confirm all tasks are satisfied, check for leftover misconfigurations, and make sure your final commit is in place. Do not leave a commit confirmed pending when time expires.
Re-read the task list and tick off each requirement. Save or commit final state per the exam instructions, then stop when instructed.
Rules to check
Bring the ID document specified by the provider and ensure the name matches your registration exactly. If you are unsure which documents are accepted, confirm with the provider before exam day.
Follow all instructions from test-center staff or the remote proctor. Personal items, phones, notes, and unauthorized devices are typically restricted; confirm the exact list with the provider.
Do not communicate with other candidates or share exam content. Treat all tasks, topologies, and scenarios as confidential, and do not reproduce them afterward.
Breaks are governed by provider policy and may be limited or unscheduled during a lab exam. Confirm with the provider in advance whether breaks are allowed and how the clock is affected.
Scoring is based on the exam's defined tasks and point allocation; partial credit rules are provider-specific. Confirm with the provider how partial configurations and verification are scored rather than assuming.
If a technical problem occurs (workstation, connectivity, or lab access), stop and notify the proctor or support channel immediately. Do not attempt to fix provider infrastructure yourself.
Manage your own time; the proctor will not warn you about remaining time beyond what the interface shows. Track your schedule and leave time for final verification.
Do not claim or imply official affiliation with the certification body in any communication about the exam.