DP-700 Implement and Manage an Analytics Solution Practice Question
Exhibit
{
"capacityName": "fabric_cap_01",
"metrics": [
{ "time": "2023-10-01T12:00:00Z", "baseCU": 64, "percentUtilization": 125, "throttlingStatus": "Throttled" },
{ "time": "2023-10-01T12:05:00Z", "baseCU": 64, "percentUtilization": 110, "throttlingStatus": "Throttled" }
]
}Refer to the exhibit. An administrator is reviewing the capacity metrics for a Fabric F64 capacity. The logs indicate that the 'percentUtilization' has exceeded 100% and the 'throttlingStatus' is 'Throttled'. What is the most likely cause for this behavior in a Fabric environment?
⚠ Common exam trap
Candidates mistakenly blame instantaneous high CPU usage for throttling, overlooking how accumulated burst debt over time triggers the threshold.
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 cumulative 'debt' from previous burstable operations has exceeded the allowable limits.
Fabric uses a smoothing mechanism to handle bursts in activity. When utilization exceeds 100% of the purchased capacity, the system allows the burst but tracks the debt. If the debt becomes too large over a 24-hour period (for background tasks) or a shorter window (for interactive tasks), throttling occurs.
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 capacity has been paused by an automated script.
Why it's wrong here
If the capacity were paused, the utilization would drop to zero and the status would not be 'Throttled'; instead, the service would be unavailable. Throttling specifically refers to the intentional slowing or rejection of requests due to over-consumption of the allocated compute units over time.
- ✓
The cumulative 'debt' from previous burstable operations has exceeded the allowable limits.
Why this is correct
Fabric allows jobs to 'burst' by consuming more than the base CU. However, this creates a 'debt' that must be repaid. If the total consumption over the smoothing window exceeds the capacity's limits, Fabric throttles new requests to protect the system and ensure fair resource distribution.
- ✗
A user has manually capped the utilization at 100% in the Admin portal.
Why it's wrong here
There is no setting in the Fabric Admin portal to manually cap utilization at 100% to trigger throttling. Throttling is an automatic system response to resource exhaustion based on the SKU size and the smoothing logic applied to interactive and background workloads in the capacity.
- ✗
The OneLake storage limit has been reached, causing compute operations to fail.
Why it's wrong here
OneLake storage is virtually unlimited and billed based on usage; it does not have a 'limit' that would cause compute throttling. Throttling is strictly a function of the Capacity Units (CU) consumed by compute engines like Spark, SQL, and Power BI, not storage volume.
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.