Reliability · interview question
Which boundary choice best fits failure policy in a maintainable Python system?
Multiple choiceHardchapter-5-curatedpremiumreliabilityfailure-policy
Answer and explanation
Correct answer
D. 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 Reliability
A free test with instant, explained results. No account needed.
More Reliability questions
- If you wrote a test around failure policy, what should the test prove first?
- Which option describes the most likely pitfall around failure policy?
- What is the clearest sign that code around failure policy should be refactored?
- A teammate submits shaky failure policy code. Which review comment is the strongest?
- A bug appears around failure policy. What is the strongest first debugging move?
- Which explanation would sound strongest in an interview when discussing failure policy?