Question 770
A pipeline deploys to production immediately after any branch push. Which technical reason BEST explains the proposed correction?
Explanation
Correct Answer
Automated execution without authorization can promote unreviewed schema changes. This explains why the corrective action is to use protected branch triggers, environment approval gates and deployment-specific identities. Confirm the diagnosis when unapproved branch commits never reach production.
Incorrect Answers
Path ownership helps route high-impact DDL for accountable review. The actual technical constraint is that automated execution without authorization can promote unreviewed schema changes.
Repeatable deployments must not assume reference rows are absent. The actual technical constraint is that automated execution without authorization can promote unreviewed schema changes.
A text merge can compile but still change business behavior. The actual technical constraint is that automated execution without authorization can promote unreviewed schema changes.