DP-700 Monitor and Optimize an Analytics Solution Practice Question
In Microsoft Fabric, you notice that a background job (such as a Dataflow refresh) is taking significantly longer than usual, even though the total Capacity Unit (CU) usage is below the limit. What is the most likely cause of this behavior based on Fabric's capacity management rules?
⚠ Common exam trap
Candidates often think background jobs execute immediately based on current low CU usage, forgetting that Fabric smooths background operations over a 24-hour window.
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 job is being smoothed over a 24-hour window.
Fabric manages capacity by smoothing the consumption of CUs over time. Background operations are smoothed over a 24-hour window, while interactive operations are smoothed over 5 minutes. If a capacity was previously over-utilized, background jobs may be delayed by the system to prevent further overages, even if current usage appears low on the dashboard.
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 background job has been rejected by the system.
Why it's wrong here
If a job is rejected, it fails immediately with an error message rather than running slowly. Taking longer than usual suggests that the job is being throttled or deprioritized by the capacity's scheduler rather than being blocked entirely from starting due to severe overage or policy violations.
- ✓
The job is being smoothed over a 24-hour window.
Why this is correct
Fabric's smoothing policy means that the impact of a heavy background job is spread out over 24 hours. If there was a large spike in usage earlier, the system may delay the allocation of CUs to new background tasks to stay within the average limit, causing them to take longer to complete.
- ✗
The SQL Analytics Endpoint has higher priority than Dataflows.
Why it's wrong here
While interactive tasks (like SQL queries) have a shorter smoothing window, they do not inherently 'starve' background tasks unless the capacity is completely exhausted. The delay in background tasks is usually a result of their own 24-hour smoothing logic and the cumulative carryover of CU consumption from previous timepoints.
- ✗
The workspace is in a 'Trial' capacity which lacks background processing.
Why it's wrong here
Trial capacities in Microsoft Fabric support both interactive and background processing just like paid capacities, although they have lower total CU limits. The slow performance is not due to a lack of support for the feature, but rather the standard resource management and smoothing algorithms applied to all capacity types.
About these practice questions
One of 152 original DP-700 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This DP-700 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-700 exam.