Question 760
Any developer can merge a production schema change directly into the main branch without independent review. What is the most defensible technical decision?
Explanation
Correct Answer
Protected branches prevent unreviewed changes from becoming deployment inputs.
Incorrect Answers
Restrict production triggers to approved branches or release tags with explicit gated authorization: restrict production triggers to approved branches or release tags with explicit gated authorization: deployment triggers must reflect approved lifecycle boundaries, not arbitrary source events; Enforce branch protection and required reviewer approval for the SQL project before merge.
Rebase or reconcile against current source and inspect the generated schema diff before deployment: rebase or reconcile against current source and inspect the generated schema diff before deployment: keeping migration branches current reduces accidental reversal of already approved database controls; Enforce branch protection and required reviewer approval for the SQL project before merge.
Use CODEOWNERS and required security or payroll data-owner review for changes touching those database objects: use CODEOWNERS and required security or payroll data-owner review for changes touching those database objects: domain-specific reviewers reduce the chance of approving changes that break business or privacy controls; Enforce branch protection and required reviewer approval for the SQL project before merge.



Developing AI-Enabled Database Solutions (DP-800) Practice Tests