NVIDIA NCP-AII exam-day guide
NVIDIA NCP-AII · Prepare for the day ahead.
Your checklist
Confirm the exact exam name and code on your registration confirmation
The NVIDIA Certified Professional - AI Infrastructure (NCP-AII) is delivered through NVIDIA's certification program, typically via a remote-proctored or test-center vendor. Open your confirmation email and match the exam title, code, and appointment time before you plan anything else. If the title on your confirmation does not match what you intended to book, contact the provider immediately - reschedules often have deadlines.
Government-issued photo ID with the name matching your registration
Most proctoring vendors require a government-issued photo ID (passport or national ID card) whose name matches your registration exactly. Confirm with the provider which ID types are accepted and whether a secondary ID is needed. If your registration name differs from your ID (nickname, maiden name, missing middle name), fix it before test day - proctors can and do turn candidates away.
Stable internet connection and a quiet, private room (remote delivery)
If you are testing remotely, you need a wired or strong Wi-Fi connection, a webcam, a microphone, and a closed room with no other people. Clear your desk of papers, phones, and second screens. Run the vendor's system test on the same machine and network you will use on exam day, ideally 48 hours ahead so you have time to fix driver or bandwidth issues.
Install and test the proctoring browser/software in advance
Remote proctoring usually requires a secure browser or a downloaded lockdown client. Install it and complete the equipment check at least a day early. Confirm with the provider whether a work laptop with corporate security agents is permitted - some lockdown tools conflict with endpoint protection and will fail at launch.
Know your exam blueprint and weighting
Pull the official exam description from NVIDIA's certification page and note the domains and their approximate weightings. For an AI-infrastructure exam the domains typically cover GPU and system hardware, Linux and driver/container stack, cluster networking (InfiniBand/RoCE), storage, scheduling/orchestration, monitoring, and troubleshooting. Allocate your last study hours to the heaviest domains. Confirm the current blueprint with the provider, since it can be revised.
Rehearse the hands-on commands you will be reasoning about
You should be able to recall, without notes, how to check GPU health and topology (nvidia-smi, nvidia-smi topo -m, nvidia-smi -q), query fabric state (ibstat, iblinkinfo), and inspect container/GPU visibility (nvidia-container-cli, docker run --gpus). Practicing these on a real or lab machine cements them far better than reading.
Prepare a one-page mental checklist of diagnostic order
Infrastructure questions reward a systematic approach: physical layer (power, cabling, link lights) → firmware/driver → OS/kernel modules → container runtime → scheduler → application. Write this order down during your study and rehearse applying it to sample scenarios so you do not freeze on troubleshooting items.
Plan your arrival or login buffer
Arrive at the test center 15–30 minutes early, or log in to the remote session 15–30 minutes before your slot. Proctoring check-in (ID scan, room pan, rule acknowledgment) routinely takes 10–20 minutes. Confirm with the provider how late you may check in before your seat is forfeited.
Decide your timing strategy for the question count
Note the total number of questions and time limit from your confirmation. Divide time evenly and leave 10–15 minutes at the end for flagged items. Confirm with the provider whether questions are weighted equally and whether partial credit exists - do not assume.
Confirm break and materials policy
Ask the provider whether scheduled or unscheduled breaks are allowed, whether the clock pauses during breaks, and whether scratch paper, a whiteboard, or an on-screen notepad is provided. Do not bring your own paper or pens unless explicitly permitted.
Charge devices and have a backup plan
For remote delivery, charge your laptop, keep the charger plugged in, and have a phone nearby (but out of reach during the test) so you can call support if the session drops. Know the vendor's support number before you start.
Confirm score reporting and retake policy
Ask the provider when and how results are delivered (immediate on-screen vs. emailed), what the passing score is, and how soon a retake is allowed. Do this before test day so a borderline result does not catch you off guard.
Plan the day
Finish your final content pass. Re-read your notes on the highest-weighted domains and the diagnostic-order checklist. Stop learning brand-new topics; consolidate what you know. Do one timed practice set under exam-like conditions to calibrate pacing, then review only the misses.
Run the vendor's system test on your exam machine and network. Install or update the proctoring client and confirm your webcam, mic, and browser work. Verify your ID name matches your registration. If anything is off (name mismatch, software conflict), contact the provider now - not the morning of.
Confirm your appointment time in your local time zone (watch for UTC offsets in confirmation emails). Prepare your ID, charger, and a water bottle. Clear and clean your test space. Do a light review of command syntax and key concepts, then stop early. Get a full night's sleep - sleep is worth more than one more hour of cramming.
Eat a normal meal, avoid heavy caffeine if you are jittery, and do a 10-minute warm-up: skim your diagnostic-order checklist and a few command examples. Log in or arrive with a 15–30 minute buffer. Close all other applications, silence your phone, and remove anything from your desk that the proctor could flag.
Read each question fully before answering - infrastructure questions often hinge on one word like 'first' or 'root cause'. Answer confident items quickly, flag anything that needs calculation or deep reasoning, and return to flagged items after the first pass. Apply the physical → driver → OS → runtime → scheduler → application order to troubleshooting scenarios. If a question is truly unknown, eliminate clearly wrong options and move on rather than burning time.
Review flagged items only. Do not change answers without a concrete reason - second-guessing correct instincts is a common way to lose points. Confirm you have answered every question, then submit and note any on-screen result or confirmation number.
Rules to check
Bring a government-issued photo ID whose name matches your registration exactly; confirm accepted ID types with the provider before test day.
Do not bring notes, phones, smartwatches, or a second screen into the test environment. Remote proctoring typically requires a 360-degree room scan and a clear desk; follow the proctor's instructions precisely.
Confirm the break policy with the provider in advance - whether breaks are allowed, whether the timer pauses, and whether you may leave the camera view. Assume no breaks unless told otherwise.
Scoring and passing thresholds are set by the provider; confirm the passing score, question weighting, and whether partial credit applies rather than assuming. Results are usually provisional until confirmed in writing.
Do not attempt to capture, screenshot, or share exam content. Doing so violates the certification agreement and can void your result and bar future attempts.
If your session drops or the proctoring software fails, stay calm, note the time, and contact the vendor's support line immediately; most providers have a documented reconnect or reschedule path - confirm it beforehand.
Arrive or log in early. Confirm with the provider how late you may check in before your seat is forfeited, and do not rely on being admitted after the cutoff.
Treat any technical issue with your exam machine as your responsibility to test in advance; run the system check at least 48 hours ahead so there is time to resolve problems.