Demonstrate the capabilities of Power Apps →hardMultiple ChoiceObjective-mapped

PL-900 Demonstrate the capabilities of Power Apps Practice Question

Exhibit

Refer to the exhibit. The following is a Power Automate flow snippet used in a Power Apps app:

"triggers": {
  "manual": {
    "inputs": {
      "schema": {
        "type": "object",
        "properties": {
          "email": {
            "type": "string"
          },
          "score": {
            "type": "number"
          }
        }
      }
    }
  }
}

A Power Apps app calls a Power Automate flow with the trigger schema shown. The app passes an email string and a score number. However, the flow fails with a validation error. What is the most likely cause?

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 app is passing the parameters as individual strings instead of a JSON object

The trigger expects an object with properties 'email' and 'score'. If the app passes the parameters in a different order or as separate values instead of a JSON object, the flow fails. The schema is valid, and the types match.

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 app is passing the parameters as individual strings instead of a JSON object
Why this is correct
Correct: The trigger expects a JSON object with properties.
✗
The email property is misspelled
Why it's wrong here
There's no evidence of misspelling.
✗
The score property should be a string
Why it's wrong here
Schema expects number, which is correct.
✗
The flow trigger is set to 'When a HTTP request is received' instead of manual
Why it's wrong here
The exhibit shows manual trigger, which is correct.

Go deeper

PL-900 Demonstrate the capabilities of Power Apps Practice Question

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question