Describe the business value of Microsoft Power Platform →hardMultiple Choice

PL-900 Practice Question: Describe the business value of Microsoft Power Platform

Exhibit

Refer to the exhibit.
```json
{
  "name": "New Employee Onboarding",
  "triggers": {
    "manual": true,
    "schedule": {
      "frequency": "Day",
      "interval": 1,
      "startTime": "2026-05-01T08:00:00Z"
    }
  },
  "actions": [
    {
      "type": "CreateRecord",
      "entityName": "Users",
      "fields": {
        "FirstName": "{{triggerOutputs()?['name']}}",
        "Department": "IT"
      }
    },
    {
      "type": "SendEmail",
      "to": "hr@contoso.com",
      "subject": "New employee created",
      "body": "User {{triggerOutputs()?['name']}} has been created."
    }
  ]
}
```

Refer to the exhibit. You are analyzing a Power Automate flow definition. The flow is intended to create a new user record in Dataverse and send an email notification when manually triggered or daily at 8 AM. However, when the flow runs on its schedule, it fails because the trigger output 'name' is empty. What is the most likely cause?

⚠ Common exam trap

The PL-900 exam often tests the misconception that all triggers provide identical output schemas, leading candidates to overlook that scheduled triggers lack user-provided fields like 'name'.

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 schedule trigger does not provide a 'name' field in its outputs, causing the expression to fail.

A scheduled trigger in Power Automate does not include a 'name' field in its outputs, whereas a manual trigger (e.g., Power Apps or button) typically does. When the flow runs on its daily 8 AM schedule, the expression referencing trigger outputs 'name' evaluates to empty, causing the subsequent actions to fail. This is a common mismatch between trigger types and expected output schemas.

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 action 'CreateRecord' has an invalid entity name 'Users'.
Why it's wrong here
An invalid entity name would fail the CreateRecord action, not leave the trigger's 'name' output empty. It is tempting because Dataverse table naming errors are frequent, and would be correct if the flow reached CreateRecord and returned an entity-not-found error.
✓
The schedule trigger does not provide a 'name' field in its outputs, causing the expression to fail.
Why this is correct
The Recurrence trigger emits only timestamp-based outputs such as start time, so no 'name' token exists at runtime. Referencing that dynamic content therefore resolves to empty on scheduled runs, while the manual trigger supplies it.
✗
The flow is configured to run only on manual trigger, ignoring the schedule.
Why it's wrong here
A manual-only configuration would mean the scheduled run never starts, yet the flow does run and fails with an empty 'name'. It is tempting because trigger misconfiguration is common, and would be correct if no scheduled runs appeared in the run history at all.
✗
The flow does not have permission to create records in Dataverse.
Why it's wrong here
Permissions would block record creation entirely, yet the failure is an empty trigger output 'name', which occurs before any Dataverse write. It is tempting because authorisation errors are common in flows, and would be correct if the run failed with an access-denied error at the CreateRecord step.

Go deeper

PL-900 Practice Question: Describe the business value of Microsoft Power Platform

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question