Transit wants schema PRs that touch dbo objects to require designated reviewers before release. Which pipeline control should they use?
Select an answer to reveal the explanation.
Short Explanation
Code owners on dbo PRs means the transit schema guardians have to sign the work order before release—no anonymous merge into the main switchyard.
Full Explanation
Transit wants schema PRs that touch dbo objects to require designated reviewers before release—implement that with code owners (or equivalent required-reviewer path policies) so dbo schema pull requests cannot merge without the owning guardians’ approval. Code owners bind file paths (for example dbo/**) to responsible reviewers inside the PR workflow, which is the pipeline/source-control control that enforces designated approval before release proceeds. Allowing any forked anonymous contributor to merge dbo changes instantly removes review and invites unvetted schema changes into transit systems. Disabling pull requests and committing dbo changes only on Fridays is calendar theater without quality gates. Storing the dacpac on a public blob container without review gates exposes deployment artifacts and skips human authorization on dbo changes. Exam caveat: code owners must be enforced by branch policy (“require code owner review”), not merely a CODEOWNERS file that reviewers can ignore. Combine with CI build validation so owners review a green, buildable schema change. Distinguish code-owner review on merge from environment approval gates on production deploy—both are useful and complementary. Operational check: add CODEOWNERS entries for dbo schema paths; enable required code owner approval on the protected branch; open a dbo PR as a non-owner and confirm merge is blocked until an owner approves; merge after approval and ensure release still respects any production environment gate.