GameDay — Vocabulary and Communication Language
Learn vocabulary for planning and communicating chaos GameDay exercises: announcement, roles, real-time communication, and outcomes.
0 / 45 completed
1 / 45
What is a 'GameDay' in chaos engineering vocabulary?
A GameDay (popularized by Netflix and Amazon) is a structured exercise: pick a failure scenario (e.g., 'what happens if our payment service becomes unavailable?'), inject the failure in a controlled way, observe system behavior and team response, and hold a retrospective. It combines chaos experimentation with incident response training.
2 / 45
What is the role of a 'chaos facilitator' in a GameDay?
The chaos facilitator (or GameDay host) is distinct from the participants: they control the experiment progression, watch safety metrics, trigger the kill switch if needed, capture observations, keep the session on schedule, and run the post-GameDay retrospective. They do not 'play' the incident — they run the exercise.
3 / 45
What does a GameDay 'announcement' typically communicate?
GameDay announcements (typically sent 1–2 weeks in advance to affected teams): date/time, scope (which systems), scenario (what failure will be introduced), facilitator name and contact, kill switch conditions, and who to contact if they observe unexpected impact outside the announced scope.
4 / 45
What is a 'GameDay retrospective' in chaos engineering vocabulary?
The GameDay retrospective is as important as the experiment itself: Did the system behave as expected? Did monitoring catch the failure? Did the team respond effectively? What gaps were discovered? What needs to be improved? Action items: system fixes, runbook updates, monitoring improvements, and future GameDay scenarios.
5 / 45
What is 'hypothesis confirmation' vs. 'hypothesis rejection' in a GameDay?
Hypothesis confirmation: 'We injected 500ms of latency into the payment service. Our checkout flow degraded gracefully (timeouts handled correctly, fallback triggered) — error rate remained below 0.1%. The system is resilient to this failure mode.' Rejection: 'Error rate spiked to 15% — the system does not handle this failure gracefully. Finding: missing timeout configuration in the checkout service.'
6 / 45
Sarah: "Hey team, I'm running a GameDay to test the impact of increased traffic on our API. We're going to simulate a sudden spike in requests and observe how the system responds. I need everyone to monitor key metrics like latency and error rates. Let me know if you spot anything unusual!" Which of the following best describes
Sarah's intention when announcing this GameDay?The question focuses on the core purpose of a GameDay.
Sarah is deliberately creating a simulated scenario—a 'chaos experiment'—to actively test the system's resilience under stress. Option A incorrectly frames it as a budget request; B accurately describes the goal of identifying vulnerabilities and bottlenecks, while options C and D represent secondary or misaligned activities. This demonstrates understanding that GameDays are about controlled experimentation for risk assessment.7 / 45
Mark: 'Okay team, we're kicking off a GameDay focused on the new user onboarding flow. The goal is to intentionally introduce some failures – think intermittent database connection drops and simulated rate limits – to see how gracefully our system degrades under load. Specifically, I want you to observe any impact on the conversion funnel metrics: signup completion rates and initial user activation. Let's use this as an opportunity to identify potential bottlenecks before they affect real users.'This question tests understanding of GameDay's core purpose beyond simple load testing. The correct answer highlights that a GameDay isn't just about observing failures; it's about proactively identifying resilience gaps by simulating *controlled* failures and tracking key business metrics like the conversion funnel. The other options misinterpret the term, suggesting passive observation or an overly narrow focus on specific failure types without considering the impact on user experience – a crucial element of a successful GameDay.
8 / 45
David: 'Alright team, we're running a GameDay to validate the new caching layer. We'll be triggering a series of cache misses – essentially forcing requests to bypass the cache and hit the backend database – and monitoring the impact on response times. The key metric is overall latency; I want to see if the change has improved or worsened it, especially during peak hours. Let's keep an eye on the error rates too, just in case.'This scenario highlights the core purpose of a GameDay: it's not about simply deploying or testing something. David is explicitly stating he wants to *identify potential regressions* – meaning problems that the new caching layer might have caused. The focus on latency and error rates directly aligns with this goal, correcting the misconception that GameDays are purely for demonstration or general exercises.
9 / 45
PR Description:
"Running a GameDay to simulate a flash sale. Expect high load on the product catalog service and potential timeouts. Monitoring key metrics: CPU utilization, memory usage, response times (specifically for product searches), and error rates. Please flag any significant deviations from baseline."This
PR Description clearly indicates a GameDay scenario. The language – 'flash sale,' 'high load,' 'simulated stress'— points to a deliberate test of the system's capacity under unexpected demand. It highlights the need for monitoring key metrics, which is a core component of chaos engineering exercises. Option A misinterprets this as a standard code review; options B and C are incorrect because they don't describe a planned experiment or operational testing.10 / 45
Reviewing a pull request for a new microservice deployment, you see the following comment from Alex:
@team I'm initiating a GameDay to stress test this service. We'll be injecting synthetic traffic and monitoring key metrics – specifically CPU utilization, network latency, and error rates. Let me know if you observe any unexpected behavior or performance degradation.
Which of the following best captures Alex's primary objective during this 'GameDay'?
The correct answer is 'To proactively simulate real user traffic patterns and assess the service's resilience under duress.' While generating load (option B) is a component, Alex's goal extends beyond just finding constraints. A 'GameDay' in chaos engineering aims to *simulate* realistic scenarios – including high volume – to understand how the system behaves under pressure, testing its ability to recover and maintain stability. Options A and D are misinterpretations of the purpose; option C accurately describes the core intent of a GameDay: to validate performance and resilience through controlled stress.
11 / 45
Sarah: "Hey team, I'm running a GameDay to test the impact of increased traffic on our API. We're going to simulate a sudden spike in requests and observe how the system responds. I need everyone to monitor key metrics like latency and error rates. Let me know if you spot anything unusual!" Which of the following best describes
Sarah's intention when announcing this GameDay?The question focuses on the core purpose of a GameDay.
Sarah is deliberately creating a simulated scenario—a 'chaos experiment'—to actively test the system's resilience under stress. Option A incorrectly frames it as a budget request; B accurately describes the goal of identifying vulnerabilities and bottlenecks, while options C and D represent secondary or misaligned activities. This demonstrates understanding that GameDays are about controlled experimentation for risk assessment.12 / 45
Mark: 'Okay team, we're kicking off a GameDay focused on the new user onboarding flow. The goal is to intentionally introduce some failures – think intermittent database connection drops and simulated rate limits – to see how gracefully our system degrades under load. Specifically, I want you to observe any impact on the conversion funnel metrics: signup completion rates and initial user activation. Let's use this as an opportunity to identify potential bottlenecks before they affect real users.'This question tests understanding of GameDay's core purpose beyond simple load testing. The correct answer highlights that a GameDay isn't just about observing failures; it's about proactively identifying resilience gaps by simulating *controlled* failures and tracking key business metrics like the conversion funnel. The other options misinterpret the term, suggesting passive observation or an overly narrow focus on specific failure types without considering the impact on user experience – a crucial element of a successful GameDay.
13 / 45
David: 'Alright team, we're running a GameDay to validate the new caching layer. We'll be triggering a series of cache misses – essentially forcing requests to bypass the cache and hit the backend database – and monitoring the impact on response times. The key metric is overall latency; I want to see if the change has improved or worsened it, especially during peak hours. Let's keep an eye on the error rates too, just in case.'This scenario highlights the core purpose of a GameDay: it's not about simply deploying or testing something. David is explicitly stating he wants to *identify potential regressions* – meaning problems that the new caching layer might have caused. The focus on latency and error rates directly aligns with this goal, correcting the misconception that GameDays are purely for demonstration or general exercises.
14 / 45
PR Description:
"Running a GameDay to simulate a flash sale. Expect high load on the product catalog service and potential timeouts. Monitoring key metrics: CPU utilization, memory usage, response times (specifically for product searches), and error rates. Please flag any significant deviations from baseline."This
PR Description clearly indicates a GameDay scenario. The language – 'flash sale,' 'high load,' 'simulated stress'— points to a deliberate test of the system's capacity under unexpected demand. It highlights the need for monitoring key metrics, which is a core component of chaos engineering exercises. Option A misinterprets this as a standard code review; options B and C are incorrect because they don't describe a planned experiment or operational testing.15 / 45
Reviewing a pull request for a new microservice deployment, you see the following comment from Alex:
@team I'm initiating a GameDay to stress test this service. We'll be injecting synthetic traffic and monitoring key metrics – specifically CPU utilization, network latency, and error rates. Let me know if you observe any unexpected behavior or performance degradation.
Which of the following best captures Alex's primary objective during this 'GameDay'?
The correct answer is 'To proactively simulate real user traffic patterns and assess the service's resilience under duress.' While generating load (option B) is a component, Alex's goal extends beyond just finding constraints. A 'GameDay' in chaos engineering aims to *simulate* realistic scenarios – including high volume – to understand how the system behaves under pressure, testing its ability to recover and maintain stability. Options A and D are misinterpretations of the purpose; option C accurately describes the core intent of a GameDay: to validate performance and resilience through controlled stress.
16 / 45
Sarah: "Hey team, I'm running a GameDay to test the impact of increased traffic on our API. We're going to simulate a sudden spike in requests and observe how the system responds. I need everyone to monitor key metrics like latency and error rates. Let me know if you spot anything unusual!" Which of the following best describes
Sarah's intention when announcing this GameDay?The question focuses on the core purpose of a GameDay.
Sarah is deliberately creating a simulated scenario—a 'chaos experiment'—to actively test the system's resilience under stress. Option A incorrectly frames it as a budget request; B accurately describes the goal of identifying vulnerabilities and bottlenecks, while options C and D represent secondary or misaligned activities. This demonstrates understanding that GameDays are about controlled experimentation for risk assessment.17 / 45
Mark: 'Okay team, we're kicking off a GameDay focused on the new user onboarding flow. The goal is to intentionally introduce some failures – think intermittent database connection drops and simulated rate limits – to see how gracefully our system degrades under load. Specifically, I want you to observe any impact on the conversion funnel metrics: signup completion rates and initial user activation. Let's use this as an opportunity to identify potential bottlenecks before they affect real users.'This question tests understanding of GameDay's core purpose beyond simple load testing. The correct answer highlights that a GameDay isn't just about observing failures; it's about proactively identifying resilience gaps by simulating *controlled* failures and tracking key business metrics like the conversion funnel. The other options misinterpret the term, suggesting passive observation or an overly narrow focus on specific failure types without considering the impact on user experience – a crucial element of a successful GameDay.
18 / 45
David: 'Alright team, we're running a GameDay to validate the new caching layer. We'll be triggering a series of cache misses – essentially forcing requests to bypass the cache and hit the backend database – and monitoring the impact on response times. The key metric is overall latency; I want to see if the change has improved or worsened it, especially during peak hours. Let's keep an eye on the error rates too, just in case.'This scenario highlights the core purpose of a GameDay: it's not about simply deploying or testing something. David is explicitly stating he wants to *identify potential regressions* – meaning problems that the new caching layer might have caused. The focus on latency and error rates directly aligns with this goal, correcting the misconception that GameDays are purely for demonstration or general exercises.
19 / 45
PR Description:
"Running a GameDay to simulate a flash sale. Expect high load on the product catalog service and potential timeouts. Monitoring key metrics: CPU utilization, memory usage, response times (specifically for product searches), and error rates. Please flag any significant deviations from baseline."This
PR Description clearly indicates a GameDay scenario. The language – 'flash sale,' 'high load,' 'simulated stress'— points to a deliberate test of the system's capacity under unexpected demand. It highlights the need for monitoring key metrics, which is a core component of chaos engineering exercises. Option A misinterprets this as a standard code review; options B and C are incorrect because they don't describe a planned experiment or operational testing.20 / 45
Reviewing a pull request for a new microservice deployment, you see the following comment from Alex:
@team I'm initiating a GameDay to stress test this service. We'll be injecting synthetic traffic and monitoring key metrics – specifically CPU utilization, network latency, and error rates. Let me know if you observe any unexpected behavior or performance degradation.
Which of the following best captures Alex's primary objective during this 'GameDay'?
The correct answer is 'To proactively simulate real user traffic patterns and assess the service's resilience under duress.' While generating load (option B) is a component, Alex's goal extends beyond just finding constraints. A 'GameDay' in chaos engineering aims to *simulate* realistic scenarios – including high volume – to understand how the system behaves under pressure, testing its ability to recover and maintain stability. Options A and D are misinterpretations of the purpose; option C accurately describes the core intent of a GameDay: to validate performance and resilience through controlled stress.
21 / 45
Sarah: "Hey team, I'm running a GameDay to test the impact of increased traffic on our API. We're going to simulate a sudden spike in requests and observe how the system responds. I need everyone to monitor key metrics like latency and error rates. Let me know if you spot anything unusual!" Which of the following best describes
Sarah's intention when announcing this GameDay?The question focuses on the core purpose of a GameDay.
Sarah is deliberately creating a simulated scenario—a 'chaos experiment'—to actively test the system's resilience under stress. Option A incorrectly frames it as a budget request; B accurately describes the goal of identifying vulnerabilities and bottlenecks, while options C and D represent secondary or misaligned activities. This demonstrates understanding that GameDays are about controlled experimentation for risk assessment.22 / 45
Mark: 'Okay team, we're kicking off a GameDay focused on the new user onboarding flow. The goal is to intentionally introduce some failures – think intermittent database connection drops and simulated rate limits – to see how gracefully our system degrades under load. Specifically, I want you to observe any impact on the conversion funnel metrics: signup completion rates and initial user activation. Let's use this as an opportunity to identify potential bottlenecks before they affect real users.'This question tests understanding of GameDay's core purpose beyond simple load testing. The correct answer highlights that a GameDay isn't just about observing failures; it's about proactively identifying resilience gaps by simulating *controlled* failures and tracking key business metrics like the conversion funnel. The other options misinterpret the term, suggesting passive observation or an overly narrow focus on specific failure types without considering the impact on user experience – a crucial element of a successful GameDay.
23 / 45
David: 'Alright team, we're running a GameDay to validate the new caching layer. We'll be triggering a series of cache misses – essentially forcing requests to bypass the cache and hit the backend database – and monitoring the impact on response times. The key metric is overall latency; I want to see if the change has improved or worsened it, especially during peak hours. Let's keep an eye on the error rates too, just in case.'This scenario highlights the core purpose of a GameDay: it's not about simply deploying or testing something. David is explicitly stating he wants to *identify potential regressions* – meaning problems that the new caching layer might have caused. The focus on latency and error rates directly aligns with this goal, correcting the misconception that GameDays are purely for demonstration or general exercises.
24 / 45
PR Description:
"Running a GameDay to simulate a flash sale. Expect high load on the product catalog service and potential timeouts. Monitoring key metrics: CPU utilization, memory usage, response times (specifically for product searches), and error rates. Please flag any significant deviations from baseline."This
PR Description clearly indicates a GameDay scenario. The language – 'flash sale,' 'high load,' 'simulated stress'— points to a deliberate test of the system's capacity under unexpected demand. It highlights the need for monitoring key metrics, which is a core component of chaos engineering exercises. Option A misinterprets this as a standard code review; options B and C are incorrect because they don't describe a planned experiment or operational testing.25 / 45
Reviewing a pull request for a new microservice deployment, you see the following comment from Alex:
@team I'm initiating a GameDay to stress test this service. We'll be injecting synthetic traffic and monitoring key metrics – specifically CPU utilization, network latency, and error rates. Let me know if you observe any unexpected behavior or performance degradation.
Which of the following best captures Alex's primary objective during this 'GameDay'?
The correct answer is 'To proactively simulate real user traffic patterns and assess the service's resilience under duress.' While generating load (option B) is a component, Alex's goal extends beyond just finding constraints. A 'GameDay' in chaos engineering aims to *simulate* realistic scenarios – including high volume – to understand how the system behaves under pressure, testing its ability to recover and maintain stability. Options A and D are misinterpretations of the purpose; option C accurately describes the core intent of a GameDay: to validate performance and resilience through controlled stress.
26 / 45
Sarah: "Hey team, I'm running a GameDay to test the impact of increased traffic on our API. We're going to simulate a sudden spike in requests and observe how the system responds. I need everyone to monitor key metrics like latency and error rates. Let me know if you spot anything unusual!" Which of the following best describes
Sarah's intention when announcing this GameDay?The question focuses on the core purpose of a GameDay.
Sarah is deliberately creating a simulated scenario—a 'chaos experiment'—to actively test the system's resilience under stress. Option A incorrectly frames it as a budget request; B accurately describes the goal of identifying vulnerabilities and bottlenecks, while options C and D represent secondary or misaligned activities. This demonstrates understanding that GameDays are about controlled experimentation for risk assessment.27 / 45
Mark: 'Okay team, we're kicking off a GameDay focused on the new user onboarding flow. The goal is to intentionally introduce some failures – think intermittent database connection drops and simulated rate limits – to see how gracefully our system degrades under load. Specifically, I want you to observe any impact on the conversion funnel metrics: signup completion rates and initial user activation. Let's use this as an opportunity to identify potential bottlenecks before they affect real users.'This question tests understanding of GameDay's core purpose beyond simple load testing. The correct answer highlights that a GameDay isn't just about observing failures; it's about proactively identifying resilience gaps by simulating *controlled* failures and tracking key business metrics like the conversion funnel. The other options misinterpret the term, suggesting passive observation or an overly narrow focus on specific failure types without considering the impact on user experience – a crucial element of a successful GameDay.
28 / 45
David: 'Alright team, we're running a GameDay to validate the new caching layer. We'll be triggering a series of cache misses – essentially forcing requests to bypass the cache and hit the backend database – and monitoring the impact on response times. The key metric is overall latency; I want to see if the change has improved or worsened it, especially during peak hours. Let's keep an eye on the error rates too, just in case.'This scenario highlights the core purpose of a GameDay: it's not about simply deploying or testing something. David is explicitly stating he wants to *identify potential regressions* – meaning problems that the new caching layer might have caused. The focus on latency and error rates directly aligns with this goal, correcting the misconception that GameDays are purely for demonstration or general exercises.
29 / 45
PR Description:
"Running a GameDay to simulate a flash sale. Expect high load on the product catalog service and potential timeouts. Monitoring key metrics: CPU utilization, memory usage, response times (specifically for product searches), and error rates. Please flag any significant deviations from baseline."This
PR Description clearly indicates a GameDay scenario. The language – 'flash sale,' 'high load,' 'simulated stress'— points to a deliberate test of the system's capacity under unexpected demand. It highlights the need for monitoring key metrics, which is a core component of chaos engineering exercises. Option A misinterprets this as a standard code review; options B and C are incorrect because they don't describe a planned experiment or operational testing.30 / 45
Reviewing a pull request for a new microservice deployment, you see the following comment from Alex:
@team I'm initiating a GameDay to stress test this service. We'll be injecting synthetic traffic and monitoring key metrics – specifically CPU utilization, network latency, and error rates. Let me know if you observe any unexpected behavior or performance degradation.
Which of the following best captures Alex's primary objective during this 'GameDay'?
The correct answer is 'To proactively simulate real user traffic patterns and assess the service's resilience under duress.' While generating load (option B) is a component, Alex's goal extends beyond just finding constraints. A 'GameDay' in chaos engineering aims to *simulate* realistic scenarios – including high volume – to understand how the system behaves under pressure, testing its ability to recover and maintain stability. Options A and D are misinterpretations of the purpose; option C accurately describes the core intent of a GameDay: to validate performance and resilience through controlled stress.
31 / 45
Sarah: "Hey team, I'm running a GameDay to test the impact of increased traffic on our API. We're going to simulate a sudden spike in requests and observe how the system responds. I need everyone to monitor key metrics like latency and error rates. Let me know if you spot anything unusual!" Which of the following best describes
Sarah's intention when announcing this GameDay?The question focuses on the core purpose of a GameDay.
Sarah is deliberately creating a simulated scenario—a 'chaos experiment'—to actively test the system's resilience under stress. Option A incorrectly frames it as a budget request; B accurately describes the goal of identifying vulnerabilities and bottlenecks, while options C and D represent secondary or misaligned activities. This demonstrates understanding that GameDays are about controlled experimentation for risk assessment.32 / 45
Mark: 'Okay team, we're kicking off a GameDay focused on the new user onboarding flow. The goal is to intentionally introduce some failures – think intermittent database connection drops and simulated rate limits – to see how gracefully our system degrades under load. Specifically, I want you to observe any impact on the conversion funnel metrics: signup completion rates and initial user activation. Let's use this as an opportunity to identify potential bottlenecks before they affect real users.'This question tests understanding of GameDay's core purpose beyond simple load testing. The correct answer highlights that a GameDay isn't just about observing failures; it's about proactively identifying resilience gaps by simulating *controlled* failures and tracking key business metrics like the conversion funnel. The other options misinterpret the term, suggesting passive observation or an overly narrow focus on specific failure types without considering the impact on user experience – a crucial element of a successful GameDay.
33 / 45
David: 'Alright team, we're running a GameDay to validate the new caching layer. We'll be triggering a series of cache misses – essentially forcing requests to bypass the cache and hit the backend database – and monitoring the impact on response times. The key metric is overall latency; I want to see if the change has improved or worsened it, especially during peak hours. Let's keep an eye on the error rates too, just in case.'This scenario highlights the core purpose of a GameDay: it's not about simply deploying or testing something. David is explicitly stating he wants to *identify potential regressions* – meaning problems that the new caching layer might have caused. The focus on latency and error rates directly aligns with this goal, correcting the misconception that GameDays are purely for demonstration or general exercises.
34 / 45
PR Description:
"Running a GameDay to simulate a flash sale. Expect high load on the product catalog service and potential timeouts. Monitoring key metrics: CPU utilization, memory usage, response times (specifically for product searches), and error rates. Please flag any significant deviations from baseline."This
PR Description clearly indicates a GameDay scenario. The language – 'flash sale,' 'high load,' 'simulated stress'— points to a deliberate test of the system's capacity under unexpected demand. It highlights the need for monitoring key metrics, which is a core component of chaos engineering exercises. Option A misinterprets this as a standard code review; options B and C are incorrect because they don't describe a planned experiment or operational testing.35 / 45
Reviewing a pull request for a new microservice deployment, you see the following comment from Alex:
@team I'm initiating a GameDay to stress test this service. We'll be injecting synthetic traffic and monitoring key metrics – specifically CPU utilization, network latency, and error rates. Let me know if you observe any unexpected behavior or performance degradation.
Which of the following best captures Alex's primary objective during this 'GameDay'?
The correct answer is 'To proactively simulate real user traffic patterns and assess the service's resilience under duress.' While generating load (option B) is a component, Alex's goal extends beyond just finding constraints. A 'GameDay' in chaos engineering aims to *simulate* realistic scenarios – including high volume – to understand how the system behaves under pressure, testing its ability to recover and maintain stability. Options A and D are misinterpretations of the purpose; option C accurately describes the core intent of a GameDay: to validate performance and resilience through controlled stress.
36 / 45
Sarah: "Hey team, I'm running a GameDay to test the impact of increased traffic on our API. We're going to simulate a sudden spike in requests and observe how the system responds. I need everyone to monitor key metrics like latency and error rates. Let me know if you spot anything unusual!" Which of the following best describes
Sarah's intention when announcing this GameDay?The question focuses on the core purpose of a GameDay.
Sarah is deliberately creating a simulated scenario—a 'chaos experiment'—to actively test the system's resilience under stress. Option A incorrectly frames it as a budget request; B accurately describes the goal of identifying vulnerabilities and bottlenecks, while options C and D represent secondary or misaligned activities. This demonstrates understanding that GameDays are about controlled experimentation for risk assessment.37 / 45
Mark: 'Okay team, we're kicking off a GameDay focused on the new user onboarding flow. The goal is to intentionally introduce some failures – think intermittent database connection drops and simulated rate limits – to see how gracefully our system degrades under load. Specifically, I want you to observe any impact on the conversion funnel metrics: signup completion rates and initial user activation. Let's use this as an opportunity to identify potential bottlenecks before they affect real users.'This question tests understanding of GameDay's core purpose beyond simple load testing. The correct answer highlights that a GameDay isn't just about observing failures; it's about proactively identifying resilience gaps by simulating *controlled* failures and tracking key business metrics like the conversion funnel. The other options misinterpret the term, suggesting passive observation or an overly narrow focus on specific failure types without considering the impact on user experience – a crucial element of a successful GameDay.
38 / 45
David: 'Alright team, we're running a GameDay to validate the new caching layer. We'll be triggering a series of cache misses – essentially forcing requests to bypass the cache and hit the backend database – and monitoring the impact on response times. The key metric is overall latency; I want to see if the change has improved or worsened it, especially during peak hours. Let's keep an eye on the error rates too, just in case.'This scenario highlights the core purpose of a GameDay: it's not about simply deploying or testing something. David is explicitly stating he wants to *identify potential regressions* – meaning problems that the new caching layer might have caused. The focus on latency and error rates directly aligns with this goal, correcting the misconception that GameDays are purely for demonstration or general exercises.
39 / 45
PR Description:
"Running a GameDay to simulate a flash sale. Expect high load on the product catalog service and potential timeouts. Monitoring key metrics: CPU utilization, memory usage, response times (specifically for product searches), and error rates. Please flag any significant deviations from baseline."This
PR Description clearly indicates a GameDay scenario. The language – 'flash sale,' 'high load,' 'simulated stress'— points to a deliberate test of the system's capacity under unexpected demand. It highlights the need for monitoring key metrics, which is a core component of chaos engineering exercises. Option A misinterprets this as a standard code review; options B and C are incorrect because they don't describe a planned experiment or operational testing.40 / 45
Reviewing a pull request for a new microservice deployment, you see the following comment from Alex:
@team I'm initiating a GameDay to stress test this service. We'll be injecting synthetic traffic and monitoring key metrics – specifically CPU utilization, network latency, and error rates. Let me know if you observe any unexpected behavior or performance degradation.
Which of the following best captures Alex's primary objective during this 'GameDay'?
The correct answer is 'To proactively simulate real user traffic patterns and assess the service's resilience under duress.' While generating load (option B) is a component, Alex's goal extends beyond just finding constraints. A 'GameDay' in chaos engineering aims to *simulate* realistic scenarios – including high volume – to understand how the system behaves under pressure, testing its ability to recover and maintain stability. Options A and D are misinterpretations of the purpose; option C accurately describes the core intent of a GameDay: to validate performance and resilience through controlled stress.
41 / 45
Sarah: "Hey team, I'm running a GameDay to test the impact of increased traffic on our API. We're going to simulate a sudden spike in requests and observe how the system responds. I need everyone to monitor key metrics like latency and error rates. Let me know if you spot anything unusual!" Which of the following best describes
Sarah's intention when announcing this GameDay?The question focuses on the core purpose of a GameDay.
Sarah is deliberately creating a simulated scenario—a 'chaos experiment'—to actively test the system's resilience under stress. Option A incorrectly frames it as a budget request; B accurately describes the goal of identifying vulnerabilities and bottlenecks, while options C and D represent secondary or misaligned activities. This demonstrates understanding that GameDays are about controlled experimentation for risk assessment.42 / 45
Mark: 'Okay team, we're kicking off a GameDay focused on the new user onboarding flow. The goal is to intentionally introduce some failures – think intermittent database connection drops and simulated rate limits – to see how gracefully our system degrades under load. Specifically, I want you to observe any impact on the conversion funnel metrics: signup completion rates and initial user activation. Let's use this as an opportunity to identify potential bottlenecks before they affect real users.'This question tests understanding of GameDay's core purpose beyond simple load testing. The correct answer highlights that a GameDay isn't just about observing failures; it's about proactively identifying resilience gaps by simulating *controlled* failures and tracking key business metrics like the conversion funnel. The other options misinterpret the term, suggesting passive observation or an overly narrow focus on specific failure types without considering the impact on user experience – a crucial element of a successful GameDay.
43 / 45
David: 'Alright team, we're running a GameDay to validate the new caching layer. We'll be triggering a series of cache misses – essentially forcing requests to bypass the cache and hit the backend database – and monitoring the impact on response times. The key metric is overall latency; I want to see if the change has improved or worsened it, especially during peak hours. Let's keep an eye on the error rates too, just in case.'This scenario highlights the core purpose of a GameDay: it's not about simply deploying or testing something. David is explicitly stating he wants to *identify potential regressions* – meaning problems that the new caching layer might have caused. The focus on latency and error rates directly aligns with this goal, correcting the misconception that GameDays are purely for demonstration or general exercises.
44 / 45
PR Description:
"Running a GameDay to simulate a flash sale. Expect high load on the product catalog service and potential timeouts. Monitoring key metrics: CPU utilization, memory usage, response times (specifically for product searches), and error rates. Please flag any significant deviations from baseline."This
PR Description clearly indicates a GameDay scenario. The language – 'flash sale,' 'high load,' 'simulated stress'— points to a deliberate test of the system's capacity under unexpected demand. It highlights the need for monitoring key metrics, which is a core component of chaos engineering exercises. Option A misinterprets this as a standard code review; options B and C are incorrect because they don't describe a planned experiment or operational testing.45 / 45
Reviewing a pull request for a new microservice deployment, you see the following comment from Alex:
@team I'm initiating a GameDay to stress test this service. We'll be injecting synthetic traffic and monitoring key metrics – specifically CPU utilization, network latency, and error rates. Let me know if you observe any unexpected behavior or performance degradation.
Which of the following best captures Alex's primary objective during this 'GameDay'?
The correct answer is 'To proactively simulate real user traffic patterns and assess the service's resilience under duress.' While generating load (option B) is a component, Alex's goal extends beyond just finding constraints. A 'GameDay' in chaos engineering aims to *simulate* realistic scenarios – including high volume – to understand how the system behaves under pressure, testing its ability to recover and maintain stability. Options A and D are misinterpretations of the purpose; option C accurately describes the core intent of a GameDay: to validate performance and resilience through controlled stress.
Frequently Asked Questions
What will I practice in "GameDay — Vocabulary and Communication Language"?
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.