While conducting a peer review for a recent assessment, a penetration tester finds the debugging mode is still enabled for the production system. Which of the following is most likely responsible…

The correct answer is A. Configuration changes were not reverted. Leaving debug mode enabled in a production system is often the result of not reverting temporary configuration changes made during development or testing. Debug mode can expose sensitive information and should be disabled before deployment. This is a common misconfiguration…

Submitted by noor.lb· Mar 6, 2026Engagement Management

Question

While conducting a peer review for a recent assessment, a penetration tester finds the debugging mode is still enabled for the production system. Which of the following is most likely responsible for this observation?

Options

AConfiguration changes were not reverted.
BA full backup restoration is required for the server.
CThe penetration test was not completed on time.
DThe penetration tester was locked out of the system.

How the community answered

(29 responses)

A
83% (24)
B
3% (1)
C
3% (1)
D
10% (3)

Explanation

Leaving debug mode enabled in a production system is often the result of not reverting temporary configuration changes made during development or testing. Debug mode can expose sensitive information and should be disabled before deployment. This is a common misconfiguration found during reviews or audits.

Topics

#post-engagement cleanup#configuration management#security hygiene#penetration test reporting

Community Discussion

No community discussion yet for this question.

Full PT0-003 Practice