Why is reducing log detail during active troubleshooting counterproductive?
Select an answer to reveal the explanation.
Short Explanation
Troubleshooting is the one time you want more output, not less. Lowering verbosity strips away the diagnostic entries you need to find the cause, so you end up with less evidence than before you started.
Full Explanation
Reducing log detail during active troubleshooting is counterproductive because log levels filter which events are recorded. Lowering the level during an investigation suppresses precisely the detailed entries that would explain the behavior under examination, leaving the investigation with less evidence than before it started. The option stating that lower verbosity increases the agent's CPU consumption is incorrect because less logging reduces work rather than increasing CPU usage. The option stating that lower verbosity prevents the agent from connecting to the backend is incorrect because verbosity has no bearing on agent connectivity. The option stating that lower verbosity causes previously written log entries to be deleted is incorrect because changing the level affects what is written from that point forward, not what has already been recorded. For the exam, note that the direction of the change matters: investigate with more detail, then return to normal.