DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing
Exhibit
Refer to the exhibit.
GET https://mysynapse.azuresynapse.net/monitoring/workloadManagement/workloadClassifiers?api-version=2020-12-01
Response:
{
"value": [
{
"name": "HeavyLoader",
"properties": {
"memberName": "LoaderGroup",
"wlmContext": {
"importance": "high",
"minPercentageResource": 30,
"maxPercentageResource": 100,
"capPercentageResource": 60,
"queryExecutionTimeoutSeconds": 0
}
}
},
{
"name": "ReportUser",
"properties": {
"memberName": "ReportGroup",
"wlmContext": {
"importance": "normal",
"minPercentageResource": 10,
"maxPercentageResource": 100,
"capPercentageResource": 50,
"queryExecutionTimeoutSeconds": 3600
}
}
}
]
}Refer to the exhibit. You are reviewing the workload classifier configuration for an Azure Synapse Analytics dedicated SQL pool. You notice that the 'HeavyLoader' classifier has a queryExecutionTimeoutSeconds of 0. What is the implication of this setting?
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
✓
Queries classified as 'HeavyLoader' will not have a timeout.
When queryExecutionTimeoutSeconds is set to 0, it means no timeout is enforced. Queries classified as 'HeavyLoader' can run indefinitely without being terminated by the timeout mechanism. Option A is incorrect because a value of 0 does not mean indefinite waiting for resources; it refers to the timeout duration. Option B is incorrect; 0 is a valid configuration that disables the timeout. Option D is incorrect; a timeout of 0 does not cause immediate timeout but rather no timeout.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Queries classified as 'HeavyLoader' will wait indefinitely for resources.
Why it's wrong here
No timeout does not mean waiting for resources; it means the query can run as long as needed.
- ✗
The configuration is invalid; queryExecutionTimeoutSeconds must be greater than 0.
Why it's wrong here
0 is a valid value meaning no timeout.
- ✓
Queries classified as 'HeavyLoader' will not have a timeout.
Why this is correct
A value of 0 disables the query execution timeout.
- ✗
Queries classified as 'HeavyLoader' will timeout immediately.
Why it's wrong here
0 means no timeout, not immediate.
Go deeper
Related to this question
About these practice questions
Courseiva writes every DP-203 question from scratch — 760 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-203 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-203 exam.