Question 60
At the Juniperford research laboratory, different teams use incompatible definitions of production deployment frequency and compare their performance inaccurately. What continuing safeguard is most appropriate?
Explanation
Correct Answer
After the immediate fix, the priority is to audit metric definitions and source mappings when new deployment tools are adopted. This reinforces the control against the original weakness: counting staging releases for some teams makes delivery comparisons misleading. This directly addresses the reported issue at the Juniperford research laboratory.
Incorrect Answers
This routine applies to security remediation lead time, but it does not maintain the specific correction needed for the problem at the Juniperford research laboratory.
That practice helps control a different risk: fragmented work tracking hides blockers between components required for a common delivery. The recurring control here should be to audit metric definitions and source mappings when new deployment tools are adopted. For the Juniperford research laboratory, the priority is to standardize qualifying successful production deployments and data sources for team-level metrics.
The alternative suggests that the team verify issue-to-release mapping at each production promotion; it would not directly prevent the observed issue from returning. For the Juniperford research laboratory, the priority is to standardize qualifying successful production deployments and data sources for team-level metrics.