Which action should be performed after any increase to verbose logging after an event has been captured?

Question

Options

• AReboot the server to revert the verbose configuration.
• BRestart all services to ensure that the logging level is reporting correctly.
• CRevert the logging level back to its previous configuration.
• DDelete the log that contains the information that was captured to assist in troubleshooting.

• A
  3% (1)
• B
  3% (1)
• C
  92% (33)
• D
  3% (1)

Explanation

Reverting verbose logging to its previous configuration (C) is the correct action because verbose logging generates significantly more data than normal, consuming disk space, degrading performance, and potentially exposing sensitive information - it's a temporary diagnostic tool, not a permanent setting. Rebooting the server (A) is unnecessarily disruptive and may not even revert logging config if it's set in a persistent config file. Restarting all services (B) is similarly overkill and doesn't address the logging configuration itself. Deleting the captured logs (D) defeats the entire purpose of enabling verbose logging in the first place - you need those logs to investigate the event.

Memory tip: Think of verbose logging like a fire hose - you turn it on to fight the fire (capture the event), then turn it back off when done. Never leave the hose running unattended, and definitely don't throw away the water you collected.

No community discussion yet for this question.