Security · interview question
Which boundary choice best fits token and auth handling in a maintainable Python system?
Multiple choiceMediumchapter-17-curatedpremiumsecuritytoken-and-auth-handling
Answer and explanation
Correct answer
C. 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 production risk should you worry about most if token and auth handling is handled lazily?
- What assumption should be made explicit when working with token and auth handling?
- If token and auth handling fails in production, what handling philosophy is strongest?
- Which option describes the most likely pitfall around token and auth handling?
- When is token and auth handling being used in the wrong way?
- Which explanation would best help the team align on token and auth handling?