DP-900 Practice Question: Identify considerations for relational data on Azure
A software company is migrating an on-premises SQL Server database to Azure SQL Database. The database currently uses SQL Server Agent jobs for regular maintenance tasks. The company wants to minimize code changes during migration. Which Azure SQL Database feature should they use to replace SQL Server Agent jobs?
⚠ Common exam trap
DP-900 often tests the distinction between Azure SQL Database and Azure SQL Managed Instance; candidates incorrectly assume SQL Server Agent is available in Azure SQL Database, but it is only available in Managed Instance, making Elastic Jobs the correct replacement.
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
✓
Elastic Jobs
Elastic Jobs is the Azure SQL Database feature specifically designed to replace SQL Server Agent jobs by allowing you to run T-SQL scripts across multiple databases on a schedule. It provides a job scheduler and execution engine that is compatible with existing T-SQL maintenance scripts, minimizing code changes during migration from on-premises SQL Server.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Azure Functions
Why it's wrong here
Azure Functions requires rewriting maintenance logic as function code with triggers and bindings, plus separate hosting and identity configuration. Elastic Jobs accept T-SQL close to existing SQL Server Agent job steps, minimising changes. Azure Functions suits event-driven or serverless workloads, not direct replacement of scheduled database maintenance jobs.
- ✗
Azure Automation
Why it's wrong here
Azure Automation runs runbooks in a separate automation account, requiring jobs to be rewritten as PowerShell or Python runbooks and linked via hybrid workers or schedules. Elastic Jobs reuse near-identical T-SQL across databases, minimising code changes. Azure Automation suits cross-service orchestration, not in-database maintenance parity.
- ✓
Elastic Jobs
Why this is correct
Elastic Jobs provide a T-SQL-based scheduler that runs across Azure SQL Database, closely mirroring SQL Server Agent job semantics such as steps, schedules and retry logic. This satisfies the stem's constraint of minimising code changes, since existing Agent job scripts transfer with minimal rewriting, unlike Logic Apps or Automation runbooks.
- ✗
SQL Server Agent (available in Azure SQL Database)
Why it's wrong here
SQL Server Agent is not available in Azure SQL Database; the service omits it entirely, so this option cannot satisfy the requirement. It is tempting because the on-premises database already uses Agent jobs, making it the obvious drop-in. Elastic Jobs provide the supported T-SQL-based equivalent for Azure SQL Database.
Go deeper
Related to this question
About these practice questions
One of 851 original DP-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This DP-900 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-900 exam.