nerdexam
Microsoft

DP-700 · Question #66

You have a Fabric warehouse named DW1 that loads data by using a data pipeline named Pipeline1. Pipeline1 uses a Copy data activity with a dynamic SQL source. Pipeline1 is scheduled to run every 15…

The correct answer is B. From Monitoring hub, select the latest failed run of Pipeline1, and then view the input JSON. To identify the specific dynamic SQL query that caused a pipeline failure, you should examine the input JSON of the failed pipeline run in the Monitoring hub, which contains the parameters and configurations used.

Monitor and optimize a data analytics solution

Question

You have a Fabric warehouse named DW1 that loads data by using a data pipeline named Pipeline1. Pipeline1 uses a Copy data activity with a dynamic SQL source. Pipeline1 is scheduled to run every 15 minutes. You discover that Pipeline1 keeps failing. You need to identify which SQL query was executed when the pipeline failed. What should you do?

Options

  • AFrom Monitoring hub, select the latest failed run of Pipeline1, and then view the output JSON.
  • BFrom Monitoring hub, select the latest failed run of Pipeline1, and then view the input JSON.
  • CFrom Real-time hub, select Fabric events, and then review the details of Microsoft.Fabric.ItemReadFailed.
  • DFrom Real-time hub, select Fabric events, and then review the details of Microsoft.Fabric.ItemUpdateFailed.

How the community answered

(22 responses)
  • A
    5% (1)
  • B
    77% (17)
  • C
    9% (2)
  • D
    9% (2)

Why each option

To identify the specific dynamic SQL query that caused a pipeline failure, you should examine the input JSON of the failed pipeline run in the Monitoring hub, which contains the parameters and configurations used.

AFrom Monitoring hub, select the latest failed run of Pipeline1, and then view the output JSON.

The output JSON typically contains results, metrics, and error messages from the activity's completion, but not necessarily the specific input SQL query that caused the failure during execution.

BFrom Monitoring hub, select the latest failed run of Pipeline1, and then view the input JSON.Correct

When a pipeline with a dynamic SQL source fails, the actual SQL query executed is part of the activity's input parameters. Viewing the input JSON for the specific failed run in the Monitoring hub will reveal the exact SQL statement that was passed to the source, helping to diagnose the failure.

CFrom Real-time hub, select Fabric events, and then review the details of Microsoft.Fabric.ItemReadFailed.

Real-time hub Fabric events like 'ItemReadFailed' provide high-level failure notifications but usually lack the granular details of activity inputs, such as the dynamic SQL query.

DFrom Real-time hub, select Fabric events, and then review the details of Microsoft.Fabric.ItemUpdateFailed.

'ItemUpdateFailed' refers to failures in updating a Fabric item, which is distinct from the failure of a specific pipeline activity due to an erroneous SQL query.

Concept tested: Debugging Fabric pipeline failures with dynamic SQL

Source: https://learn.microsoft.com/en-us/azure/data-factory/monitor-pipeline?tabs=data-factory

Topics

#Pipeline Monitoring#Troubleshooting#Copy Data Activity#Dynamic SQL

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full DP-700 Practice