DP-300 Configure and manage automation of tasks Practice Question
You need to automate the deployment of schema changes to multiple Azure SQL Databases in different regions. The solution must support rollback and version control. Which technology should you use?
⚠ Common exam trap
Many exam-takers confuse Azure Data Factory or Azure Automation as valid automation tools for schema changes, overlooking that they lack the version control and rollback capabilities that are explicitly required by the question.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Azure DevOps with a database project and release pipelines.
Azure DevOps with a database project and release pipelines is the correct choice because it provides source control for schema changes, automated deployment across multiple environments, and built-in rollback capabilities through pipeline versioning and deployment history. This approach aligns with infrastructure-as-code principles, enabling consistent, repeatable, and auditable schema deployments to Azure SQL Databases in different regions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use Azure Data Factory to run stored procedures for schema changes.
Why it's wrong here
Data Factory orchestrates pipelines and runs stored procedures, but it holds no schema version history or rollback mechanism; a failed change cannot be reverted to a prior state. It is tempting because it genuinely automates cross-region execution, and would suit data movement or scheduled ETL, not versioned schema deployment.
- ✗
Use SQL Server Agent jobs to run deployment scripts on schedule.
Why it's wrong here
SQL Server Agent is unavailable in Azure SQL Database and its jobs offer no version history or rollback, so schema changes cannot be reverted. It is tempting because Agent jobs are the familiar on-premises scheduling mechanism, correct for recurring maintenance tasks on SQL Server instances you manage.
- ✓
Use Azure DevOps with a database project and release pipelines.
Why this is correct
Azure DevOps database projects keep schema definitions in version control, and release pipelines deploy them across regions with tracked, repeatable steps. This satisfies both the rollback requirement, via redeploying prior versions, and version control of schema changes.
- ✗
Use Azure Automation with PowerShell scripts to execute T-SQL scripts.
Why it's wrong here
Azure Automation runs scripts but stores no schema version history and provides no rollback mechanism, so failed deployments cannot be reverted. It is tempting because Automation is the standard Azure tool for scheduled runbooks and patching tasks, where versioned schema state is not required.
Visual reference
Go deeper
Related to this question
About these practice questions
Courseiva writes every DP-300 question from scratch — 574 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-300 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-300 exam.