The correct action is to manually drop the problematic index using a DROP INDEX command. This is because while Azure SQL Database’s Automatic Tuning feature intelligently creates indexes to boost read performance, each new index adds overhead to write operations like updates and inserts, which can manifest as increased write latency. In the context of the DP-300 exam, this scenario tests your ability to surgically resolve a specific performance degradation without disabling the broader tuning mechanism—a common trap is assuming you must revert the entire CREATE INDEX option, but that would sacrifice the benefits of other helpful indexes. Instead, you target only the offending index, preserving automatic tuning for the rest of the workload. A useful memory tip: think of it as “drop the troublemaker, not the whole team”—you isolate and remove the single index causing write latency while keeping the automatic tuning engine active for all other indexes.
DP-300 Practice Question: Monitor, configure, and optimize database resources
This DP-300 practice question tests your understanding of monitor, configure, and optimize database resources. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are monitoring an Azure SQL Database using the Automatic Tuning feature. The database has a workload that is read-intensive. You enable the CREATE INDEX and DROP INDEX options. After a week, you observe that the database has created several new indexes automatically. However, you notice that one of the new indexes is causing increased write latency for an application that performs frequent updates. What should you do to resolve the issue without losing the benefits of automatic tuning for other indexes?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Manually drop the problematic index using a DROP INDEX command.
Option D is correct because manually dropping the problematic index allows you to resolve the specific performance issue caused by increased write latency while retaining the benefits of automatic tuning for other indexes. The Automatic Tuning feature in Azure SQL Database can create indexes to improve read performance, but these indexes may introduce overhead on write operations. By issuing a DROP INDEX command, you surgically remove only the offending index without disabling the overall tuning mechanism.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use the Azure portal to revert all automatic tuning recommendations for the past week.
Why it's wrong here
This would remove beneficial indexes as well.
✗
Manually create the missing indexes that were dropped by automatic tuning.
Why it's wrong here
This does not address the problematic index.
✗
Disable automatic tuning for the entire database.
Why it's wrong here
This would stop all automatic tuning, not just the problematic index.
✓
Manually drop the problematic index using a DROP INDEX command.
Why this is correct
You can manually revert a specific index while leaving automatic tuning active for other indexes.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may think disabling automatic tuning entirely or reverting all recommendations is necessary, but the correct approach is to manually drop only the problematic index to preserve the benefits of automatic tuning for other indexes.
Detailed technical explanation
How to think about this question
Automatic Tuning in Azure SQL Database uses machine learning to analyze query performance and recommend index creation or removal. When CREATE INDEX is enabled, the system may add nonclustered indexes to speed up read-heavy queries, but each additional index increases the cost of write operations (INSERT, UPDATE, DELETE) because the index must be maintained. In a read-intensive workload, a poorly chosen index can still degrade write performance; manually dropping it with DROP INDEX is the precise corrective action, as the tuning engine will not automatically revert a recent creation without further analysis.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-300 question in full detail.
Monitor, configure, and optimize database resources — This question tests Monitor, configure, and optimize database resources — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Manually drop the problematic index using a DROP INDEX command. — Option D is correct because manually dropping the problematic index allows you to resolve the specific performance issue caused by increased write latency while retaining the benefits of automatic tuning for other indexes. The Automatic Tuning feature in Azure SQL Database can create indexes to improve read performance, but these indexes may introduce overhead on write operations. By issuing a DROP INDEX command, you surgically remove only the offending index without disabling the overall tuning mechanism.
What should I do if I get this DP-300 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
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.
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.