Microsoft DP-700 Practice Test 31
Question 300
A pipeline reaches a manual Fail activity after validation rejects records. What should an operator do?
- Inspect the validation output and rejected data rather than disabling the Fail action.
- Grant the run identity the required destination write authorization on the target Fabric item or data path.
- Cast the expression operand to the required type and validate its source shape.
- Check for an empty lookup result before accessing the first row.
Explanation
Correct Answer
A:An intentional Fail represents a business guardrail; suppressing it could allow invalid data downstream. Correct sample invalid inputs and rerun validation.
Incorrect Answers
B:Successful connection authentication does not imply write permission at the sink; target data-plane rights must allow the requested operation.
C:Type mismatches break comparisons or arithmetic even when the pipeline syntax is otherwise valid.
D:Expression assumptions about a nonempty array cause runtime failures when no rows are returned.
Question 301
A file-event pipeline has a null event-path parameter when run manually. What is the likely remedy?
- Provide test parameters or use null-safe trigger metadata expressions for manual runs.
- Investigate the failing copy activity and its dependency chain before the notebook.
- Inspect the validation output and rejected data rather than disabling the Fail action.
- Grant the run identity the required destination write authorization on the target Fabric item or data path.
Explanation
Correct Answer
A:Event-supplied fields may be absent outside the file-event context; the pipeline must handle that explicitly. Compare parameter values under event and manual triggers.
Incorrect Answers
B:Success dependencies intentionally skip downstream work when prerequisites fail; editing the skipped notebook is irrelevant.
C:An intentional Fail represents a business guardrail; suppressing it could allow invalid data downstream.
D:Successful connection authentication does not imply write permission at the sink; target data-plane rights must allow the requested operation.
Question 302
A pipeline variable expression expects an integer but receives text. Which repair is appropriate?
- Cast the expression operand to the required type and validate its source shape.
- Inspect the validation output and rejected data rather than disabling the Fail action.
- Grant the run identity the required destination write authorization on the target Fabric item or data path.
- Provide test parameters or use null-safe trigger metadata expressions for manual runs.
Explanation
Correct Answer
A:Type mismatches break comparisons or arithmetic even when the pipeline syntax is otherwise valid. Test numeric and nonnumeric sample values.
Incorrect Answers
B:An intentional Fail represents a business guardrail; suppressing it could allow invalid data downstream.
C:Successful connection authentication does not imply write permission at the sink; target data-plane rights must allow the requested operation.
D:Event-supplied fields may be absent outside the file-event context; the pipeline must handle that explicitly.
Question 303
A Copy sink fails because a target table was renamed after promotion. Where should the fix occur?
- Update the resolved target table reference or environment parameter in the activity.
- Check for an empty lookup result before accessing the first row.
- Provide test parameters or use null-safe trigger metadata expressions for manual runs.
- Inspect the validation output and rejected data rather than disabling the Fail action.
Explanation
Correct Answer
A:A valid pipeline definition can still fail when external item names or stage bindings changed. Open the new target and run a small copy.
Incorrect Answers
B:Expression assumptions about a nonempty array cause runtime failures when no rows are returned.
C:Event-supplied fields may be absent outside the file-event context; the pipeline must handle that explicitly.
D:An intentional Fail represents a business guardrail; suppressing it could allow invalid data downstream.
Question 304
A pipeline rerun duplicates already loaded records in the target. What design issue should be corrected?
- Provide test parameters or use null-safe trigger metadata expressions for manual runs.
- Make the write path idempotent or checkpoint successfully completed source partitions.
- Check for an empty lookup result before accessing the first row.
- Update the resolved target table reference or environment parameter in the activity.
Explanation
Correct Answer
B:Retries can replay prior data; deterministic keys and commit tracking prevent duplicate logical output. Replay the same batch twice and compare keys.
Incorrect Answers
A:Event-supplied fields may be absent outside the file-event context; the pipeline must handle that explicitly.
C:Expression assumptions about a nonempty array cause runtime failures when no rows are returned.
D:A valid pipeline definition can still fail when external item names or stage bindings changed.
Question 305
A Dataflow Gen2 publish reports DestinationQueryNotFound after its output step was edited manually. What should be done?
- Reconcile the destination's partial writes rather than presuming the entire refresh was rolled back.
- Remove the broken destination definition, re-add the data destination, and publish again.
- Renew and reauthenticate the destination connection with valid principal credentials.
- Open the dataflow editor validation details rather than only examining previous refresh results.
Explanation
Correct Answer
B:The internal destination query is missing, so changing the source schedule will not restore destination metadata. Validate and republish the corrected dataflow.
Incorrect Answers
A:Cancellation can leave writes already made to data destinations, so idempotent recovery is needed.
C:The destination challenge is an authorization problem; destination columns do not repair rejected authentication.
D:Save or validation failures differ from refresh execution failures and require authoring diagnostics.
Question 306
A dataflow reports DestinationQueryChallenge after its service principal secret expired. What must be fixed?
- Reconcile the destination's partial writes rather than presuming the entire refresh was rolled back.
- Renew and reauthenticate the destination connection with valid principal credentials.
- Change the destination query to return a supported table, binary, or null value.
- Open the dataflow editor validation details rather than only examining previous refresh results.
Explanation
Correct Answer
B:The destination challenge is an authorization problem; destination columns do not repair rejected authentication. Test the new connection before refresh.
Incorrect Answers
A:Cancellation can leave writes already made to data destinations, so idempotent recovery is needed.
C:Destination outputs have supported type requirements; arbitrary lists are invalid for that destination contract.
D:Save or validation failures differ from refresh execution failures and require authoring diagnostics.
Question 307
A dataflow configured through CI/CD has two destination queries attached to one source query. Which fix matches MultipleDestinationQueries?
- Reassign or remediate the affected dataflow and connection/staging ownership according to supported guidance.
- Remove the conflicting duplicate destination configuration or split outputs into separate queries.
- Compare current destination schema and column mapping, then correct the configured destination.
- Renew and reauthenticate the destination connection with valid principal credentials.
Explanation
Correct Answer
B:The standard authoring contract allows one destination per query; duplicate configurations can fail validation. Publish after the definition is normalized.
Incorrect Answers
A:Refresh may depend on credentials or staging artifacts tied to a former user, not only the transformation M logic.
C:Destination validation checks compatibility and access at refresh; source data transformation alone may not match new target columns.
D:The destination challenge is an authorization problem; destination columns do not repair rejected authentication.
Question 308
A Dataflow Gen2 destination query returns a list instead of a table or supported type. What issue does this cause?
- Change the destination query to return a supported table, binary, or null value.
- Compare current destination schema and column mapping, then correct the configured destination.
- Reassign or remediate the affected dataflow and connection/staging ownership according to supported guidance.
- Reconcile the destination's partial writes rather than presuming the entire refresh was rolled back.
Explanation
Correct Answer
A:Destination outputs have supported type requirements; arbitrary lists are invalid for that destination contract. Run validation with the corrected query result.
Incorrect Answers
B:Destination validation checks compatibility and access at refresh; source data transformation alone may not match new target columns.
C:Refresh may depend on credentials or staging artifacts tied to a former user, not only the transformation M logic.
D:Cancellation can leave writes already made to data destinations, so idempotent recovery is needed.
Question 309
A refresh fails when its original connection owner leaves the organization. Which operational dependency must be addressed?
- Reconcile the destination's partial writes rather than presuming the entire refresh was rolled back.
- Reassign or remediate the affected dataflow and connection/staging ownership according to supported guidance.
- Remove the conflicting duplicate destination configuration or split outputs into separate queries.
- Remove the broken destination definition, re-add the data destination, and publish again.
Explanation
Correct Answer
B:Refresh may depend on credentials or staging artifacts tied to a former user, not only the transformation M logic. Review exact refresh error and available support path.
Incorrect Answers
A:Cancellation can leave writes already made to data destinations, so idempotent recovery is needed.
C:The standard authoring contract allows one destination per query; duplicate configurations can fail validation.
D:The internal destination query is missing, so changing the source schedule will not restore destination metadata.
Question 310
A Dataflow Gen2 refresh is canceled after it has written some rows to its destination. What should downstream logic assume?
- Reconcile the destination's partial writes rather than presuming the entire refresh was rolled back.
- Remove the broken destination definition, re-add the data destination, and publish again.
- Reassign or remediate the affected dataflow and connection/staging ownership according to supported guidance.
- Open the dataflow editor validation details rather than only examining previous refresh results.
Explanation
Correct Answer
A:Cancellation can leave writes already made to data destinations, so idempotent recovery is needed. Compare destination row counts with last complete run.
Incorrect Answers
B:The internal destination query is missing, so changing the source schedule will not restore destination metadata.
C:Refresh may depend on credentials or staging artifacts tied to a former user, not only the transformation M logic.
D:Save or validation failures differ from refresh execution failures and require authoring diagnostics.
