Question 870 of 919
Automate Index Maintenance in Azure SQL Database: Native Options
Which TWO of the following are native options to automate index maintenance on Azure SQL Database? (Select exactly two.)
Quick Answer
The answer is enabling automatic tuning with 'CREATE INDEX' and 'DROP INDEX' options, along with Elastic Database Jobs. These are the two native options to automate index maintenance in Azure SQL Database because automatic tuning uses built-in intelligence to continuously analyze query performance and automatically create or drop indexes as needed, while Elastic Database Jobs allow you to schedule and run custom T-SQL scripts for index maintenance across multiple databases. On the Microsoft Azure Database Administrator Associate DP-300 exam, this question tests your understanding of what is natively available versus what requires external tools—a common trap is assuming SQL Agent works in Azure SQL Database, but it is only available on SQL Server and Azure SQL Managed Instance. Remember that Azure SQL Database lacks SQL Agent, so for automation you rely on automatic tuning for index management and Elastic Jobs for custom scripts. A helpful memory tip: think "auto-tune for auto-index, Elastic Jobs for manual scripts."
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
✓
Create Elastic Database Jobs that run index maintenance T-SQL scripts.
Options A and C are correct. Elastic Database Jobs (Option A) allow running custom T-SQL scripts for index maintenance across databases. Automatic tuning (Option C) can automatically create and drop indexes based on workload patterns, which is a form of index maintenance. Option B is incorrect because Azure Automation PowerShell runbooks are not a native option for Azure SQL Database index maintenance; they would require additional setup and do not directly execute T-SQL. Option D is incorrect because SQL Agent jobs are not available in Azure SQL Database (they are available in SQL Server on-premises or on Azure VMs). Option E is incorrect because Azure Data Factory is primarily for data movement and orchestration, not for direct 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.
- ✓
Create Elastic Database Jobs that run index maintenance T-SQL scripts.
Why this is correct
Elastic Jobs can automate T-SQL index maintenance across databases.
- ✗
Use Azure Automation PowerShell runbooks to invoke index rebuilds.
Why it's wrong here
PowerShell runbooks are not native to SQL and require intermediate scripting.
- ✓
Enable automatic tuning with 'CREATE INDEX' and 'DROP INDEX' options.
Why this is correct
Automatic tuning automates index management based on workload.
- ✗
Schedule SQL Agent jobs with ALTER INDEX statements.
Why it's wrong here
SQL Agent is not available in Azure SQL Database.
- ✗
Use Azure Data Factory to copy data and rebuild indexes.
Why it's wrong here
Data Factory is not designed for index maintenance.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on DP-300
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. You are configuring automated performance tuning for an Azure SQL Database. You want to automatically create missing indexes and drop unused indexes, but you need to prevent automatic index creation during peak business hours (9 AM - 5 PM). What is the best approach?
hard- A.Enable automatic indexing in Azure SQL Database and rely on the system to decide when to create indexes.
- ✓ B.Enable automatic tuning but set the 'INDEX_CREATE' option to 'OFF' and use a schedule to run a script that enables it during off-peak hours and disables during peak hours.
- C.Use SQL Server Agent to schedule index creation scripts that check for missing indexes.
- D.Use Azure Automation to run index analysis scripts only during off-peak hours.
Why B: It leverages Azure SQL Database's built-in automatic tuning feature while still allowing you to enforce a schedule. By setting the 'INDEX_CREATE' option to 'OFF' and using a script (e.g., via Azure Automation or SQL Server Agent) to toggle it on during off-peak hours and off during peak hours, you can automatically create missing indexes outside the prohibited window. This approach combines the intelligence of automatic tuning with your scheduling requirement. Option A does not allow scheduling; Option C relies on manual scripts without the built-in tuning intelligence; Option D is similar to B but less integrated with automatic tuning.
Last reviewed: Jun 21, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.