Try 12 GIAC Penetration Tester (GPEN) sample questions and practice-test preview prompts on scope, reconnaissance, enumeration, exploitation safety, password attacks, reporting, remediation evidence, and retesting.
GIAC Penetration Tester (GPEN) is an offensive-security route for candidates who need practical judgment around scoping, reconnaissance, enumeration, exploitation safety, credential attacks, reporting, remediation, and retesting.
Use this page to preview the kind of penetration-testing decisions a GPEN practice route should test. The questions below are original IT Mastery sample questions, not official GIAC exam questions.
Topic: scope
A tester discovers an adjacent IP range that appears to belong to the client but is not listed in the rules of engagement. What should happen?
Best answer: D
Explanation: Penetration testing must stay inside authorized scope. Related-looking assets still require written authorization.
Topic: reconnaissance
Which activity is most appropriate during passive reconnaissance?
Best answer: B
Explanation: Passive reconnaissance collects public or nonintrusive information. Active interaction with client systems belongs to later authorized phases.
Topic: enumeration
A port scan shows TCP 445 open on several internal hosts. What should the tester do next?
Best answer: C
Explanation: Enumeration turns open ports into useful evidence. The tester needs service, configuration, and access context before drawing conclusions.
Topic: vulnerability validation
A scanner reports a critical vulnerability, but exploitation may crash a production service. What is the best next step?
Best answer: A
Explanation: Testers should prove risk safely and within the rules of engagement. Scanner severity alone is not a reason for destructive validation.
Topic: password spraying
What makes password spraying different from repeated brute force against one account?
Best answer: D
Explanation: Password spraying spreads attempts across many accounts. It can evade simple lockout thresholds and must still be authorized.
Topic: privilege escalation
A tester gains low-privilege shell access on a Linux host. Which next step is most appropriate?
Best answer: A
Explanation: Privilege-escalation analysis should look for controlled, evidence-based paths. Destructive or unauthorized actions are not appropriate.
Topic: web authentication
An application exposes a password-reset link that remains valid after password change. What is the likely concern?
Best answer: C
Explanation: Password-reset tokens should expire or be invalidated appropriately. Weak token lifecycle can create account-takeover risk.
Topic: reporting
What makes a penetration-test finding more useful to the client?
Best answer: A
Explanation: Good reports connect technical evidence to risk and remediation. Clients need enough detail to prioritize and fix issues.
Topic: exploitation safety
A tester can prove SQL injection by dumping sensitive customer records. What is the better proof approach?
Best answer: D
Explanation: Penetration testers should minimize harm. A safe proof should demonstrate risk without exposing more sensitive data than needed.
Topic: remediation evidence
After the client patches a vulnerability, what should retesting focus on?
Best answer: A
Explanation: Retesting validates remediation with evidence. It should confirm the original issue is fixed and check for closely related regressions.
Topic: phishing authorization
A client asks for a phishing test but has not approved target groups, sending domains, or escalation handling. What should the tester do?
Best answer: C
Explanation: Social-engineering tests require explicit authorization and safety boundaries. Scope protects both users and the testing team.
Topic: retesting
Why should retesting be separate from the original finding write-up?
Best answer: A
Explanation: Retesting documents whether the fix worked. It should be evidence-based and limited to the agreed remediation scope.
| If you miss… | Drill this next |
|---|---|
| scope questions | written authorization, rules of engagement, and safety boundaries |
| attack-path questions | recon, enumeration, validation, exploitation, and post-exploitation evidence |
| reporting questions | impact, likelihood, affected assets, proof, and remediation |
| retesting questions | fix validation and controlled follow-up |