Which practice involves deliberately introducing failures to test system resilience?

Which practice involves deliberately introducing failures to test system resilience?

• A. Risk register
• B. Waterfall method
• C. Harmonogram
• D. Chaos engineering

Answer: (D)

Deliberately injecting faults to see how a system handles problems is chaos engineering. The idea is to run controlled experiments that introduce faults—like shutting down a service, adding latency, or simulating a network split—to observe the system’s response, verify that redundancy and recovery mechanisms work, and confirm that monitoring and incident response will catch and recover from real outages. These experiments are designed with a hypothesis, a small blast radius, and careful metrics (availability, latency, error rate, recovery time) to learn what needs to be improved. This isn’t about planning risks on paper, like a risk register, which identifies possible problems without testing how the system behaves under stress. It’s also not about project development methods or scheduling, such as a waterfall approach or a project timetable, which focus on planning the work rather than actively probing resilience through faults.

Deliberately injecting faults to see how a system handles problems is chaos engineering. The idea is to run controlled experiments that introduce faults—like shutting down a service, adding latency, or simulating a network split—to observe the system’s response, verify that redundancy and recovery mechanisms work, and confirm that monitoring and incident response will catch and recover from real outages. These experiments are designed with a hypothesis, a small blast radius, and careful metrics (availability, latency, error rate, recovery time) to learn what needs to be improved.

This isn’t about planning risks on paper, like a risk register, which identifies possible problems without testing how the system behaves under stress. It’s also not about project development methods or scheduling, such as a waterfall approach or a project timetable, which focus on planning the work rather than actively probing resilience through faults.