Security · interview question
A bug appears around log redaction. What is the strongest first debugging move?
Multiple choiceHardchapter-17-curatedpremiumsecuritylog-redaction
masked_email = user_email[:2] + "***"
print({"customer": masked_email})Answer and explanation
Correct answer
D. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.
Why
That approach is reliable because it creates evidence. Logging everything 'for debugging' often leaks exactly the data you most needed to protect.
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?
- Which boundary choice best fits log redaction in a maintainable Python system?
- 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?