DP-900 Describe an analytics workload on Azure Practice Question
A company uses Azure Synapse Analytics to run both interactive queries and large batch loads. The interactive queries must have consistent performance regardless of batch load activity. Which Synapse feature should the company use?
⚠ Common exam trap
Many exam-takers confuse performance optimization features like caching or materialized views with resource governance features, assuming they provide isolation when they only improve query speed without guaranteeing resource availability.
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
✓
Workload management with workload isolation.
Workload management with workload isolation in Azure Synapse Analytics allows you to reserve resources for specific workloads, such as interactive queries, ensuring they have consistent performance even when large batch loads are running. By creating a workload group with 'REQUEST_MIN_RESOURCE_PERCENT' set to a non-zero value, you guarantee a minimum amount of resources are always available for that group, preventing contention from other workloads.
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 management with workload isolation.
Why this is correct
Workload management with workload isolation in Azure Synapse uses workload groups and classifiers to assign queries to groups with a reserved amount of resources, such as MIN_PERCENTAGE_RESOURCE. This guarantees that critical queries receive a defined proportion of compute capacity, preventing concurrent workloads from starving them. Unlike caching or compression, it actively enforces resource allocation rather than simply speeding up individual queries.
- ✗
Result-set caching for frequently run queries.
Why it's wrong here
Result-set caching stores the output of a query and quickly serves it for repeated requests as long as the underlying data and query parameters are unchanged. It reduces query execution time and compute usage, but it does not set aside any compute resources for a particular workload. When other heavy queries compete for the same pool, the cached query still has no reserved capacity and may be delayed or queued.
- ✗
Materialized views for aggregate data.
Why it's wrong here
Materialized views in Azure Synapse precompute and store aggregate or joined results, and the query optimizer automatically rewrites compatible queries to use them. This speeds up reporting by avoiding repetitive expensive scans, but it provides no scheduler-level guarantee or resource reservation. If many concurrent workloads exceed the pool's capacity, queries touching materialized views still contend for the same resources.
- ✗
Data compression with columnstore indexes.
Why it's wrong here
Data compression with columnstore indexes reduces on-disk size and typically improves I/O efficiency by scanning fewer compressed pages. That reduces storage costs and may lower latency, but it does not affect the allocation of compute slots or memory to different workloads. A concurrent workload can still consume all available resources, leaving compressed queries waiting in the same queue as uncompressed ones.
Go deeper
Related to this question
About these practice questions
Courseiva writes every DP-900 question from scratch — 820 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-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.