Security · interview question
A teammate submits shaky token and auth handling code. Which review comment is the strongest?
Multiple choiceMediumchapter-17-curatedpremiumsecuritytoken-and-auth-handling
Answer and explanation
Correct answer
C. Make the rule clearer and easier to explain. Treat auth data as operational state with lifecycle, scope, and visibility rules instead of as one more header string.
Why
The best review comment anchors the change to readability, correctness, and future maintenance. Scattered token handling makes debugging and rotation much harder when systems change.
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?