DP-300 Practice Question: Monitor, configure, and optimize database resources
Exhibit
Refer to the exhibit.
```json
{
"properties": {
"name": "MyWorkloadClassifier",
"context": {
"memberName": "AzureSQL\User1",
"databaseName": "SalesDB"
},
"importance": "high",
"min_percentile_resource": 10,
"max_percentile_resource": 100,
"cap_percentile_resource": 100
}
}You are configuring workload management for an Azure SQL Database using the JSON exhibit above for a classifier named 'MyWorkloadClassifier'. The classifier is intended to assign high importance to queries from user 'User1' in the 'SalesDB' database. However, after deployment, you notice that queries from 'User1' are not getting the expected resource guarantees. What is the most likely reason?
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
✓
The 'memberName' in the context is not correctly formatted; it should be a single user or group name without a backslash.
The most likely reason is that the classifier's context is incorrectly formatted. In Azure SQL Database workload management, the 'memberName' property within the classifier context must be specified as a single user or group name without a backslash. If the JSON exhibit contains a backslash (e.g., 'SalesDB\User1' instead of 'User1'), the classifier fails to match the user. Option A is incorrect because 'importance' is a string ('high'), not an integer. Option C is incorrect because 'min_percentile_resource' is not the issue; resource guarantees depend on the workload group's allocation. Option D is incorrect because a classifier does not need to be associated with a workload group directly; it is defined at the database level.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The 'importance' property is set to 'high' but the classifier requires 'importance' to be an integer.
Why it's wrong here
'importance' is a string with values 'low', 'normal', 'high'.
- ✓
The 'memberName' in the context is not correctly formatted; it should be a single user or group name without a backslash.
Why this is correct
The backslash is not a valid JSON escape; memberName should be a simple user name like 'User1'.
- ✗
The 'min_percentile_resource' value is too low to guarantee resources.
Why it's wrong here
The value 10% is acceptable for guaranteeing at least 10% resources.
- ✗
The classifier is not associated with a workload group.
Why it's wrong here
Classifiers can be created independently and assigned to workload groups via the 'group_name' property, which is missing here.
Go deeper
Related to this question
Learn chapter
Overview of Azure Data Platform Options
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
One of 906 original DP-300 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.