DP-700 Ingest and Transform Data Practice Question
You are monitoring a Data Factory pipeline. What is the best way to be notified when a pipeline fails during an execution?
⚠ Common exam trap
Candidates often incorrectly select Azure Monitor or Log Analytics as the primary method, failing to realize that Fabric’s built-in monitoring hub is the native, direct solution for pipeline failure notifications.
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
✓
Use the alerts in the monitoring hub
Fabric pipeline monitoring can be enhanced using alerts configured within the monitoring hub or by utilizing Microsoft Fabric's integration with Azure Monitor/Log Analytics. By setting up alert rules based on pipeline status, you ensure proactive notification, allowing for rapid response and troubleshooting. This is a critical operational practice for maintaining high-reliability data systems, as it reduces downtime and ensures data quality standards are consistently met.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Manually refresh the monitor tab
Why it's wrong here
Manual monitoring is inefficient and reactive. It does not scale to handle complex enterprise environments with many pipelines. Relying on manual checks will lead to delayed problem detection and potential data quality issues, making it an inferior approach compared to automated, policy-driven alerting systems.
- ✓
Use the alerts in the monitoring hub
Why this is correct
The monitoring hub in Fabric provides built-in capabilities to set up alerts. By configuring these, you can receive notifications immediately upon failure. This proactive approach is the standard recommended practice for maintaining pipeline reliability and operational excellence in Microsoft Fabric, ensuring you stay informed without needing constant manual oversight.
- ✗
Check the SQL database logs
Why it's wrong here
SQL logs only show database-level errors. Pipeline-level failures (like network timeout or orchestration errors) will not appear in the database logs. Relying on database logs provides an incomplete view of the pipeline's health, leading to missed errors and inaccurate reporting on the overall status of your integration.
- ✗
Run a daily Notebook to check status
Why it's wrong here
This approach is overly complex and introduces an extra dependency on a Notebook just to monitor status. It is slower than native alert mechanisms and does not provide real-time feedback. Alerting should be a native configuration of the pipeline platform, not a custom-coded task that requires maintenance.
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.