System Resilience Vocabulary
Learn the vocabulary of system resilience engineering: fault tolerance, graceful degradation, circuit breaker behavior observed in chaos experiments, mean time between failures (MTBF), and how to discuss these concepts precisely.
0 / 37 completed
1 / 37
An engineer says: 'Our system is fault tolerant to dependency failures.' What does this mean?
Fault tolerance is not immunity to failure — it is the ability to continue operating when failures occur. It requires design choices: retries, circuit breakers, fallbacks, redundancy, and graceful degradation paths. In chaos experiments, fault tolerance is verified by injecting dependency failures and confirming the system continues serving users acceptably. 'Fault tolerant' systems have explicit, tested failure paths — not just hope that dependencies won't fail.
2 / 37
What is the difference between 'fault tolerance' and 'graceful degradation' in resilience vocabulary?
The distinction matters for setting expectations: 'fault tolerant to payment service failure' might mean the system serves all requests normally (using a fallback). 'Gracefully degrades when payment service fails' means the system continues running but the checkout feature returns a user-friendly error rather than crashing the whole application. Graceful degradation is often more realistic and valuable than full fault tolerance for complex systems.
3 / 37
In a chaos experiment report, an engineer writes: 'The circuit breaker opened after 10 consecutive 503 responses from the cache service, preventing cascade failure to the database.' What is being described?
Circuit breaker in action: the breaker monitors error rate or consecutive failures from a dependency. When the threshold is reached (here: 10 consecutive 503s), it 'opens' — rejecting calls to that dependency immediately (without waiting for timeouts), reducing load on the failing service and preventing cascade failures downstream. The chaos experiment verified that this mechanism triggers at the configured threshold under realistic conditions. This is a hypothesis confirmation.
4 / 37
A post-mortem states: 'Our MTBF for the search service under Black Friday load is 4 hours.' What does this communicate?
MTBF = total operating time / number of failures. An MTBF of 4 hours under peak load is a reliability planning input: if the Black Friday sale runs for 12 hours, expect approximately 3 failures. This drives decisions: Can we improve MTBF by fixing the root cause (e.g., a memory leak under high traffic)? Or do we accept the MTBF and invest in fast recovery (low MTTR) and transparent failover instead? Chaos experiments can help establish baseline MTBF under specific load conditions.
5 / 37
How do chaos engineering experiments help identify 'single points of failure' (SPOFs)?
SPOF discovery is one of chaos engineering's most valuable outputs: architectural diagrams often assume redundancy that was never verified to work. A chaos experiment that terminates one instance of a 'redundant' component and causes a complete outage reveals that the redundancy was not functioning (configuration error, no health check, wrong load balancer setting). SPOFs discovered in controlled chaos experiments are fixed before they cause real production incidents.
6 / 37
PR Description:
"Fix: Prevent cascading failures due to intermittent network issues with the external payment gateway. Implemented a circuit breaker to automatically halt requests to the gateway if it returns an error rate exceeding 95% for 30 seconds. Monitoring alerts have been configured."This question focuses on a practical application of circuit breakers. The
PR Description shows how the circuit breaker is actively *preventing* overload and cascading failures—a core function. While options A and B touch upon related concepts, they misrepresent the immediate purpose here: it's not about total outage tolerance but about managing transient dependency issues through a controlled shutdown. Option C highlights a crucial follow-up step (investigating the root cause) – resilience isn't just about reactive measures.7 / 37
Sarah: "Hey team, I'm deploying this new version of the API. We've added a circuit breaker to handle potential issues with our third-party authentication service. It should significantly improve system resilience."This scenario tests understanding of circuit breaker implementation in a practical context. A circuit breaker's primary function is to automatically stop requests to a failing dependency – in this case, the authentication service – when it detects a sustained period of errors. The key takeaway isn't just that it *should* improve resilience, but that it actively prevents cascading failures by interrupting the flow of traffic when a service becomes unavailable. Importantly, it doesn't guarantee immediate recovery; it simply provides a temporary pause to allow the failing service to recover.
8 / 37
git diff
Alex is implementing a circuit breaker pattern. This isn't about *guaranteeing* correct operation (that's fault tolerance), nor is it about bypassing the external service entirely – that would be masking the problem. Instead, a circuit breaker monitors the external service and *temporarily* stops requests when failures are detected, preventing the internal system from being overwhelmed or causing cascading failures. The 5-second trip threshold and 60-second open duration are key parameters of this pattern.
9 / 37
PR Description:
"Fix: Prevent cascading failures due to intermittent network issues with the external payment gateway. Implemented a circuit breaker to automatically halt requests to the gateway if it returns an error rate exceeding 95% for 30 seconds. Monitoring alerts have been configured."This question focuses on a practical application of circuit breakers. The
PR Description shows how the circuit breaker is actively *preventing* overload and cascading failures—a core function. While options A and B touch upon related concepts, they misrepresent the immediate purpose here: it's not about total outage tolerance but about managing transient dependency issues through a controlled shutdown. Option C highlights a crucial follow-up step (investigating the root cause) – resilience isn't just about reactive measures.10 / 37
Sarah: "Hey team, I'm deploying this new version of the API. We've added a circuit breaker to handle potential issues with our third-party authentication service. It should significantly improve system resilience."This scenario tests understanding of circuit breaker implementation in a practical context. A circuit breaker's primary function is to automatically stop requests to a failing dependency – in this case, the authentication service – when it detects a sustained period of errors. The key takeaway isn't just that it *should* improve resilience, but that it actively prevents cascading failures by interrupting the flow of traffic when a service becomes unavailable. Importantly, it doesn't guarantee immediate recovery; it simply provides a temporary pause to allow the failing service to recover.
11 / 37
git diff
Alex is implementing a circuit breaker pattern. This isn't about *guaranteeing* correct operation (that's fault tolerance), nor is it about bypassing the external service entirely – that would be masking the problem. Instead, a circuit breaker monitors the external service and *temporarily* stops requests when failures are detected, preventing the internal system from being overwhelmed or causing cascading failures. The 5-second trip threshold and 60-second open duration are key parameters of this pattern.
12 / 37
PR Description:
"Fix: Prevent cascading failures due to intermittent network issues with the external payment gateway. Implemented a circuit breaker to automatically halt requests to the gateway if it returns an error rate exceeding 95% for 30 seconds. Monitoring alerts have been configured."This question focuses on a practical application of circuit breakers. The
PR Description shows how the circuit breaker is actively *preventing* overload and cascading failures—a core function. While options A and B touch upon related concepts, they misrepresent the immediate purpose here: it's not about total outage tolerance but about managing transient dependency issues through a controlled shutdown. Option C highlights a crucial follow-up step (investigating the root cause) – resilience isn't just about reactive measures.13 / 37
Sarah: "Hey team, I'm deploying this new version of the API. We've added a circuit breaker to handle potential issues with our third-party authentication service. It should significantly improve system resilience."This scenario tests understanding of circuit breaker implementation in a practical context. A circuit breaker's primary function is to automatically stop requests to a failing dependency – in this case, the authentication service – when it detects a sustained period of errors. The key takeaway isn't just that it *should* improve resilience, but that it actively prevents cascading failures by interrupting the flow of traffic when a service becomes unavailable. Importantly, it doesn't guarantee immediate recovery; it simply provides a temporary pause to allow the failing service to recover.
14 / 37
git diff
Alex is implementing a circuit breaker pattern. This isn't about *guaranteeing* correct operation (that's fault tolerance), nor is it about bypassing the external service entirely – that would be masking the problem. Instead, a circuit breaker monitors the external service and *temporarily* stops requests when failures are detected, preventing the internal system from being overwhelmed or causing cascading failures. The 5-second trip threshold and 60-second open duration are key parameters of this pattern.
15 / 37
PR Description:
"Fix: Prevent cascading failures due to intermittent network issues with the external payment gateway. Implemented a circuit breaker to automatically halt requests to the gateway if it returns an error rate exceeding 95% for 30 seconds. Monitoring alerts have been configured."This question focuses on a practical application of circuit breakers. The
PR Description shows how the circuit breaker is actively *preventing* overload and cascading failures—a core function. While options A and B touch upon related concepts, they misrepresent the immediate purpose here: it's not about total outage tolerance but about managing transient dependency issues through a controlled shutdown. Option C highlights a crucial follow-up step (investigating the root cause) – resilience isn't just about reactive measures.16 / 37
Sarah: "Hey team, I'm deploying this new version of the API. We've added a circuit breaker to handle potential issues with our third-party authentication service. It should significantly improve system resilience."This scenario tests understanding of circuit breaker implementation in a practical context. A circuit breaker's primary function is to automatically stop requests to a failing dependency – in this case, the authentication service – when it detects a sustained period of errors. The key takeaway isn't just that it *should* improve resilience, but that it actively prevents cascading failures by interrupting the flow of traffic when a service becomes unavailable. Importantly, it doesn't guarantee immediate recovery; it simply provides a temporary pause to allow the failing service to recover.
17 / 37
git diff
Alex is implementing a circuit breaker pattern. This isn't about *guaranteeing* correct operation (that's fault tolerance), nor is it about bypassing the external service entirely – that would be masking the problem. Instead, a circuit breaker monitors the external service and *temporarily* stops requests when failures are detected, preventing the internal system from being overwhelmed or causing cascading failures. The 5-second trip threshold and 60-second open duration are key parameters of this pattern.
18 / 37
During a standup meeting, David says: "We've implemented a circuit breaker for the Kafka producer. It monitors queue depth and automatically throttles requests if it exceeds 10,000 messages per second to prevent overload.". What is David primarily describing?
David is explaining the core function of a circuit breaker: proactively limiting load to prevent overload. A circuit breaker doesn't directly address fault tolerance or MTBF but uses these concepts to achieve its goal. It's a specific implementation detail focused on throttling requests.
19 / 37
A Slack message from Maria reads: 'The team is investigating a spike in error rates for the user profile service. Initial analysis suggests a high volume of calls to a third-party API are causing timeouts and impacting our own database. We're considering implementing a circuit breaker to isolate this dependency'. What key concept is Maria addressing?
Maria's message directly refers to a circuit breaker as a solution. The situation describes a dependency that's causing problems, and the circuit breaker is designed to isolate this dependency by halting requests when it becomes unreliable. This is a classic use case for circuit breakers.
20 / 37
In a code review comment, John writes: 'I've added a retry mechanism with exponential backoff to the API calls to the payment processor. This should improve resilience against transient network issues and prevent service degradation'. What is John primarily focusing on?
John is describing fault tolerance through retry mechanisms and exponential backoff. This approach allows the system to gracefully handle temporary issues (like network glitches) without a complete failure. While rate limiting is related, it's not the primary focus here.
21 / 37
A PR description states: 'Implemented a circuit breaker around the external shipping service to mitigate potential delays due to high traffic. The breaker will automatically switch to a fallback mechanism if the shipping service is unresponsive for more than 5 seconds'. What metric is implicitly being considered when defining the '5 second' threshold?
The '5 second' threshold is directly related to the circuit breaker's trip time. It represents the duration after which the breaker will automatically switch to a fallback mechanism. This ensures rapid response to issues without prolonged downtime caused by a stuck breaker.
22 / 37
During a technical discussion, Emily says: 'We're aiming for an MTBF of 99.99% for the core microservice. To achieve this, we are employing circuit breakers and robust monitoring to quickly detect and isolate issues.' What is Emily's primary strategy?
Emily is explicitly stating that circuit breakers are a *key component* of her strategy for achieving a high MTBF. Circuit breakers contribute directly to fault tolerance and rapid isolation of issues, which are crucial factors in improving system reliability—the goal of an MTBF.
23 / 37
During a standup meeting, David says: "We've implemented a circuit breaker for the Kafka producer. It monitors queue depth and automatically throttles requests if it exceeds 10,000 messages per second to prevent overload.". What is David primarily describing?
David is explaining the core function of a circuit breaker: proactively limiting load to prevent overload. A circuit breaker doesn't directly address fault tolerance or MTBF but uses these concepts to achieve its goal. It's a specific implementation detail focused on throttling requests.
24 / 37
A Slack message from Maria reads: 'The team is investigating a spike in error rates for the user profile service. Initial analysis suggests a high volume of calls to a third-party API are causing timeouts and impacting our own database. We're considering implementing a circuit breaker to isolate this dependency'. What key concept is Maria addressing?
Maria's message directly refers to a circuit breaker as a solution. The situation describes a dependency that's causing problems, and the circuit breaker is designed to isolate this dependency by halting requests when it becomes unreliable. This is a classic use case for circuit breakers.
25 / 37
In a code review comment, John writes: 'I've added a retry mechanism with exponential backoff to the API calls to the payment processor. This should improve resilience against transient network issues and prevent service degradation'. What is John primarily focusing on?
John is describing fault tolerance through retry mechanisms and exponential backoff. This approach allows the system to gracefully handle temporary issues (like network glitches) without a complete failure. While rate limiting is related, it's not the primary focus here.
26 / 37
A PR description states: 'Implemented a circuit breaker around the external shipping service to mitigate potential delays due to high traffic. The breaker will automatically switch to a fallback mechanism if the shipping service is unresponsive for more than 5 seconds'. What metric is implicitly being considered when defining the '5 second' threshold?
The '5 second' threshold is directly related to the circuit breaker's trip time. It represents the duration after which the breaker will automatically switch to a fallback mechanism. This ensures rapid response to issues without prolonged downtime caused by a stuck breaker.
27 / 37
During a technical discussion, Emily says: 'We're aiming for an MTBF of 99.99% for the core microservice. To achieve this, we are employing circuit breakers and robust monitoring to quickly detect and isolate issues.' What is Emily's primary strategy?
Emily is explicitly stating that circuit breakers are a *key component* of her strategy for achieving a high MTBF. Circuit breakers contribute directly to fault tolerance and rapid isolation of issues, which are crucial factors in improving system reliability—the goal of an MTBF.
28 / 37
During a standup meeting, David says: "We've implemented a circuit breaker for the Kafka producer. It monitors queue depth and automatically throttles requests if it exceeds 10,000 messages per second to prevent overload.". What is David primarily describing?
David is explaining the core function of a circuit breaker: proactively limiting load to prevent overload. A circuit breaker doesn't directly address fault tolerance or MTBF but uses these concepts to achieve its goal. It's a specific implementation detail focused on throttling requests.
29 / 37
A Slack message from Maria reads: 'The team is investigating a spike in error rates for the user profile service. Initial analysis suggests a high volume of calls to a third-party API are causing timeouts and impacting our own database. We're considering implementing a circuit breaker to isolate this dependency'. What key concept is Maria addressing?
Maria's message directly refers to a circuit breaker as a solution. The situation describes a dependency that's causing problems, and the circuit breaker is designed to isolate this dependency by halting requests when it becomes unreliable. This is a classic use case for circuit breakers.
30 / 37
In a code review comment, John writes: 'I've added a retry mechanism with exponential backoff to the API calls to the payment processor. This should improve resilience against transient network issues and prevent service degradation'. What is John primarily focusing on?
John is describing fault tolerance through retry mechanisms and exponential backoff. This approach allows the system to gracefully handle temporary issues (like network glitches) without a complete failure. While rate limiting is related, it's not the primary focus here.
31 / 37
A PR description states: 'Implemented a circuit breaker around the external shipping service to mitigate potential delays due to high traffic. The breaker will automatically switch to a fallback mechanism if the shipping service is unresponsive for more than 5 seconds'. What metric is implicitly being considered when defining the '5 second' threshold?
The '5 second' threshold is directly related to the circuit breaker's trip time. It represents the duration after which the breaker will automatically switch to a fallback mechanism. This ensures rapid response to issues without prolonged downtime caused by a stuck breaker.
32 / 37
During a technical discussion, Emily says: 'We're aiming for an MTBF of 99.99% for the core microservice. To achieve this, we are employing circuit breakers and robust monitoring to quickly detect and isolate issues.' What is Emily's primary strategy?
Emily is explicitly stating that circuit breakers are a *key component* of her strategy for achieving a high MTBF. Circuit breakers contribute directly to fault tolerance and rapid isolation of issues, which are crucial factors in improving system reliability—the goal of an MTBF.
33 / 37
During a standup meeting, David says: "We've implemented a circuit breaker for the Kafka producer. It monitors queue depth and automatically throttles requests if it exceeds 10,000 messages per second to prevent overload.". What is David primarily describing?
David is explaining the core function of a circuit breaker: proactively limiting load to prevent overload. A circuit breaker doesn't directly address fault tolerance or MTBF but uses these concepts to achieve its goal. It's a specific implementation detail focused on throttling requests.
34 / 37
A Slack message from Maria reads: 'The team is investigating a spike in error rates for the user profile service. Initial analysis suggests a high volume of calls to a third-party API are causing timeouts and impacting our own database. We're considering implementing a circuit breaker to isolate this dependency'. What key concept is Maria addressing?
Maria's message directly refers to a circuit breaker as a solution. The situation describes a dependency that's causing problems, and the circuit breaker is designed to isolate this dependency by halting requests when it becomes unreliable. This is a classic use case for circuit breakers.
35 / 37
In a code review comment, John writes: 'I've added a retry mechanism with exponential backoff to the API calls to the payment processor. This should improve resilience against transient network issues and prevent service degradation'. What is John primarily focusing on?
John is describing fault tolerance through retry mechanisms and exponential backoff. This approach allows the system to gracefully handle temporary issues (like network glitches) without a complete failure. While rate limiting is related, it's not the primary focus here.
36 / 37
A PR description states: 'Implemented a circuit breaker around the external shipping service to mitigate potential delays due to high traffic. The breaker will automatically switch to a fallback mechanism if the shipping service is unresponsive for more than 5 seconds'. What metric is implicitly being considered when defining the '5 second' threshold?
The '5 second' threshold is directly related to the circuit breaker's trip time. It represents the duration after which the breaker will automatically switch to a fallback mechanism. This ensures rapid response to issues without prolonged downtime caused by a stuck breaker.
37 / 37
During a technical discussion, Emily says: 'We're aiming for an MTBF of 99.99% for the core microservice. To achieve this, we are employing circuit breakers and robust monitoring to quickly detect and isolate issues.' What is Emily's primary strategy?
Emily is explicitly stating that circuit breakers are a *key component* of her strategy for achieving a high MTBF. Circuit breakers contribute directly to fault tolerance and rapid isolation of issues, which are crucial factors in improving system reliability—the goal of an MTBF.
Frequently Asked Questions
What will I practice in "System Resilience Vocabulary — Fault Tolerance, Circuit Breaker, MTBF"?
This is a Chaos Engineering exercise set. It walks through 37 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 37 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.