You have previously run a pipeline containing multiple activities. What's the best way to check how long each individual activity took to complete?

You have previously run a pipeline containing multiple activities. What's the best way to check how long each individual activity took to complete?

• A. View the run details in the run history
• B. Open the activity's telemetry in the monitoring pane
• C. View the Refreshed value for your lakehouse's default dataset
• D. Rerun the pipeline and observe the output, timing each activity

Answer: (A)

The key idea is to inspect execution details that are tied to a specific run. When you view the run history and open a particular pipeline run, you get a list of every activity that executed, with each one's status and the exact time it took from start to finish. This gives precise, per-activity durations for that run, making it straightforward to see which steps were slow and how long they required. Telemetry in the monitoring pane can offer useful metrics, but it isn’t as directly tied to the exact timing of each activity within a given run, and rerunning just to time things wastes time and doesn’t reflect what happened previously. The refreshed value for a lakehouse dataset isn’t related to execution timing. So, the most reliable way to check how long each individual activity took is to view the run details in the run history.

The key idea is to inspect execution details that are tied to a specific run. When you view the run history and open a particular pipeline run, you get a list of every activity that executed, with each one's status and the exact time it took from start to finish. This gives precise, per-activity durations for that run, making it straightforward to see which steps were slow and how long they required. Telemetry in the monitoring pane can offer useful metrics, but it isn’t as directly tied to the exact timing of each activity within a given run, and rerunning just to time things wastes time and doesn’t reflect what happened previously. The refreshed value for a lakehouse dataset isn’t related to execution timing. So, the most reliable way to check how long each individual activity took is to view the run details in the run history.