easyMultiple Choice
PT0-002 Practice Question: After a penetration test, the client's technical…
After a penetration test, the client's technical team wants to understand the exact steps required to reproduce a cross-site scripting vulnerability found in the web application. In which section of the standard penetration testing report should this information be included?
⚠ Common exam trap
It's easy for candidates to confuse the high-level 'Methodology' section (which describes the overall testing process) with the detailed 'Technical Findings' section, mistakenly thinking reproduction steps belong in the methodology rather than the findings.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Technical Findings and Recommendations
The Technical Findings and Recommendations section is the correct place for step-by-step reproduction steps because it provides detailed, actionable technical information for the client's technical team. This section typically includes specific payloads, HTTP request/response details, and the exact sequence of user interactions needed to trigger the XSS vulnerability, enabling the team to verify and remediate the issue.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Executive Summary
Why it's wrong here
The Executive Summary is designed for non-technical stakeholders such as management or executives, providing a high-level overview of risks, business impact, and broad recommendations. It intentionally excludes granular technical details like exact URLs, request payloads, or step-by-step proof-of-concept commands because that audience requires a concise risk narrative, not procedural reproduction instructions. Thus, it is the wrong section for the client's technical team seeking actionable reproduction steps.
- ✓
Technical Findings and Recommendations
Why this is correct
The Technical Findings and Recommendations section is the correct location because it houses the detailed, vulnerability-specific information that a client's technical team needs for validation and remediation. For each finding, it includes the affected asset, severity rating, CVSS vector, full technical description, and precise step-by-step reproduction instructions—often including exact HTTP requests, parameters, and expected responses. This structure allows engineers to independently reproduce the issue, confirm the risk, and verify that fixes work, which is exactly the team's objective.
- ✗
Methodology
Why it's wrong here
The Methodology section describes the overall penetration testing process, such as the scope, tools used, reconnaissance phases, rules of engagement, and techniques for enumeration or exploitation. It explains what was done and how the test was conducted at a process level, but it does not document individual vulnerabilities or provide per-finding step-by-step reproduction commands. Since the technical team specifically needs to reproduce each discovered flaw, methodology lacks the necessary detail and specificity.
- ✗
Appendices
Why it's wrong here
Appendices typically hold supplementary material like raw scan outputs, full tool logs, long command transcripts, or large code snippets that support the findings but are not curated into a clear, step-by-step narrative. While an appendix might contain the raw evidence needed to infer reproduction, it lacks the structured, per-vulnerability format that explains the sequence of actions and expected results. Therefore, it is not the primary section where a client team should expect to find concise, actionable reproduction steps for every finding.
Go deeper
Related to this question
Learn chapter
PowerShell for Penetration Testing
Key term
Penetration testing
Penetration testing is a simulated cyberattack on a computer system, network, or application to find security weaknesses before real attackers can exploit them.
Key term
XSS
Cross-Site Scripting (XSS) is a security vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users.
About these practice questions
One of 777 original PT0-003 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PT0-003 practice question is part of Courseiva's free CompTIA certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PT0-003 exam.