Question 530
A CRISC practitioner validates a response to this scenario: An organization assumes a distributed microservice system has no single point of failure because it has many components. Which evidence most directly establishes the desired risk outcome?
Explanation
Correct Answer
Fault injection confirms the application maintains defined service through one common dependency failure. This demonstrates the intended business or control result, rather than just task completion. The underlying response was: Identify and treat shared single points of failure despite service distribution. The evidence should relate to: Map shared databases, identity services, routing, messaging and deployment dependencies.
Incorrect Answers
A third-party timeout does not trigger cascading failure or duplicate transactions. That would matter when a payment platform relies on synchronous API calls to a fragile third-party service for every transaction. The relevant distinction in this case is: Fault injection confirms the application maintains defined service through one common dependency failure.
Testing demonstrates each control addresses the intended security or resilience consequence. That would matter when a bank classifies encryption as an availability control for its online banking service. It does not address this case's requirement: An organization assumes a distributed microservice system has no single point of failure because it has many components.
A connectivity-loss test preserves required safety operations within tolerance. That would matter when a warehouse sensor rollout assumes that all wireless devices remain reachable during an internet outage. That separate mechanism does not verify the needed risk management outcome in this case.