Question 20
At the Cedarport payments platform, compliance reviewers receive a deployment date but cannot identify which approved requests it delivered. How should the team reduce the chance of the issue recurring?
Explanation
Correct Answer
After the immediate fix, the priority is to check traceability links for material changes during each release review. This reinforces the control against the original weakness: a timestamp alone cannot establish the scope or authorization of deployed application changes. This directly addresses the reported issue at the Cedarport payments platform.
Incorrect Answers
This routine applies to automated issue creation from failures, but it does not maintain the specific correction needed for the problem at the Cedarport payments platform.
That practice helps control a different risk: infrastructure startup time can understate the interval until a usable service is restored. The recurring control here should be to check traceability links for material changes during each release review. For the Cedarport payments platform, the priority is to associate each production release with reviewed work items, commits, build artifacts and deployment records.
The alternative suggests that the team revalidate notification routing after on-call and team membership changes; it would not directly prevent the observed issue from returning. For the Cedarport payments platform, the priority is to associate each production release with reviewed work items, commits, build artifacts and deployment records.