DP-300 Plan and implement data platform resources Practice Question
Your company is migrating an on-premises SQL Server database to Azure SQL Managed Instance. The database uses a SQL Server Agent job that runs a PowerShell script to process files. You need to ensure the job continues to run after migration with minimal changes. What should you do?
⚠ Common exam trap
Many candidates assume Azure SQL Database is a suitable target because it is the most common PaaS offering, but they overlook that SQL Managed Instance is required to retain SQL Server Agent and PowerShell job step support, which Azure SQL Database lacks entirely.
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
✓
Migrate the database to Azure SQL Managed Instance and recreate the job using SQL Server Agent.
Azure SQL Managed Instance supports SQL Server Agent, including jobs that run PowerShell scripts via CmdExec or PowerShell job steps. By migrating the database and recreating the job with the same script, you preserve the existing automation with minimal changes. This is the only option that keeps the job execution environment identical to the on-premises setup.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Migrate the database to Azure SQL Managed Instance and recreate the job using SQL Server Agent.
Why this is correct
Azure SQL Managed Instance includes SQL Server Agent, so recreating the job there preserves the PowerShell step with minimal changes. Migrating to single database would require replacing the agent with Elastic Jobs or Azure Automation.
- ✗
Migrate the database to Azure SQL Managed Instance and configure an Azure Automation runbook to run the script.
Why it's wrong here
Azure Automation runbooks run in Azure, not inside the managed instance, so they cannot use the instance's SQL Server Agent job step or access its local files without re-architecting. It is tempting because Automation hosts PowerShell, but the requirement is minimal change to the existing Agent job.
- ✗
Migrate the database to Azure SQL Managed Instance and use Elastic Jobs to run the PowerShell script.
Why it's wrong here
Elastic Jobs target Azure SQL Database and Azure SQL Managed Instance databases but execute T-SQL against them; they cannot run PowerShell or reach the file system. It is tempting because Elastic Jobs replace SQL Server Agent for cross-database scheduling, which suits T-SQL-only workloads, not script execution.
- ✗
Migrate the database to Azure SQL Database and use Elastic Jobs to run the PowerShell script.
Why it's wrong here
Elastic Jobs target Azure SQL Database, which lacks SQL Server Agent and the PowerShell subsystem, so the script cannot run unchanged; the stem requires minimal changes to an existing Agent job. Elastic Jobs suit scheduled T-SQL across databases, not PowerShell file processing.
Go deeper
Related to this question
Learn chapter
Deploying and Configuring SQL Server on Azure Virtual Machines
Key term
Azure SQL Managed Instance
Azure SQL Managed Instance is a fully managed cloud database service that gives you nearly all the features of Microsoft SQL Server on your own server, without you having to manage the hardware or operating system.
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.