Check Your Knowledge

1.

You create a cloud flow that triggers from a pipeline gate. The flow runs for all pipelines instead of the specific one that it's intended for. Which action should you take to correct this issue?

Change the name of the cloud flow to include the pipeline name.

Define a trigger condition with the pipeline name.

Change the connection for Dataverse to a service principal.

2.

You create a cloud flow that a pipeline gate triggers for a specific deployment stage. The flow runs successfully but the pipeline doesn't move beyond this gate. How can you ensure that the pipeline continues its implementation after this flow?

Validate that the unbound action that relates to the gate triggers from this flow.

Add a filter condition to trigger the flow only at the expected deployment stage.

Configure the pipeline with an additional gate.

3.

You extend a pipeline with an approval cloud flow. The flow runs and the approval processes. After the gate, the deployment always stops. What should you do?

Configure the flow with a single unbound action to return 20 (success) after the approval action.

Configure the unbound action return parameter to 20 (success) for the approved branch.

Add an unbound action with the pending (10) status before triggering the approval action.

4.

You create a cloud flow that triggers from a pipeline named Extend a Pipeline Demo. The trigger condition is @equals(triggerOutputs()?['body/OutputParameters/DeploymentPipelineName'], 'Extend a pipeline demo'). The flow doesn't run when this pipeline triggers a deployment. What should you do?

Adjust the trigger condition by placing double quotes (“) around the pipeline name.

Change the name of the cloud flow to be identical to the pipeline name.

Adjust the trigger condition to match the pipeline name by using the same case and syntax as the original pipeline name.

Answer the following questions to see what you learned.

Feedback