DP-700 Monitor and Optimize an Analytics Solution Practice Question
Exhibit
{
"capacityId": "F-SKU-64-PROD",
"metrics": [
{ "metricName": "CUPercent", "value": 98.5 },
{ "metricName": "BackgroundOverage", "value": 120.0 },
{ "metricName": "InteractiveOverage", "value": 0.0 }
],
"throttling": "Active"
}Refer to the exhibit. You are reviewing the capacity state for a production Fabric environment. Based on the JSON output from the monitoring API, what is the most likely impact on users and what should be your immediate action?
⚠ Common exam trap
Candidates mistakenly assume interactive user reports are failing completely, missing that smoothing primarily impacts background jobs before degrading interactive experiences.
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
✓
Background jobs are being delayed; optimize or reschedule ETL tasks.
Fabric uses a smoothing algorithm to handle spikes in resource usage. When background overage is high and throttling is active, it indicates that past background tasks (like refreshes) have exceeded the capacity's limit and are now 'borrowing' from future CUs. This will eventually lead to delays in starting new background jobs, though interactive reports might still function temporarily.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Interactive reports will stop working immediately; upgrade the SKU.
Why it's wrong here
Fabric prioritizes interactive operations over background ones. While the CU percentage is high, the Interactive Overage is zero, meaning interactive users might not see an immediate failure yet. Upgrading the SKU is a valid long-term fix, but the assessment of immediate total failure for interactive users is incorrect.
- ✓
Background jobs are being delayed; optimize or reschedule ETL tasks.
Why this is correct
The exhibit shows significant Background Overage and active throttling. In Fabric, this means that background tasks have consumed more than their allotted share, and the system is now delaying new background operations to stay within the smoothed CU limits. Rescheduling these tasks to off-peak times is the best mitigation.
- ✗
The capacity is healthy; ignore the warning as smoothing is active.
Why it's wrong here
The 'Throttling: Active' status indicates the capacity is not in a healthy state. While smoothing allows for temporary spikes, reaching a state where throttling is actively enforced means the overage has exceeded the allowed window, and performance for background operations will be negatively impacted until the overage clears.
- ✗
Data loss is occurring in OneLake; check the transaction logs.
Why it's wrong here
Capacity throttling in Microsoft Fabric affects the compute layer (processing) rather than the storage layer (OneLake). Throttling will cause delays in execution or failures to start new jobs, but it does not inherently cause data loss or corruption within the underlying Delta tables or OneLake storage files.
About these practice questions
Courseiva writes every DP-700 question from scratch — 152 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 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.