Question 70
During an operational security assessment at a public-sector technology agency, the team documents this issue: Weekly charts treat an aborted promotion as a successful customer deployment. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Select TWO: one corrective action and one test that confirms its effectiveness. (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Compute change failure rate using a documented production deployment denominator and associated rollback or incident criteria, then trend by service. The action targets the recorded failure (Weekly charts treat an aborted promotion as a successful customer deployment), and is intended to reduce the corresponding risk: Counting only successful releases or redefining failure types can conceal unstable delivery practices.
Correct verification. Reproduce the ratio for a reporting window from deployment and incident records, including a failed rollback-triggering release. The measurement or controlled test provides evidence for the issue (Weekly charts treat an aborted promotion as a successful customer deployment) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
A sampled change's merge and successful production deployment timestamps reconcile to the reported lead-time metric. This does not supply the required change failure rate dashboard action-and-control pair.
Use Azure Boards queries and analytics views with agreed work item states, area paths and iteration scope to report delivery commitments. The change failure rate dashboard implementation and safeguard are still missing.
Calculate time to restore from a clearly defined customer-impacting incident start to verified service recovery, correlating incident and telemetry records. The two-part change failure rate dashboard control remains unsatisfied.