HTTP Integration · interview question
What is the clearest sign that code around 429s and backoff should be refactored?
Multiple choiceHardchapter-12-curatedpremiumhttp-integration429s-and-backoff
Answer and explanation
Correct answer
C. When the rule is no longer easy to trace, explain, or change without breaking nearby behavior.
Why
A refactor is justified when the code stops communicating its intent. Back off deliberately and make the retry policy visible when the remote service is telling you to slow down.
Test yourself on HTTP Integration
A free test with instant, explained results. No account needed.
More HTTP Integration questions
- Which explanation would best help the team align on pagination and rate limits?
- A bug appears around basic http clients. What is the strongest first debugging move?
- Which response shows the healthiest evidence-first mindset around json mapping?
- Which judgment is strongest when choosing a data shape for 429s and backoff?
- Which option treats basic http clients as an engineering policy decision instead of a syntax trick?
- What does a strong engineer do when reasoning through pagination and rate limits code?