Describe the business value of Microsoft Power Platform →hardMultiple Choice

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

Exhibit

{
  "triggers": [
    {
      "type": "Schedule",
      "recurrence": {
        "frequency": "Hour",
        "interval": 1
      }
    }
  ],
  "actions": [
    {
      "type": "ApiConnection",
      "inputs": {
        "host": {
          "apiId": "/providers/Microsoft.PowerApps/apis/shared_commondataservice"
        },
        "parameters": {
          "tableName": "accounts",
          "filterQuery": "createdon ge @{addHours(utcNow(), -1)}"
        }
      }
    }
  ]
}

Refer to the exhibit. A Power Automate flow runs hourly to retrieve new accounts from Dataverse. However, it sometimes misses records created at the exact hour boundary. What is the most likely reason?

⚠ Common exam trap

Test-takers frequently assume utcNow() is the cause of the issue, but the real problem is the fundamental difference between scheduled polling and event-driven triggers in Power Automate.

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 runs on a schedule, not triggered by record creation, so it may miss records created between runs.

The flow is configured to run on a recurring schedule (e.g., every hour), not as an instant trigger on record creation. When a record is created at the exact boundary between two scheduled runs, it may not be captured by the previous run (which already completed) and may not yet exist when the next run begins, especially if the flow uses a filter query based on a timestamp. This is a classic limitation of scheduled polling compared to event-driven triggers like 'When a row is added, modified, or deleted' in Dataverse.

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 flow runs on a schedule, not triggered by record creation, so it may miss records created between runs.
Why this is correct
A recurring schedule trigger only queries at fixed intervals, so records created between executions are absent until the next run. This explains the missed hour-boundary records, unlike an event-driven Dataverse trigger that fires on creation.
✗
The accounts table has a security filter that hides records from the flow owner.
Why it's wrong here
A security filter hiding records would omit them consistently, not only those created at the exact hour boundary. It is tempting because row-level security genuinely causes missing records, and would be correct if the flow owner lacked read privileges on a subset of the accounts table.
✗
The API connection to Dataverse is not authenticated properly.
Why it's wrong here
Authentication failures would block the flow entirely or throw errors, not selectively miss records created at the hour boundary. It is tempting because broken connections commonly cause missing data, and would be correct if the flow failed consistently with authorisation errors logged against the Dataverse connector.
✗
The filter query uses utcNow() which may not be precise across time zones.
Why it's wrong here
utcNow() returns a single UTC timestamp unaffected by time zones, so it cannot cause boundary records to be skipped. It is tempting because time-zone confusion genuinely breaks date filters, and would be correct if the flow compared local-time values against UTC-stored Dataverse fields.

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