DP-700 Monitor and Optimize an Analytics Solution Practice Question
A Data Factory pipeline in Fabric fails during the execution of a Copy activity. You need to find the specific error message and the number of rows successfully written before the failure. Where should you look?
⚠ Common exam trap
Candidates tend to check workspace-level logs or Spark event logs, failing to realize that individual activity outputs in the Monitoring Hub contain exact row metrics and error codes.
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 pipeline run details in the Monitoring Hub
Data Factory in Fabric provides detailed execution logs for every activity within a pipeline. Accessing the output of a specific activity allows you to see the error codes and performance metrics like rows read and written. This is the first step in troubleshooting data movement issues and identifying data quality problems.
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 Spark UI environment logs
Why it's wrong here
Copy activities in Data Factory do not necessarily run on Spark unless specifically configured to use a Spark-based connector or notebook. Checking Spark logs for a standard Copy activity would likely yield no information, as the execution occurs within the Data Integration service rather than a Spark cluster.
- ✓
The pipeline run details in the Monitoring Hub
Why this is correct
The Monitoring Hub allows you to drill down into the specific pipeline run and then into the activity details. Clicking the 'output' icon for the failed Copy activity provides a JSON response containing the error message and the execution statistics, including the row counts for both source and destination.
- ✗
The OneLake data access logs
Why it's wrong here
OneLake data access logs show who accessed which files and when, but they do not contain the internal logic or failure details of a Data Factory pipeline. These logs are security-focused and lack the row-level telemetry or activity-specific error messages required for debugging a failed pipeline execution.
- ✗
The Capacity Metrics 'Overages' view
Why it's wrong here
The Overages view tracks compute usage against the capacity limit and would show if a pipeline was throttled, but it cannot provide the specific reason for a logic failure or row count statistics. Throttling and activity failures are distinct events that require different tools for proper analysis and resolution.
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.