Which log-level practice best balances diagnostic value against operational cost?
Select an answer to reveal the explanation.
Short Explanation
Keep normal verbosity as your standing configuration, then raise it only for a defined period on the specific components under investigation. You pay the extra cost only when the detail is actually needed.
Full Explanation
The best practice is to keep normal verbosity as the standing configuration and raise it for a defined period on the specific components under investigation. This keeps steady-state cost low while making full detail available whenever an investigation calls for it, which is the practical balance for production systems.
Keeping debug verbosity as the standing configuration is incorrect because it pays the maximum cost continuously for detail that is needed occasionally. Keeping minimal verbosity at all times and relying on reproducing problems in a test environment is incorrect because many production problems cannot be reproduced elsewhere, and minimal logging leaves nothing to work with when they occur. Alternating verbosity on a fixed schedule regardless of whether anything is being investigated is incorrect because scheduled changes are unrelated to when detail is required and will usually be at the wrong level at the wrong moment.
For the exam, describe the balance as normal by default with targeted temporary increases.