Question 410
A release pipeline automatically publishes SQL schema changes to production on every developer push. Which implementation step most directly addresses this requirement?
Explanation
Correct Answer
Manual approvals and protected environment gates provide controlled production change authorization. Require explicit production approval and validated predeploy diffs. Unauthorized pushes cannot deploy and approved releases are traceable.
Incorrect Answers
That change leaves the underlying defect unresolved: Build validation and release authorization are separate; require gated, accountable approval and diff review.
The proposed implementation creates the wrong boundary because Protect the deployment environment and service identity independently of source branch policy.
This step would not produce the required behavior: Meaningful, traceable approval depends on reviewable diffs and technical tests; clicks are not correctness proof. This alternative omits a necessary contract or control and leaves the tested failure path open.