Demonstrate the capabilities of Power Automate →easyMultiple ChoiceObjective-mapped

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

Exhibit

{
  "type": "object",
  "properties": {
    "customerName": {
      "type": "string"
    },
    "orderAmount": {
      "type": "number"
    },
    "items": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "productId": {
            "type": "string"
          },
          "quantity": {
            "type": "integer"
          }
        },
        "required": ["productId", "quantity"]
      }
    }
  },
  "required": ["customerName", "orderAmount"]
}

Refer to the exhibit. You are designing a Power Automate flow that receives an HTTP request with a JSON body. You use the 'Parse JSON' action with the schema shown. The flow fails when the incoming JSON contains an 'items' array with a product object missing the 'quantity' field. What is the best way to fix this?

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

✓

Remove 'quantity' from the required array inside the items schema.

The schema defines 'quantity' as required in each item. To make it optional, you should remove it from the 'required' array inside the items schema. Option B is wrong because the 'items' array itself is not required. Option C is wrong because changing the type to 'string' is incorrect. Option D is wrong because the issue is in the child object, not the parent.

Answer analysis

Option-by-option breakdown

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

✓
Remove 'quantity' from the required array inside the items schema.
Why this is correct
Makes quantity optional.
✗
Add 'items' to the top-level required array.
Why it's wrong here
Items is optional.
✗
Change the type of 'quantity' to 'string'.
Why it's wrong here
Not a type issue.
✗
Remove the 'required' array from the top level.
Why it's wrong here
Top-level required fields are fine.

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