Report Writing and Post-Testing Actions CPENT Practice Questions (Page 8)

Questions 36–40

1. 36foundation · easy

   What is the main objective of a client debriefing after a penetration testing engagement?

   • ATo collect the final payment for the engagement
   • BTo demonstrate the tester's technical skills
   • CTo sign non-disclosure agreements
   • DTo explain the findings, risks, and recommended actions to stakeholders
   Reveal Solution Discussion Select an answer first
2. 37foundation · easy

   What is the primary goal of post-testing cleanup in a penetration testing engagement?

   • ATo delete all logs that might reveal the tester's activities
   • BTo remove all tools from the tester's own machine
   • CTo remove all test artifacts and restore systems to their original state
   • DTo ensure that the client cannot detect that testing occurred
   Reveal Solution Discussion Select an answer first
4. 38application · medium

   After completing a penetration test, you review the engagement and notice that the team spent excessive time manually verifying vulnerabilities that could have been automated, and one tester accidentally left a test file on a client server that was only discovered during cleanup. What should you document in the lessons-learned section of your internal post-engagement review?

   • ADocument that the cleanup issue was a one-time mistake and no process change is needed.
   • BSuggest that the client provide more time for testing so the team can be more thorough.
   • CRecommend investing in automated verification tooling and implementing a pre-cleanup checklist to prevent artifact residue.
   • DRecommend that the team avoid using automated tools to prevent false positives in the future.
   Reveal Solution Discussion Select an answer first
5. 39application · medium

   After completing a penetration test, your team reviews the engagement and notes that the client's change-management process was not followed when you requested firewall rule changes, causing a delay. What is the most appropriate lesson-learned action?

   • AAvoid requesting firewall changes in future tests to prevent delays.
   • BUpdate the engagement playbook to include a pre-test review of the client's change-management process and required approvals.
   • CDocument the delay in the final report and blame the client's process.
   • DAsk the client to waive the change-management process for future tests.
   Reveal Solution Discussion Select an answer first
6. 40expert · hard

   You are preparing a penetration test report that will be reviewed by both the client's technical team and external auditors. The auditors require traceability between each finding and the evidence supporting it. The technical team needs to quickly identify which systems are affected. How should you structure the report to satisfy both requirements?

   • AInclude a findings summary table with affected systems and severity, and add a cross-reference in each finding that links to the specific evidence appendix.
   • BCreate a separate evidence-only document with no connection to the findings.
   • CPlace all evidence in the executive summary so auditors can easily find it.
   • DList findings alphabetically with evidence embedded in each finding, without a summary table.
   Reveal Solution Discussion Select an answer first