How can you best check how long each individual activity took to complete in a previously run pipeline?

Prepare for the DP-700 Microsoft Fabric Data Engineer Exam with flashcards and multiple choice questions. Study with hints and explanations, and ensure success on your certification exam!

Multiple Choice

How can you best check how long each individual activity took to complete in a previously run pipeline?

Explanation:
To see how long each activity took in a previously executed pipeline, check the pipeline’s run history and open a past run. The run details show the start and end times for every activity and provide the duration for each one. This lets you see exactly how long each step took in that specific run and spot any bottlenecks. In Fabric/Data Factory, you can navigate to the monitor or pipeline runs, pick a past run, and drill into each activity to view its timing. Rerunning would create a new run with new timings, so it doesn’t reveal past activity durations. The lakehouse dataset refresh is unrelated to execution timing, and portal metrics typically give overall or aggregated numbers rather than per-activity timings for a specific past run.

To see how long each activity took in a previously executed pipeline, check the pipeline’s run history and open a past run. The run details show the start and end times for every activity and provide the duration for each one. This lets you see exactly how long each step took in that specific run and spot any bottlenecks. In Fabric/Data Factory, you can navigate to the monitor or pipeline runs, pick a past run, and drill into each activity to view its timing.

Rerunning would create a new run with new timings, so it doesn’t reveal past activity durations. The lakehouse dataset refresh is unrelated to execution timing, and portal metrics typically give overall or aggregated numbers rather than per-activity timings for a specific past run.

Subscribe

Get the latest from Passetra

You can unsubscribe at any time. Read our privacy policy