Security · interview question
Which boundary choice best fits log redaction in a maintainable Python system?
Multiple choiceHardchapter-17-curatedpremiumsecuritylog-redaction
Answer and explanation
Correct answer
A. Keep the concern close to the data or API boundary that owns it instead of scattering it across unrelated helpers.
Why
Responsibility should follow ownership. When the concern lives near the right boundary, the system is easier to test and explain.
Test yourself on Security
A free test with instant, explained results. No account needed.
More Security questions
- What is the healthiest performance judgment around secrets management?
- What is the clearest sign that code around secrets management should be refactored?
- If input validation fails in production, what handling philosophy is strongest?
- Which response shows the healthiest evidence-first mindset around input validation?
- When is log redaction being used in the wrong way?
- You cannot rewrite everything today. What is the best incremental improvement around dependency hygiene?