Monitor, configure, and optimize database resources →mediumMultiple ChoiceObjective-mapped

DP-300 Practice Question: Monitor, configure, and optimize database resources

Exhibit

Refer to the exhibit.

```kusto
AzureDiagnostics
| where ResourceProvider == "MICROSOFT.SQL"
| where Category == "QueryStoreRuntimeStatistics"
| where database_name_s == "SalesDB"
| summarize avg_duration = avg(duration_s) by query_id_d, interval_start_time_t
| where avg_duration > 1000
| order by avg_duration desc
```

You run the above KQL query in Azure Monitor Log Analytics to investigate performance issues in SalesDB. What is the primary purpose of this query?

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

✓

Identify queries with high average duration

The query filters for queries with average duration > 1000 ms and orders by duration, identifying high-duration queries. Option B is wrong because plan changes are not detected. Option C is wrong because it does not sort by frequency. Option D is wrong because it does not compare across time intervals.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
Identify queries with high average duration
Why this is correct
Filters for avg_duration > 1000 ms and orders descending.
✗
Identify queries that have had plan changes
Why it's wrong here
No plan comparison is done.
✗
Find the most frequently executed queries
Why it's wrong here
It summarizes by avg_duration, not count.
✗
Compare query performance over different time intervals
Why it's wrong here
It doesn't compare intervals; it averages over intervals.

Go deeper

DP-300 Practice Question: Monitor, configure, and optimize database resources

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question