Question 150
A team stores all schema changes only in screenshots of query windows and cannot reproduce the last release in disaster recovery. What should the SQL developer do next?
Explanation
Correct Answer
Versioned source and artifacts support reproducible database releases rather than undocumented manual changes.
Incorrect Answers
Add project build and model validation checks to the pull-request pipeline and fail changes on unresolved references; compile-time database-model checks can catch dependency errors before an expensive deployment.
Capture intentional changes in source-controlled project files and validate a repeatable schema deployment workflow; schema-as-code relies on the model being the authoritative definition rather than an outdated snapshot.
Resolve database project conflicts using dependency review and rerun build and integration tests after the merge; a textual merge is not sufficient when related database objects have behavioral dependencies.



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