The answer is workload classification. This is the correct choice because workload classification in Azure Synapse Analytics dedicated SQL pool allows you to assign incoming queries to specific workload groups with guaranteed minimum resource allocations, such as setting `REQUEST_MIN_RESOURCE_PERCENT` and `IMPORTANCE` via `CREATE WORKLOAD CLASSIFIER`. By classifying the weekly report queries into a high-importance group, the team ensures those reports always receive predictable resources, even when ad-hoc data scientist queries are running concurrently. On the Microsoft Azure Data Fundamentals DP-900 exam, this scenario tests your understanding of how to manage concurrency and resource governance in a dedicated SQL pool, often contrasting workload classification with workload isolation or resource classes. A common trap is confusing workload classification with workload groups themselves—remember that classification is the *routing* mechanism that assigns queries to groups, while the groups define the resource limits. For a memory tip, think of it as a VIP lane: classification puts the weekly reports in the express lane with guaranteed resources, while ad-hoc queries take the regular lane.
DP-900 Describe an analytics workload on Azure Practice Question
This DP-900 practice question tests your understanding of describe an analytics workload on azure. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
A data warehouse team uses Azure Synapse Analytics dedicated SQL pool to serve both business executives running weekly reports and data scientists running complex ad-hoc queries on large fact tables. The ad-hoc queries often consume excessive resources and degrade performance for the weekly reports. The team needs to ensure that the weekly reports always get guaranteed resources regardless of other concurrent queries. Which Synapse feature should they use?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "always"
Why it matters: Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
Correct. Workload classification assigns queries to workload groups with resource limits, ensuring critical queries get guaranteed resources.
B
Result set caching
Why wrong: Incorrect. Result set caching caches query results for reuse, but does not provide resource guarantees; a resource-intensive query could still block cache population.
C
Materialized views
Why wrong: Incorrect. Materialized views pre-aggregate data to speed up queries, but they do not isolate resources among concurrent workloads.
D
Columnstore indexes
Why wrong: Incorrect. Columnstore indexes improve compression and query performance, but they do not provide workload management or resource guarantees.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Workload classification
Workload classification in Azure Synapse Analytics dedicated SQL pool allows the team to assign incoming queries to specific workload groups with predefined resource allocations. By classifying the weekly report queries into a group with guaranteed minimum resources (e.g., using `CREATE WORKLOAD CLASSIFIER` with `IMPORTANCE` and `REQUEST_MIN_RESOURCE_PERCENT`), the team ensures those queries always receive the necessary resources, even when ad-hoc data scientist queries are running concurrently. This directly addresses the need for predictable performance for critical reports.
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.
✓
Workload classification
Why this is correct
Correct. Workload classification assigns queries to workload groups with resource limits, ensuring critical queries get guaranteed resources.
Clue confirmation
The clue word "always" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Result set caching
Why it's wrong here
Incorrect. Result set caching caches query results for reuse, but does not provide resource guarantees; a resource-intensive query could still block cache population.
✗
Materialized views
Why it's wrong here
Incorrect. Materialized views pre-aggregate data to speed up queries, but they do not isolate resources among concurrent workloads.
✗
Columnstore indexes
Why it's wrong here
Incorrect. Columnstore indexes improve compression and query performance, but they do not provide workload management or resource guarantees.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse performance optimization features (like caching, materialized views, or indexes) with resource governance features, mistakenly believing that making queries faster inherently guarantees resource availability, whereas workload classification is the only option that provides explicit resource isolation and guarantees.
Detailed technical explanation
How to think about this question
Under the hood, workload classification uses `CREATE WORKLOAD CLASSIFIER` to map queries (based on criteria like `MEMBERNAME`, `LABEL`, or `QUERYTAG`) to a workload group defined by `CREATE WORKLOAD GROUP`. The workload group can have `REQUEST_MIN_RESOURCE_PERCENT` set to guarantee a minimum percentage of resources (e.g., 20%), and `IMPORTANCE` (e.g., `HIGH`) to prioritize resource allocation over lower-importance queries. In a real-world scenario, a team might set the weekly report classifier to `IMPORTANCE = HIGH` and `REQUEST_MIN_RESOURCE_PERCENT = 25`, ensuring those queries always get at least 25% of the pool's resources, while ad-hoc queries run with lower importance and no minimum guarantee.
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-900 question in full detail.
Describe an analytics workload on Azure — This question tests Describe an analytics workload on Azure — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Workload classification — Workload classification in Azure Synapse Analytics dedicated SQL pool allows the team to assign incoming queries to specific workload groups with predefined resource allocations. By classifying the weekly report queries into a group with guaranteed minimum resources (e.g., using `CREATE WORKLOAD CLASSIFIER` with `IMPORTANCE` and `REQUEST_MIN_RESOURCE_PERCENT`), the team ensures those queries always receive the necessary resources, even when ad-hoc data scientist queries are running concurrently. This directly addresses the need for predictable performance for critical reports.
What should I do if I get this DP-900 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "always". Absolute qualifier. An answer using 'always' is only correct if there are genuinely no exceptions — absolute statements are often wrong in networking.
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-900 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-900 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.