Question 320
A junior developer commits a DROP TABLE into the release branch without review. Initial testing shows: Unapproved destructive DDL cannot merge even when build succeeds. Which limitation should the team still consider?
Explanation
Correct Answer
Reviewers need adequate context to catch semantic changes. Protected branches and code-owner policies can prevent unreviewed destructive schema merges.
Incorrect Answers
Required data-owner approval can still miss the SQL migration's semantic impact if reviewers lack the destructive diff, dependencies or acceptance tests.
SQL builds cannot evaluate business retention requirements; reviewers need contract and dependency context.
Merge rules control authorization, not the behavioral compatibility of schema changes with dependent consumers.