Verbose debug logging is enabled in a shared config that currently ships in every package, including production. What should the team do for environment-specific configuration?
Select an answer to reveal the explanation.
Short Explanation
Production should not shout every internal thought by default. Keep debug noise for non-prod configs and ship quiet, safe defaults to citizens' environments. Turning logging off entirely—or logging secrets—swings the pendulum the wrong way.
Full Explanation
Developers prepare configuration for different stages with production-safe defaults. Verbose debug logging increases cost, noise, and potential data exposure if enabled by default in production packages. Environment-specific config (via AppConfig, env vars, or staged parameter values) should disable debug verbosity in production unless temporarily elevated under controlled change. Eliminating all logs or printing secrets contradicts operational and security expectations.