Question 50
During an operational security assessment at a public-sector technology agency, the team documents this issue: One service calculates lead time from ticket creation while another begins at commit. The affected delivery process supports citizen applications and reusable infrastructure; accountability and service availability depend on controlled delivery. Which TWO responses form a sound implementation-and-verification pair for this issue? (Select TWO.)
Explanation
Correct Answers
Correct corrective action. Define deployment lead time from accepted code changes to production delivery using consistent CI/CD timestamps and a segmented dashboard. The action targets the recorded failure (One service calculates lead time from ticket creation while another begins at commit), and is intended to reduce the corresponding risk: Measuring development effort or ticket age instead of production lead time hides delivery bottlenecks and misleading trends.
Correct verification. A sampled change's merge and successful production deployment timestamps reconcile to the reported lead-time metric. The measurement or controlled test provides evidence for the issue (One service calculates lead time from ticket creation while another begins at commit) and complements the selected corrective action rather than simply repeating a recommendation.
Incorrect Answers
Calculate time to restore from a clearly defined customer-impacting incident start to verified service recovery, correlating incident and telemetry records. The paired controls concern dora lead time metrics, not that measure.
A dashboard work item count matches a bounded Boards query and an independently sampled team's current iteration backlog. The dora lead time metrics implementation and safeguard are still missing.
Compute change failure rate using a documented production deployment denominator and associated rollback or incident criteria, then trend by service. The two-part dora lead time metrics control remains unsatisfied.