DP-300 Configure and manage automation of tasks Practice Question
A DBA manages an Azure SQL Database and needs to schedule a T-SQL script to run every day at 02:00 UTC to perform index maintenance. The solution must minimize administrative overhead and must not require an on-premises server. What should the DBA use?
⚠ Common exam trap
The trap here is assuming that SQL Server Agent is available on Azure SQL Database, when Agent is only supported on Azure SQL Managed Instance and on-premises SQL Server.
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 Database Jobs in Azure SQL Database
Elastic Database Jobs provide a built-in scheduling mechanism for T-SQL scripts against Azure SQL Database. The DBA creates a job agent, defines a job with a T-SQL step, and attaches a schedule. This requires no on-premises server and minimal administrative effort, making it the correct choice for daily index maintenance.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Elastic Database Jobs in Azure SQL Database
Why this is correct
Elastic Database Jobs are a native Azure SQL Database feature that can run T-SQL scripts against one or many databases on a schedule. They require no on-premises infrastructure and minimal setup: create a job agent, a job, a step, and a schedule. This directly satisfies the requirement to run a T-SQL script daily with low overhead.
- ✗
SQL Server Agent job on the Azure SQL Database logical server
Why it's wrong here
Azure SQL Database does not include SQL Server Agent. Agent is only available on Azure SQL Managed Instance and on-premises SQL Server. Therefore, a DBA cannot create a SQL Server Agent job directly on an Azure SQL Database logical server, making this option invalid for the scenario.
- ✗
Azure Automation runbook with a schedule and the Az.Sql module
Why it's wrong here
Azure Automation runbooks can run PowerShell or Python and can connect to Azure SQL Database, but they are not the most direct way to run a T-SQL script. While they can execute SQL, they require managing runbook code and credentials, adding overhead compared to native scheduling features. The scenario asks for minimal administrative overhead for a T-SQL script.
- ✗
Azure Logic Apps with a recurrence trigger and SQL Server connector
Why it's wrong here
Azure Logic Apps can schedule and run SQL queries via the SQL Server connector, but they are designed for workflow orchestration rather than database maintenance scripting. Using Logic Apps for a simple T-SQL script adds unnecessary complexity and cost. Elastic Database Jobs are purpose-built for scheduled T-SQL execution across Azure SQL databases.
Go deeper
Related to this question
Learn chapter
Optimizing Database Query and Index Performance
Key term
Azure SQL Performance Tuning
Azure SQL Performance Tuning is the process of optimizing the speed and efficiency of queries and database operations in Microsoft Azure SQL Database or SQL Managed Instance to reduce latency and improve throughput.
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 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-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.