QuizzesTimeouts & Deadline Propagation — Concept Check
intermediate
microservices

Timeouts & Deadline Propagation — Concept Check

Questions on Timeouts & Deadline Propagation. Always set read/connect timeouts on HTTP clients; propagate deadlines through call chains so that downstream work is abandoned when the upstream caller has given up.

8 minutes 8 questions Pass at 70%
Time Limit
8 minutes - timer starts when you begin
Change Answers Freely
Revisit and change any answer before submitting
Full Review After Submit
Correct answers and explanations shown for every question
Auto-submit on timeout
Quiz submits automatically when time runs out

Questions in this quiz

8 questions on Timeouts & Deadline Propagation — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.A service you manage is experiencing cascading failures due to a slow downstream service. What is the most effective immediate action?

    • ASwitch to a different protocol like gRPC
    • BSet a short connect timeout and a read timeout based on normal p99 latency
    • CIncrease the thread pool size to handle more requests
    • DDisable timeouts to allow more time for responses
  2. 2.Your HTTP client is configured with a connect timeout of 30 seconds. What is a likely consequence of this setting?

    • AImproved resilience to network issues
    • BReduced load on the thread pool
    • CIncreased risk of cascading failures
    • DFaster recovery from service outages
  3. 3.When propagating deadlines in a call chain, what should be done at each service hop?

    • ASubtract elapsed time from the remaining deadline
    • BIgnore the deadline and set local timeouts
    • CReset the deadline to the original value
    • DExtend the deadline to accommodate processing time
  4. 4.A developer sets a read timeout of 30 seconds for a service that usually responds in 200 ms. What is the likely impact during an outage?

    • AThe service will automatically scale to handle load
    • BThe service will handle requests more efficiently
    • CTimeouts will prevent any request failures
    • DThreads will pile up, leading to resource exhaustion
  5. 5.What is the purpose of using a custom X-Request-Deadline header in HTTP services?

    • ATo log the request processing time for auditing
    • BTo ensure requests are retried automatically
    • CTo propagate the remaining time budget through the call chain
    • DTo increase the timeout for downstream services
  6. 6.In a distributed system, why is it important to combine timeouts with circuit breakers?

    • ATo ensure all services have the same timeout settings
    • BTo allow more time for slow services to respond
    • CTo fail fast when a service consistently times out
    • DTo prevent any service from being called during high load
  7. 7.A service chain A→B→C has each service set with a 10-second timeout. What is the potential issue with this configuration?

    • AThe overall system will be more resilient
    • BEach service will timeout too quickly
    • CThe call chain will automatically balance timeouts
    • DThe total call chain can take up to 30 seconds
  8. 8.What is the role of a circuit breaker in a microservices architecture?

    • ATo prevent repeated failures by stopping requests temporarily
    • BTo ensure all requests are processed in order
    • CTo increase the timeout duration during high load
    • DTo log errors for later analysis