Automatic Tuning Options in Azure SQL Database
You are configuring automatic tuning for an Azure SQL Database. The database has a heavy OLTP workload. You want to automatically correct query plan choice regressions without manual intervention. Which automatic tuning option should you enable?
⚠ Common exam trap
It's easy for candidates to confuse index tuning options (CREATE_INDEX, DROP_INDEX) with query plan regression correction, mistakenly thinking that creating or dropping indexes will fix a plan choice regression, when in fact FORCE_LAST_GOOD_PLAN is the specific feature designed for that purpose.
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
✓
FORCE_LAST_GOOD_PLAN
FORCE_LAST_GOOD_PLAN, is the correct automatic tuning option for Azure SQL Database to automatically correct query plan choice regressions. When the database engine detects that a newly compiled query plan performs worse than the previously known good plan, it can automatically force the last known good plan without manual intervention, which is ideal for a heavy OLTP workload where performance stability is critical.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
DROP_INDEX
Why it's wrong here
DROP_INDEX reverts an index that automatic tuning created, so it cannot correct a regressed query plan; plan-choice regression is handled by FORCE_LAST_GOOD_PLAN, which pins the previously efficient plan. DROP_INDEX is correct when an auto-created index proves harmful to the workload.
- ✗
CREATE_INDEX
Why it's wrong here
CREATE_INDEX identifies and builds missing indexes; it does not detect or revert plan-choice regressions, so it cannot satisfy the stem's requirement. It is tempting because it is an automatic tuning action on the same blade, but its mechanism is index creation, whereas plan regression needs FORCE_LAST_GOOD_PLAN.
- ✗
CORRECT_INDEX
Why it's wrong here
CORRECT_INDEX is not a valid automatic tuning option; the index-related setting is CREATE_INDEX, which adds missing indexes rather than fixing plan regressions. FORCE_LAST_GOOD_PLAN detects plan choice regressions and reverts to the last known good plan. CREATE_INDEX suits workloads where missing indexes, not regressed plans, cause poor performance.
- ✓
FORCE_LAST_GOOD_PLAN
Why this is correct
FORCE_LAST_GOOD_PLAN detects plan-choice regressions by comparing a query's performance against its previous good plan, then forces the earlier plan automatically. This satisfies the OLTP requirement to correct regressions without manual intervention, unlike CREATE INDEX or DROP INDEX tuning options.
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 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.