Describe the business value of Microsoft Power Platform →mediumMultiple Choice

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

Exhibit

Refer to the exhibit.

{
  "triggers": {
    "When_a_new_email_arrives": {
      "type": "ApiConnection",
      "inputs": {
        "host": {
          "connectionName": "shared_office365"
        },
        "operationId": "OnNewEmail",
        "parameters": {
          "folderPath": "Inbox",
          "importance": "Any",
          "includeAttachments": true
        }
      }
    }
  },
  "actions": {
    "Create_item": {
      "type": "ApiConnection",
      "inputs": {
        "host": {
          "connectionName": "shared_commondataserviceforapps"
        },
        "operationId": "CreateItem",
        "parameters": {
          "entityName": "Leads",
          "item/email": "@{triggerOutputs()?['body/from']}"
        }
      }
    }
  }
}

Refer to the exhibit. You see a Power Automate flow definition in JSON. What does this flow do?

⚠ Common exam trap

Test-takers frequently confuse the trigger and action direction: candidates often misread the flow as 'when a lead is created, send an email' (Option C) instead of correctly identifying that an email arrival triggers the creation of a lead.

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

✓

It creates a lead in Dataverse when a new email arrives in the inbox.

The flow trigger is 'When a new email arrives' (inbox trigger), and the action is 'Create a new lead' in Dataverse. This means the flow automatically creates a lead record in Dataverse whenever a new email arrives in the specified inbox, without requiring any manual intervention.

Answer analysis

Option-by-option breakdown

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

✗
It updates a lead record when an email is received.
Why it's wrong here
The flow's trigger is a SharePoint item-creation event, not an email-arrival event, so no mailbox connector fires and no lead update occurs on incoming mail. It tempts because Power Automate's Outlook "When a new email arrives" trigger with a Dataverse update action would indeed update a lead on receipt.
✗
It deletes emails after creating leads.
Why it's wrong here
The flow's trigger and actions determine its behaviour, and deleting emails after creating leads misreads the sequence and operations shown in the JSON. It is tempting because flows often combine Outlook and Dataverse steps, and it would be correct if the definition actually contained a delete-email action following lead creation.
✗
It sends an email when a new lead is created in Dataverse.
Why it's wrong here
The JSON defines a Dataverse trigger on the Lead table, but the action shown is an approval request, not an email send. Email delivery requires the Office 365 Outlook connector's Send an email action. This option is tempting because lead-creation triggers paired with notification actions are a common Power Automate pattern.
✓
It creates a lead in Dataverse when a new email arrives in the inbox.
Why this is correct
The JSON shows an email-arrival trigger in the inbox followed by a Dataverse create-record action targeting the lead table. This satisfies the exhibit's flow definition: each new email automatically generates a lead record, matching the described behaviour precisely.

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