Question 870
A junior developer commits a DROP TABLE into the release branch without review. The team implemented this change: Require data-owner review, CI pass and protected merge workflow. Which result would best confirm the change worked?
Explanation
Correct Answer
Unapproved destructive DDL cannot merge even when build succeeds. Protected branches and code-owner policies can prevent unreviewed destructive schema merges.
Incorrect Answers
A DROP TABLE statement can compile correctly, but the protected release gate must block merging that destructive SQL change without code-owner approval.
A positive case does not test enforcement of required reviewer and protected-branch settings on destructive SQL.
Post-deployment notification is not evidence that the change was blocked before authorized review.