Your application in production has recently been experiencing reliability issues, and you are unsure how the application will behave in the event of an unexpected failure. You want to assess the appli

Question

Options

• AWrite end-to-end tests to determine how different microservices interact. Validate that all tests
• BPerform chaos engineering by intentionally introducing failures into the system. Observe how the
• CTest individual units of code for a critical portion of the application's code. Ensure that unit tests
• DPerform load testing of the application, and use JMeter for the critical endpoints of the application.

• A
  13% (7)
• B
  76% (42)
• C
  4% (2)
• D
  7% (4)

Explanation

Chaos engineering is the discipline of intentionally injecting failures (network partitions, instance terminations, latency spikes, dependency outages) into a running system to observe and measure its actual resilience behavior. It directly answers the question 'how will the application behave during unexpected failures?' Options A and C (end-to-end and unit tests) verify functional correctness but do not simulate production failures. Option D (load testing with JMeter) evaluates performance under high traffic but does not test failure modes like dependency unavailability or partial outages. Only chaos engineering proactively surfaces resilience gaps before they become real incidents.

No community discussion yet for this question.