What is the main drawback of leaving debug logging enabled permanently in production?
Select an answer to reveal the explanation.
Short Explanation
Debug logging burns disk and I/O all the time, and it buries the useful entries in noise—so you lose the signal you turned it on for.
Full Explanation
The correct answer is that debug logging consumes disk and I/O continuously and dilutes significant entries among routine detail, making real problems harder to find. Verbose logging has a standing cost in disk consumption and write throughput, and the signal-to-noise ratio worsens: the interesting entries are still there, but they are surrounded by far more output that is not useful. The claim that the agent stops reporting telemetry to the backend while debug logging is active is incorrect because telemetry reporting continues independently of the agent's own log verbosity. The claim that debug logging cannot be disabled once enabled is incorrect because log level is a configuration setting that can be reverted at any time. The claim that debug output is not written to disk, so nothing is retained, is incorrect because debug output is written and retained, which is exactly why the disk cost is real. For the exam, describe the cost of permanent debug logging as resource consumption plus reduced signal.