PNPT exam-day guide
PNPT · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the same ID you registered with; name must match your registration exactly. Confirm with the provider which ID types are accepted and whether a secondary ID is required.
Provider account credentials and exam launch instructions
Know how to reach the exam portal, your candidate dashboard, and any launch link or proctor check-in page. Confirm with the provider the exact launch procedure for a practical/hands-on exam.
Reliable internet connection with a backup
Wired connection preferred; have a mobile hotspot as fallback. Test upload/download speeds and latency the day before. Confirm with the provider the minimum bandwidth and whether a disconnection pauses or ends the attempt.
Charged laptop and power adapter
Fully charge overnight and keep the adapter plugged in during the exam. Have a spare cable if possible.
Your own testing environment and tooling plan
Know which tools, terminals, VPN clients, or browsers you are permitted to use, and prepare them in advance. Confirm with the provider whether third-party tools, notes, or a second monitor are allowed.
Written notes on scope, methodology, and reporting structure
If open-notes are permitted, prepare a concise one-page reminder of engagement phases, evidence capture, and report sections. Confirm with the provider whether notes are allowed before relying on this.
Time budget written down
Note the total exam duration and your planned split across enumeration, exploitation, post-exploitation, and reporting. Confirm with the provider the exact duration and whether the report is submitted within the same window.
Backup plan for technical failure
Know the provider's support contact and incident process before you start. Confirm with the provider how to report a mid-exam outage and what evidence they require.
Quiet, private room
Remove distractions, silence phones, and tell household members you are unavailable. Confirm with the provider whether a room scan or proctor monitoring is required.
Water, snacks, and a break plan
Keep supplies at your desk so short breaks do not eat exam time. Confirm with the provider whether scheduled or unscheduled breaks are permitted and whether the clock runs during them.
Report template ready
Have an offline document with headings for scope, findings, evidence, impact, and remediation. Confirm with the provider the required report format and submission method.
Rest and a clear head
Sleep well the night before; a practical exam rewards steady judgment more than last-minute cramming.
Plan the day
Re-read the exam objectives and scope statement and map each objective to a technique you can execute without reference material. Rehearse your full workflow end to end on a practice lab: enumeration, foothold, privilege escalation, lateral movement, and evidence capture. Time yourself so you know how long each phase takes. Finalize your note sheet and report template, and verify every tool you plan to use launches and connects.
Do a full technical dry run: test the exam portal login, proctor check-in if applicable, network stability, and any VPN or client software. Charge all devices and pack your ID. Confirm with the provider any last details you are unsure about, such as permitted tools, break policy, and report submission. Stop studying early, eat properly, and sleep a full night.
Eat a real meal and hydrate. Set up your workspace, close unnecessary applications, and silence notifications. Log in early to absorb any check-in friction. Re-read your time budget and note sheet once, then put the notes aside. Start with a short scope and enumeration plan rather than diving straight into exploitation.
Confirm the environment and connectivity work, then complete broad enumeration before attacking anything. Record every host, service, and credential you find as you go, because evidence you do not capture is evidence you cannot report. Set a checkpoint alarm so you do not over-invest in a single target.
Work the exploitation and post-exploitation phases against your time budget. When a path stalls, note it and pivot rather than burning an hour. Keep capturing screenshots and command output for the report as you work, not afterward.
Reserve a fixed block for the report, even if some objectives are unfinished. Write findings with clear evidence, impact, and remediation, and follow the required format exactly. Verify the submission method and confirm the report is received before the window closes.
Rules to check
Present valid government-issued photo ID matching your registration; confirm with the provider the accepted ID types and any secondary verification.
Follow the provider's rules on permitted tools, notes, internet access, and AI assistance. When in doubt, ask before the exam rather than risk a conduct violation.
Do not communicate with other people about the exam content during the attempt, and do not share, publish, or discuss specific exam tasks afterward in violation of the provider's confidentiality terms.
Confirm with the provider whether breaks are allowed, whether the clock runs during them, and what happens if you leave the testing environment.
Understand the scoring model before you start: confirm with the provider how objectives are weighted, whether partial credit exists, and whether the report is graded separately from the technical work.
If a technical failure occurs, stop and follow the provider's incident process, capturing timestamps and evidence; do not attempt to work around it silently.
Submit the report through the required channel within the stated window; confirm with the provider the exact deadline and accepted file formats.
Keep your own evidence and notes secure and do not reuse real client data from other engagements in your exam report.