Demonstrate the capabilities of Power Automate →hardMultiple ChoiceObjective-mapped

PL-900 Practice Question: Demonstrate the capabilities of Power Automate

Exhibit

{
  "definition": {
    "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
    "actions": {
      "Send_approval_email": {
        "type": "ApiConnection",
        "inputs": {
          "host": {
            "connectionName": "shared_office365",
            "operationId": "SendEmail"
          },
          "parameters": {
            "to": "manager@contoso.com",
            "subject": "Approve request",
            "body": "Please approve."
          },
          "authentication": "@parameters('$authentication')"
        },
        "runAfter": {}
      }
    },
    "triggers": {
      "manual": {
        "type": "Request",
        "kind": "Http",
        "inputs": {
          "schema": {}
        }
      }
    }
  }
}

Refer to the exhibit. This Power Automate flow is triggered manually via HTTP request. The action 'Send_approval_email' sends an email. What is a potential issue with this flow design?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The flow does not include an approval action, only an email notification.

The flow lacks an approval action; it only sends an email notification. To implement an approval process, a 'Start and wait for an approval' action must be included. Option A is wrong because the 'When an HTTP request is received' trigger can be used for manual or external triggers. Option B is wrong because email actions in Power Automate authenticate via the connection, not explicit authentication parameters. Option D is wrong because the 'Send an email' action supports required parameters like To, Subject, and Body, which are not deprecated.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✗
The manual trigger cannot be used for HTTP requests.
Why it's wrong here
Manual trigger with kind Http is valid.
✗
The authentication parameter is missing.
Why it's wrong here
Authentication is referenced via parameters.
✓
The flow does not include an approval action, only an email notification.
Why this is correct
There is no 'Start and wait for an approval' action; it directly sends an email.
✗
The email action uses deprecated parameters.
Why it's wrong here
Parameters are standard.

Go deeper

PL-900 Practice Question: Demonstrate the capabilities of Power Automate

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question