HTTP Integration · interview question
Which boundary choice best fits timeouts and retries in a maintainable Python system?
Multiple choiceMediumchapter-12-curatedpremiumhttp-integrationtimeouts-and-retries
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 HTTP Integration
A free test with instant, explained results. No account needed.
More HTTP Integration questions
- Which naming or modeling choice is strongest for timeouts and retries?
- What production risk should you worry about most if timeouts and retries is handled lazily?
- What is the healthiest performance judgment around timeouts and retries?
- If timeouts and retries fails in production, what handling philosophy is strongest?
- You cannot rewrite everything today. What is the best incremental improvement around timeouts and retries?
- Another engineer will maintain this code later. What choice helps the most around timeouts and retries?