HTTP Integration · interview question

What is the healthiest performance judgment around timeouts and retries?

Multiple choiceMediumchapter-12-curatedpremiumhttp-integrationtimeouts-and-retries

python

def call_partner(client: httpx.Client) -> dict:
    response = client.get("/orders", timeout=5.0)
    response.raise_for_status()
    return response.json()

Keep timeouts and retries implicit so the script stays short and hope the next engineer infers the rule.Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Solve the symptom with comments only and avoid changing the code shape around timeouts and retries.

Answer and explanation

Correct answer

B. Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.

Why

Premature optimization is usually weaker than targeted optimization backed by measurement.

Test yourself on HTTP Integration

A free test with instant, explained results. No account needed.

Start free test

All HTTP Integration questions →

What is the healthiest performance judgment around timeouts and retries?

Correct answer

Why

More HTTP Integration questions