Demonstrate the capabilities of Power Automate →easyMultiple Choice

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?

⚠ Common exam trap

PL-900 often tests the misconception that changing a property's type or removing the top-level required array fixes missing nested properties, when the actual fix is to remove the specific property from the nested required array.

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 Parse JSON action validates the incoming payload against the schema, and if a property listed in the 'required' array is missing, the action fails. Since the error is specifically about a product object missing 'quantity', the fix is to remove 'quantity' from the required array inside the items schema so the property becomes optional. This allows the flow to continue processing payloads where quantity is absent.

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
The Parse JSON action validates incoming payloads against the schema's required fields, so a product object lacking 'quantity' fails validation. Removing 'quantity' from the required array makes the field optional, allowing the flow to process payloads where it is absent.
✗
Add 'items' to the top-level required array.
Why it's wrong here
Marking 'items' required at the top level only enforces that the array itself is present; it does nothing about a product object lacking 'quantity' inside the array. It suits guaranteeing the array exists. The fix is removing 'quantity' from the product object's required list.
✗
Change the type of 'quantity' to 'string'.
Why it's wrong here
Changing 'quantity' to string still leaves it in the required list, so a missing field fails validation regardless of type. String typing suits values like alphanumeric codes. The fix is deleting 'quantity' from the product object's required array so absent fields are tolerated.
✗
Remove the 'required' array from the top level.
Why it's wrong here
Removing the top-level required array permits the whole body to omit 'items', but the failure occurs inside the array, where the product object's own required list still demands 'quantity'. It suits optional top-level properties. The fix is removing 'quantity' from the product object's required list.

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