Reliability · interview question
Which naming or modeling choice is strongest for failure policy?
Multiple choiceHardchapter-5-curatedpremiumreliabilityfailure-policy
def should_retry(status_code: int) -> bool:
return status_code in {429, 502, 503, 504}Answer and explanation
Correct answer
D. Use names and structures that describe the business fact directly instead of temporary implementation noise.
Why
Clear naming and modeling shorten debugging, review, and onboarding time.
Test yourself on Reliability
A free test with instant, explained results. No account needed.
More Reliability questions
- What kind of contract clarity matters most for failure policy?
- Which response shows the healthiest evidence-first mindset around failure policy?
- What does a strong engineer do when reasoning through failure policy code?
- A senior interviewer asks for one tradeoff behind failure policy. What is the strongest follow-up?
- What production risk should you worry about most if failure policy is handled lazily?
- Which option is the safer default when shipping code around failure policy?