DP-700 Implement and Manage an Analytics Solution Practice Question
Exhibit
{
"status": "Throttled",
"rejectedRequests": 450,
"smoothingWindow": "24 hours",
"currentUtilization": 1.15,
"operationType": "Background"
}Refer to the exhibit. Your Fabric capacity is showing a status of 'Throttled' for background operations. Based on the JSON snippet from the capacity monitoring logs, what is the most likely consequence for a new Spark Notebook scheduled to run immediately?
⚠ Common exam trap
Candidates often assume the system will queue the job and wait for capacity to become available, not realizing that 'Throttled' status triggers an immediate rejection of new background operations.
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 notebook will be rejected and fail to start.
Fabric uses a smoothing mechanism for capacity utilization. When background operations exceed the capacity (utilization > 1.0), the overage is spread over 24 hours. If the overage becomes too large, the capacity enters a throttled state where new background requests are rejected until the utilization drops below the threshold, ensuring stability.
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 notebook will run but at a reduced speed.
Why it's wrong here
Fabric does not typically 'slow down' individual operations like a traditional CPU might. Instead, it uses a rejection or queuing mechanism. If the capacity is already in a throttled state for background operations, a new request will generally be blocked entirely rather than allowed to run slowly.
- ✓
The notebook will be rejected and fail to start.
Why this is correct
When a capacity is throttled due to excessive background utilization (as indicated by the 1.15 utilization and rejected requests), new background tasks like scheduled notebooks are rejected. The system will not initiate new work until the smoothed utilization falls back within the limits of the provisioned capacity.
- ✗
The notebook will be automatically upgraded to an interactive task.
Why it's wrong here
The classification of a task as 'Background' or 'Interactive' is determined by how it is triggered (e.g., scheduled vs. manual run). The system does not dynamically change the type of a task to bypass throttling rules; both types have their own separate smoothing windows and throttling thresholds.
- ✗
The notebook will be moved to a different capacity automatically.
Why it's wrong here
Fabric does not automatically load-balance workloads across different capacities. A workspace is tied to a specific capacity, and if that capacity is overwhelmed, the tasks within that workspace will fail or be delayed. Moving workloads requires manual intervention by a capacity or workspace administrator.
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.