Question 770
A release pipeline automatically publishes SQL schema changes to production on every developer push. The team implemented this change: Require explicit production approval and validated predeploy diffs. Which result would best confirm the change worked?
Explanation
Correct Answer
Unauthorized pushes cannot deploy and approved releases are traceable. Manual approvals and protected environment gates provide controlled production change authorization. Approval without meaningful inspection does not guarantee safe schema changes.
Incorrect Answers
That observation could pass while the problem persists: Build validation and release authorization are separate; require gated, accountable approval and diff review.
This acceptance test measures the wrong outcome: Protect the deployment environment and service identity independently of source branch policy.
The suggested success signal is inadequate because Meaningful, traceable approval depends on reviewable diffs and technical tests; clicks are not correctness proof. The suggested measurement would appear successful even in a reproducible case where the original failure remains.