Resilience Patterns — Vocabulary
Learn vocabulary for retry with backoff, jitter, timeout, bulkhead pattern, fallback mechanisms, degraded mode, and service health indicators.
0 / 45 completed
1 / 45
What is 'exponential backoff with jitter' in resilience pattern vocabulary?
Exponential backoff: wait 1s, 2s, 4s, 8s... between retries (doubles each time). Jitter: add random delay (e.g., wait = min(cap, base * 2^attempt) * random(0.5, 1.5)). Without jitter, all clients that hit the same failure retry at the same time ('thundering herd'), re-overloading the recovering service. AWS, Google Cloud, and most SDK retry policies recommend 'full jitter' or 'decorrelated jitter.'
2 / 45
What is the 'bulkhead pattern' in resilience vocabulary?
Bulkhead (from ship design: watertight compartments prevent sinking if one compartment floods): in software, allocate separate thread pools or semaphores per downstream service. If Service A becomes slow and exhausts its thread pool, calls to Service B and Service C use their own separate pools and remain unaffected. Netflix Hystrix popularized this. Prevents 'slow dependency cascading to full service failure' — one of the most common distributed systems failure modes.
3 / 45
What is a 'fallback mechanism' in resilience pattern vocabulary?
Fallback strategies: (1) Cached response — return the last successful result (acceptable if data can be slightly stale). (2) Default value — return a safe default ('0 items in cart' instead of an error). (3) Stub/static content — return a simplified response. (4) Fail fast — return an immediate error rather than a slow timeout. The key vocabulary: 'graceful degradation' means the user still gets partial functionality, not a hard error.
4 / 45
What is 'degraded mode' in resilience vocabulary?
Degraded mode (graceful degradation) vocabulary: 'We are operating in degraded mode — recommendation engine is unavailable, but checkout and order placement remain fully functional.' Key design principle: identify which features are critical (checkout) vs. non-critical (personalized recommendations, product reviews). When dependencies for non-critical features fail, disable those features instead of failing the entire request. Feature flags enable programmatic degraded mode.
5 / 45
What is a 'service health indicator' (SHI) in resilience and chaos engineering vocabulary?
Service health indicators go beyond 'is the process running?' They measure business-meaningful signals: 'order completion rate > 99%' (not just 'HTTP 200 rate'), 'payment processing latency p99 < 400ms' (not just 'server is reachable'). SHIs are inputs to chaos experiment steady-state definitions, SLO burn rate alerts, and automated circuit breakers. Choosing the right SHIs is itself a resilience engineering discipline.
6 / 45
PR Description:
"Fixes a failing deployment. Initial investigation suggests intermittent network issues impacting the external API call to PaymentGatewayService. Implementing circuit breaker with 30s timeout and retry attempts (exponential backoff). Monitoring metrics will be crucial."This response correctly identifies the use of a circuit breaker as demonstrating an understanding of resilience patterns. The key is recognizing that exponential backoff with jitter is specifically designed for *transient* network issues – short-lived failures that are common in distributed systems. Options A and C misunderstand the purpose of a circuit breaker; rate limiting addresses different problems, and simply blaming the service misses the point of proactive fault tolerance. Option D highlights an important consideration (details about retry policy), but doesn't capture the core concept.
7 / 45
This scenario highlights the importance of initial triage when encountering intermittent errors. Option A is incorrect because a simple retry loop without understanding the underlying problem won't resolve the 'TimeoutException'. Option B is also flawed; simply increasing connection pools doesn't address potential failures on the AnalyticsBackend. Option D, deploying immediately with aggressive logging, is premature and could mask critical information. Option 2 correctly emphasizes investigating the AnalyticsBackend first – a crucial step before implementing more complex resilience patterns like circuit breakers.
8 / 45
The correct answer addresses the core issue of resilience: anticipating failures. Increasing the timeout value is a common, though sometimes insufficient, tactic. A fallback mechanism (option 3) is significantly better because it actively handles the degraded state – maintaining alerting functionality even when the primary service fails. Options 1 and 4 are incorrect; aggressive retries can exacerbate issues, and simply ignoring an unresponsive service isn't a resilient solution. This demonstrates understanding that resilience requires proactive planning for potential disruptions.
9 / 45
The correct answer is exponential backoff with jitter. This pattern acknowledges that intermittent failures are common and allows for retries with increasing delays, preventing overwhelming the failing service. Options A and B introduce synchronous calls or timeouts which don't account for transient issues; they can actually exacerbate the problem. Option C simply masks the underlying issue and doesn't address resilience. Option D provides visibility but doesn't actively manage the failure – it's a diagnostic step, not a solution.
10 / 45
OrderProcessingService is intermittently failing when updating inventory in the InventoryService. Logs show slow response times from InventoryService, and no retry logic exists. Which of the following strategies would best address this situation, prioritizing resilience? Exponential backoff with jitter is ideal here because it dynamically adjusts retry attempts based on network conditions and
InventoryService's availability – preventing overwhelming the service during periods of congestion or temporary unavailability. The other options are less effective: synchronous calls could exacerbate timeouts, escalating to Operations might delay a more targeted solution, and increasing the timeout statically won't account for intermittent problems.11 / 45
PR Description:
"Fixes a failing deployment. Initial investigation suggests intermittent network issues impacting the external API call to PaymentGatewayService. Implementing circuit breaker with 30s timeout and retry attempts (exponential backoff). Monitoring metrics will be crucial."This response correctly identifies the use of a circuit breaker as demonstrating an understanding of resilience patterns. The key is recognizing that exponential backoff with jitter is specifically designed for *transient* network issues – short-lived failures that are common in distributed systems. Options A and C misunderstand the purpose of a circuit breaker; rate limiting addresses different problems, and simply blaming the service misses the point of proactive fault tolerance. Option D highlights an important consideration (details about retry policy), but doesn't capture the core concept.
12 / 45
This scenario highlights the importance of initial triage when encountering intermittent errors. Option A is incorrect because a simple retry loop without understanding the underlying problem won't resolve the 'TimeoutException'. Option B is also flawed; simply increasing connection pools doesn't address potential failures on the AnalyticsBackend. Option D, deploying immediately with aggressive logging, is premature and could mask critical information. Option 2 correctly emphasizes investigating the AnalyticsBackend first – a crucial step before implementing more complex resilience patterns like circuit breakers.
13 / 45
The correct answer addresses the core issue of resilience: anticipating failures. Increasing the timeout value is a common, though sometimes insufficient, tactic. A fallback mechanism (option 3) is significantly better because it actively handles the degraded state – maintaining alerting functionality even when the primary service fails. Options 1 and 4 are incorrect; aggressive retries can exacerbate issues, and simply ignoring an unresponsive service isn't a resilient solution. This demonstrates understanding that resilience requires proactive planning for potential disruptions.
14 / 45
The correct answer is exponential backoff with jitter. This pattern acknowledges that intermittent failures are common and allows for retries with increasing delays, preventing overwhelming the failing service. Options A and B introduce synchronous calls or timeouts which don't account for transient issues; they can actually exacerbate the problem. Option C simply masks the underlying issue and doesn't address resilience. Option D provides visibility but doesn't actively manage the failure – it's a diagnostic step, not a solution.
15 / 45
OrderProcessingService is intermittently failing when updating inventory in the InventoryService. Logs show slow response times from InventoryService, and no retry logic exists. Which of the following strategies would best address this situation, prioritizing resilience? Exponential backoff with jitter is ideal here because it dynamically adjusts retry attempts based on network conditions and
InventoryService's availability – preventing overwhelming the service during periods of congestion or temporary unavailability. The other options are less effective: synchronous calls could exacerbate timeouts, escalating to Operations might delay a more targeted solution, and increasing the timeout statically won't account for intermittent problems.16 / 45
PR Description:
"Fixes a failing deployment. Initial investigation suggests intermittent network issues impacting the external API call to PaymentGatewayService. Implementing circuit breaker with 30s timeout and retry attempts (exponential backoff). Monitoring metrics will be crucial."This response correctly identifies the use of a circuit breaker as demonstrating an understanding of resilience patterns. The key is recognizing that exponential backoff with jitter is specifically designed for *transient* network issues – short-lived failures that are common in distributed systems. Options A and C misunderstand the purpose of a circuit breaker; rate limiting addresses different problems, and simply blaming the service misses the point of proactive fault tolerance. Option D highlights an important consideration (details about retry policy), but doesn't capture the core concept.
17 / 45
This scenario highlights the importance of initial triage when encountering intermittent errors. Option A is incorrect because a simple retry loop without understanding the underlying problem won't resolve the 'TimeoutException'. Option B is also flawed; simply increasing connection pools doesn't address potential failures on the AnalyticsBackend. Option D, deploying immediately with aggressive logging, is premature and could mask critical information. Option 2 correctly emphasizes investigating the AnalyticsBackend first – a crucial step before implementing more complex resilience patterns like circuit breakers.
18 / 45
The correct answer addresses the core issue of resilience: anticipating failures. Increasing the timeout value is a common, though sometimes insufficient, tactic. A fallback mechanism (option 3) is significantly better because it actively handles the degraded state – maintaining alerting functionality even when the primary service fails. Options 1 and 4 are incorrect; aggressive retries can exacerbate issues, and simply ignoring an unresponsive service isn't a resilient solution. This demonstrates understanding that resilience requires proactive planning for potential disruptions.
19 / 45
The correct answer is exponential backoff with jitter. This pattern acknowledges that intermittent failures are common and allows for retries with increasing delays, preventing overwhelming the failing service. Options A and B introduce synchronous calls or timeouts which don't account for transient issues; they can actually exacerbate the problem. Option C simply masks the underlying issue and doesn't address resilience. Option D provides visibility but doesn't actively manage the failure – it's a diagnostic step, not a solution.
20 / 45
OrderProcessingService is intermittently failing when updating inventory in the InventoryService. Logs show slow response times from InventoryService, and no retry logic exists. Which of the following strategies would best address this situation, prioritizing resilience? Exponential backoff with jitter is ideal here because it dynamically adjusts retry attempts based on network conditions and
InventoryService's availability – preventing overwhelming the service during periods of congestion or temporary unavailability. The other options are less effective: synchronous calls could exacerbate timeouts, escalating to Operations might delay a more targeted solution, and increasing the timeout statically won't account for intermittent problems.21 / 45
PR Description:
"Fixes a failing deployment. Initial investigation suggests intermittent network issues impacting the external API call to PaymentGatewayService. Implementing circuit breaker with 30s timeout and retry attempts (exponential backoff). Monitoring metrics will be crucial."This response correctly identifies the use of a circuit breaker as demonstrating an understanding of resilience patterns. The key is recognizing that exponential backoff with jitter is specifically designed for *transient* network issues – short-lived failures that are common in distributed systems. Options A and C misunderstand the purpose of a circuit breaker; rate limiting addresses different problems, and simply blaming the service misses the point of proactive fault tolerance. Option D highlights an important consideration (details about retry policy), but doesn't capture the core concept.
22 / 45
This scenario highlights the importance of initial triage when encountering intermittent errors. Option A is incorrect because a simple retry loop without understanding the underlying problem won't resolve the 'TimeoutException'. Option B is also flawed; simply increasing connection pools doesn't address potential failures on the AnalyticsBackend. Option D, deploying immediately with aggressive logging, is premature and could mask critical information. Option 2 correctly emphasizes investigating the AnalyticsBackend first – a crucial step before implementing more complex resilience patterns like circuit breakers.
23 / 45
The correct answer addresses the core issue of resilience: anticipating failures. Increasing the timeout value is a common, though sometimes insufficient, tactic. A fallback mechanism (option 3) is significantly better because it actively handles the degraded state – maintaining alerting functionality even when the primary service fails. Options 1 and 4 are incorrect; aggressive retries can exacerbate issues, and simply ignoring an unresponsive service isn't a resilient solution. This demonstrates understanding that resilience requires proactive planning for potential disruptions.
24 / 45
The correct answer is exponential backoff with jitter. This pattern acknowledges that intermittent failures are common and allows for retries with increasing delays, preventing overwhelming the failing service. Options A and B introduce synchronous calls or timeouts which don't account for transient issues; they can actually exacerbate the problem. Option C simply masks the underlying issue and doesn't address resilience. Option D provides visibility but doesn't actively manage the failure – it's a diagnostic step, not a solution.
25 / 45
OrderProcessingService is intermittently failing when updating inventory in the InventoryService. Logs show slow response times from InventoryService, and no retry logic exists. Which of the following strategies would best address this situation, prioritizing resilience? Exponential backoff with jitter is ideal here because it dynamically adjusts retry attempts based on network conditions and
InventoryService's availability – preventing overwhelming the service during periods of congestion or temporary unavailability. The other options are less effective: synchronous calls could exacerbate timeouts, escalating to Operations might delay a more targeted solution, and increasing the timeout statically won't account for intermittent problems.26 / 45
PR Description:
"Fixes a failing deployment. Initial investigation suggests intermittent network issues impacting the external API call to PaymentGatewayService. Implementing circuit breaker with 30s timeout and retry attempts (exponential backoff). Monitoring metrics will be crucial."This response correctly identifies the use of a circuit breaker as demonstrating an understanding of resilience patterns. The key is recognizing that exponential backoff with jitter is specifically designed for *transient* network issues – short-lived failures that are common in distributed systems. Options A and C misunderstand the purpose of a circuit breaker; rate limiting addresses different problems, and simply blaming the service misses the point of proactive fault tolerance. Option D highlights an important consideration (details about retry policy), but doesn't capture the core concept.
27 / 45
This scenario highlights the importance of initial triage when encountering intermittent errors. Option A is incorrect because a simple retry loop without understanding the underlying problem won't resolve the 'TimeoutException'. Option B is also flawed; simply increasing connection pools doesn't address potential failures on the AnalyticsBackend. Option D, deploying immediately with aggressive logging, is premature and could mask critical information. Option 2 correctly emphasizes investigating the AnalyticsBackend first – a crucial step before implementing more complex resilience patterns like circuit breakers.
28 / 45
The correct answer addresses the core issue of resilience: anticipating failures. Increasing the timeout value is a common, though sometimes insufficient, tactic. A fallback mechanism (option 3) is significantly better because it actively handles the degraded state – maintaining alerting functionality even when the primary service fails. Options 1 and 4 are incorrect; aggressive retries can exacerbate issues, and simply ignoring an unresponsive service isn't a resilient solution. This demonstrates understanding that resilience requires proactive planning for potential disruptions.
29 / 45
The correct answer is exponential backoff with jitter. This pattern acknowledges that intermittent failures are common and allows for retries with increasing delays, preventing overwhelming the failing service. Options A and B introduce synchronous calls or timeouts which don't account for transient issues; they can actually exacerbate the problem. Option C simply masks the underlying issue and doesn't address resilience. Option D provides visibility but doesn't actively manage the failure – it's a diagnostic step, not a solution.
30 / 45
OrderProcessingService is intermittently failing when updating inventory in the InventoryService. Logs show slow response times from InventoryService, and no retry logic exists. Which of the following strategies would best address this situation, prioritizing resilience? Exponential backoff with jitter is ideal here because it dynamically adjusts retry attempts based on network conditions and
InventoryService's availability – preventing overwhelming the service during periods of congestion or temporary unavailability. The other options are less effective: synchronous calls could exacerbate timeouts, escalating to Operations might delay a more targeted solution, and increasing the timeout statically won't account for intermittent problems.31 / 45
PR Description:
"Fixes a failing deployment. Initial investigation suggests intermittent network issues impacting the external API call to PaymentGatewayService. Implementing circuit breaker with 30s timeout and retry attempts (exponential backoff). Monitoring metrics will be crucial."This response correctly identifies the use of a circuit breaker as demonstrating an understanding of resilience patterns. The key is recognizing that exponential backoff with jitter is specifically designed for *transient* network issues – short-lived failures that are common in distributed systems. Options A and C misunderstand the purpose of a circuit breaker; rate limiting addresses different problems, and simply blaming the service misses the point of proactive fault tolerance. Option D highlights an important consideration (details about retry policy), but doesn't capture the core concept.
32 / 45
This scenario highlights the importance of initial triage when encountering intermittent errors. Option A is incorrect because a simple retry loop without understanding the underlying problem won't resolve the 'TimeoutException'. Option B is also flawed; simply increasing connection pools doesn't address potential failures on the AnalyticsBackend. Option D, deploying immediately with aggressive logging, is premature and could mask critical information. Option 2 correctly emphasizes investigating the AnalyticsBackend first – a crucial step before implementing more complex resilience patterns like circuit breakers.
33 / 45
The correct answer addresses the core issue of resilience: anticipating failures. Increasing the timeout value is a common, though sometimes insufficient, tactic. A fallback mechanism (option 3) is significantly better because it actively handles the degraded state – maintaining alerting functionality even when the primary service fails. Options 1 and 4 are incorrect; aggressive retries can exacerbate issues, and simply ignoring an unresponsive service isn't a resilient solution. This demonstrates understanding that resilience requires proactive planning for potential disruptions.
34 / 45
The correct answer is exponential backoff with jitter. This pattern acknowledges that intermittent failures are common and allows for retries with increasing delays, preventing overwhelming the failing service. Options A and B introduce synchronous calls or timeouts which don't account for transient issues; they can actually exacerbate the problem. Option C simply masks the underlying issue and doesn't address resilience. Option D provides visibility but doesn't actively manage the failure – it's a diagnostic step, not a solution.
35 / 45
OrderProcessingService is intermittently failing when updating inventory in the InventoryService. Logs show slow response times from InventoryService, and no retry logic exists. Which of the following strategies would best address this situation, prioritizing resilience? Exponential backoff with jitter is ideal here because it dynamically adjusts retry attempts based on network conditions and
InventoryService's availability – preventing overwhelming the service during periods of congestion or temporary unavailability. The other options are less effective: synchronous calls could exacerbate timeouts, escalating to Operations might delay a more targeted solution, and increasing the timeout statically won't account for intermittent problems.36 / 45
PR Description:
"Fixes a failing deployment. Initial investigation suggests intermittent network issues impacting the external API call to PaymentGatewayService. Implementing circuit breaker with 30s timeout and retry attempts (exponential backoff). Monitoring metrics will be crucial."This response correctly identifies the use of a circuit breaker as demonstrating an understanding of resilience patterns. The key is recognizing that exponential backoff with jitter is specifically designed for *transient* network issues – short-lived failures that are common in distributed systems. Options A and C misunderstand the purpose of a circuit breaker; rate limiting addresses different problems, and simply blaming the service misses the point of proactive fault tolerance. Option D highlights an important consideration (details about retry policy), but doesn't capture the core concept.
37 / 45
This scenario highlights the importance of initial triage when encountering intermittent errors. Option A is incorrect because a simple retry loop without understanding the underlying problem won't resolve the 'TimeoutException'. Option B is also flawed; simply increasing connection pools doesn't address potential failures on the AnalyticsBackend. Option D, deploying immediately with aggressive logging, is premature and could mask critical information. Option 2 correctly emphasizes investigating the AnalyticsBackend first – a crucial step before implementing more complex resilience patterns like circuit breakers.
38 / 45
The correct answer addresses the core issue of resilience: anticipating failures. Increasing the timeout value is a common, though sometimes insufficient, tactic. A fallback mechanism (option 3) is significantly better because it actively handles the degraded state – maintaining alerting functionality even when the primary service fails. Options 1 and 4 are incorrect; aggressive retries can exacerbate issues, and simply ignoring an unresponsive service isn't a resilient solution. This demonstrates understanding that resilience requires proactive planning for potential disruptions.
39 / 45
The correct answer is exponential backoff with jitter. This pattern acknowledges that intermittent failures are common and allows for retries with increasing delays, preventing overwhelming the failing service. Options A and B introduce synchronous calls or timeouts which don't account for transient issues; they can actually exacerbate the problem. Option C simply masks the underlying issue and doesn't address resilience. Option D provides visibility but doesn't actively manage the failure – it's a diagnostic step, not a solution.
40 / 45
OrderProcessingService is intermittently failing when updating inventory in the InventoryService. Logs show slow response times from InventoryService, and no retry logic exists. Which of the following strategies would best address this situation, prioritizing resilience? Exponential backoff with jitter is ideal here because it dynamically adjusts retry attempts based on network conditions and
InventoryService's availability – preventing overwhelming the service during periods of congestion or temporary unavailability. The other options are less effective: synchronous calls could exacerbate timeouts, escalating to Operations might delay a more targeted solution, and increasing the timeout statically won't account for intermittent problems.41 / 45
PR Description:
"Fixes a failing deployment. Initial investigation suggests intermittent network issues impacting the external API call to PaymentGatewayService. Implementing circuit breaker with 30s timeout and retry attempts (exponential backoff). Monitoring metrics will be crucial."This response correctly identifies the use of a circuit breaker as demonstrating an understanding of resilience patterns. The key is recognizing that exponential backoff with jitter is specifically designed for *transient* network issues – short-lived failures that are common in distributed systems. Options A and C misunderstand the purpose of a circuit breaker; rate limiting addresses different problems, and simply blaming the service misses the point of proactive fault tolerance. Option D highlights an important consideration (details about retry policy), but doesn't capture the core concept.
42 / 45
This scenario highlights the importance of initial triage when encountering intermittent errors. Option A is incorrect because a simple retry loop without understanding the underlying problem won't resolve the 'TimeoutException'. Option B is also flawed; simply increasing connection pools doesn't address potential failures on the AnalyticsBackend. Option D, deploying immediately with aggressive logging, is premature and could mask critical information. Option 2 correctly emphasizes investigating the AnalyticsBackend first – a crucial step before implementing more complex resilience patterns like circuit breakers.
43 / 45
The correct answer addresses the core issue of resilience: anticipating failures. Increasing the timeout value is a common, though sometimes insufficient, tactic. A fallback mechanism (option 3) is significantly better because it actively handles the degraded state – maintaining alerting functionality even when the primary service fails. Options 1 and 4 are incorrect; aggressive retries can exacerbate issues, and simply ignoring an unresponsive service isn't a resilient solution. This demonstrates understanding that resilience requires proactive planning for potential disruptions.
44 / 45
The correct answer is exponential backoff with jitter. This pattern acknowledges that intermittent failures are common and allows for retries with increasing delays, preventing overwhelming the failing service. Options A and B introduce synchronous calls or timeouts which don't account for transient issues; they can actually exacerbate the problem. Option C simply masks the underlying issue and doesn't address resilience. Option D provides visibility but doesn't actively manage the failure – it's a diagnostic step, not a solution.
45 / 45
OrderProcessingService is intermittently failing when updating inventory in the InventoryService. Logs show slow response times from InventoryService, and no retry logic exists. Which of the following strategies would best address this situation, prioritizing resilience? Exponential backoff with jitter is ideal here because it dynamically adjusts retry attempts based on network conditions and
InventoryService's availability – preventing overwhelming the service during periods of congestion or temporary unavailability. The other options are less effective: synchronous calls could exacerbate timeouts, escalating to Operations might delay a more targeted solution, and increasing the timeout statically won't account for intermittent problems.Frequently Asked Questions
What will I practice in "Resilience Patterns — Vocabulary"?
This is a Chaos Engineering exercise set. It walks through 45 scenario-based multiple-choice questions built around real usage of Chaos Engineering terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 45 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the Chaos Engineering vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Chaos Engineering exercises?
See the Chaos Engineering exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — Chaos Engineering vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.