DP-700 Monitor and Optimize an Analytics Solution Practice Question
Exhibit
Error: Capacity limit exceeded. Request rejected. Status: 429
Refer to the exhibit. You are reviewing pipeline logs and notice the 429 error. What is the most appropriate long-term action to prevent this?
⚠ Common exam trap
Candidates frequently select immediate capacity SKU upgrades as the primary answer, missing the prompt's focus on long-term prevention through code and query optimization.
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
✓
Analyze query patterns and optimize resource-heavy jobs
A 429 error indicates that the request was throttled because the capacity reached its compute limit. While immediate scaling might fix the current issue, long-term stability requires identifying the root cause of the spike in resource usage. Optimizing the code, adjusting concurrency, or smoothing out scheduled job times ensures the capacity operates within its allocated limits without requiring constant upgrades.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the Fabric capacity SKU immediately
Why it's wrong here
While upgrading the SKU provides more headroom, it is a costly reactive measure. Without first optimizing the underlying data processes that are causing the capacity spikes, the new capacity may eventually face the same throttling issues as the workloads continue to scale ineffectively.
- ✗
Configure retry policies with exponential backoff
Why it's wrong here
Implementing exponential backoff is a best practice for handling transient errors and throttling in distributed systems. However, this is a mitigation technique that handles the symptom rather than solving the underlying resource contention caused by poorly performing or overlapping data jobs.
- ✓
Analyze query patterns and optimize resource-heavy jobs
Why this is correct
Optimizing resource-intensive jobs is the most sustainable way to resolve 429 errors. By improving query efficiency, reducing data volume, or staggering pipeline executions, you ensure that the current capacity can handle the workload without hitting the hard compute limits defined by the service.
- ✗
Disable monitoring to reduce overhead
Why it's wrong here
Disabling monitoring is never an appropriate solution, as it eliminates visibility into system health. Without logs and metrics, you would have no way of knowing when your pipelines are failing, and you would be unable to perform the necessary troubleshooting to resolve performance degradation.
About these practice questions
This DP-700 question is part of Courseiva's 152-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.