Retry Pattern — Concept Check
Questions on Retry Pattern. Transient failures are retried with exponential back-off and jitter; combine with idempotency on the server side to avoid duplicate effects.
Questions in this quiz
8 questions on Retry Pattern — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A service using Resilience4j experiences frequent 503 errors. What should be configured to prevent retry storms?
- AIncrease max retry attempts
- BDisable exponential backoff
- CRetry on all 5xx errors
- DEnable circuit breaker with retries
2.Your system retries a POST request without an idempotency key. What is a likely consequence?
- AIncreased server load
- BFaster recovery from failures
- CDuplicate operations
- DReduced latency
3.In a Spring WebClient setup, which status code should not trigger a retry?
- A500 Internal Server Error
- B404 Not Found
- C503 Service Unavailable
- D502 Bad Gateway
4.A service is set to retry with exponential backoff. What is the initial wait time if configured with a 500ms wait-duration and a multiplier of 2?
- A500ms
- B1s
- C4s
- D2s
5.What is the role of jitter in retry mechanisms?
- ATo desynchronize concurrent retries
- BTo synchronize retries
- CTo reduce retry attempts
- DTo increase server load
6.Why might retrying a 401 Unauthorized error be problematic?
- AIt is necessary for idempotent requests
- BIt could fix credential issues
- CIt may cause duplicate operations
- DIt wastes resources on non-transient errors
7.What happens if retries are applied to non-idempotent operations?
- AFaster error recovery
- BReduced server load
- CImproved reliability
- DPotential duplicate effects
8.How does the retry pattern handle transient errors like connection resets?
- ARetries with exponential backoff and jitter
- BImmediately fails the operation
- CRetries on all errors
- DSurfaces the error to the caller