PL-900 Demonstrate the capabilities of Power Automate — Timed 10 Questions

Question 1

A company wants to automate sending a welcome email to new employees after they are added to a SharePoint list. Which type of trigger should be used in the Power Automate flow?

Accepted Answer

When an item is created - SharePoint. The 'When an item is created - SharePoint' trigger is the correct choice because it initiates the flow automatically whenever a new item (in this case, a new employee record) is added to the specified SharePoint list. This event-driven trigger eliminates the need for manual intervention, making it ideal for automating the welcome email process immediately upon creation.

Answer

For a selected item - SharePoint

Answer

Recurrence

Answer

Start and wait for an approval

Question 2

You have a Power Automate flow that sends an email notification when a new file is added to a SharePoint document library. Users report that emails are not being sent for some files. What is the most likely cause?

Accepted Answer

A trigger condition is filtering out some files. Option C is correct because trigger conditions in Power Automate allow you to define expressions that must evaluate to true for the flow to run. If a condition is configured to filter out certain files (e.g., based on file name, metadata, or size), those files will not trigger the flow, and no email will be sent. This is the most likely cause when emails are missing for some files but not all.

Answer

The flow uses a premium connector that requires a license

Answer

The file is being co-authored by multiple users

Answer

The file content contains sensitive information

Question 3

You are designing a Power Automate flow to approve expense reports. The flow must allow managers to approve or reject directly from the email notification without signing in. Which action should you use?

Accepted Answer

Start and wait for an approval. The 'Start and wait for an approval' action is specifically designed to send an approval request via email or the Power Automate mobile app, and it allows recipients to approve or reject directly from the email notification without needing to sign in, using adaptive cards or lightweight approval buttons. This meets the requirement for manager approval without authentication.

Answer

Create a file

Answer

Send an email (V2)

Answer

Send an HTTP request

Question 4

A flow fails with the error: 'GatewayTimeout'. The flow connects to an on-premises SQL Server via a data gateway. What is the most likely cause?

Accepted Answer

The on-premises data gateway is not running or unreachable. The 'GatewayTimeout' error indicates that the flow successfully reached the on-premises data gateway but the gateway did not respond within the expected time frame. This typically occurs when the gateway service is not running, the machine hosting the gateway is offline, or network connectivity between the gateway and the SQL Server is broken. Incorrect credentials or missing tables would produce different errors (e.g., 'Login failed' or 'Invalid object name').

Answer

The SQL login credentials are incorrect

Answer

The SQL table does not exist

Answer

The flow trigger did not fire

Question 5

You need to design a Power Automate flow that processes orders from a CSV file in SharePoint. The flow should read each row and create a record in a SQL database. If a row contains invalid data, the flow should continue with the next row. Which configuration should you use?

Accepted Answer

Use an apply to each loop and configure 'Configure run after' for the SQL insert action to include 'is successful', 'has timed out', 'is skipped', 'has failed'. Option C is correct because configuring 'Configure run after' for the SQL insert action to include 'is successful', 'has timed out', 'is skipped', and 'has failed' ensures that even if a row fails validation or the SQL insert fails, the flow continues to the next iteration of the Apply to each loop. This allows the flow to process all rows in the CSV file without stopping on an error, meeting the requirement to skip invalid data and proceed with the next row.

Answer

Use parallel branches for each row

Answer

Use an apply to each loop with default settings

Answer

Use a scope with sequential actions and set 'Configure run after' to 'is successful' only

Question 6

Which TWO components are required to create a Power Automate flow that sends an email when a new item is added to a SharePoint list? (Choose two.)

Accepted Answer

A trigger. A trigger is required because a Power Automate flow must have a starting event to initiate execution. For a SharePoint list, the 'When an item is created' trigger fires automatically when a new item is added, which is the necessary first step before any actions can run.

Answer

An approval action

Answer

A variable

Answer

A condition

Question 7

Which THREE are valid options for handling errors in a Power Automate flow? (Choose three.)

Accepted Answer

Configure run after. Option A is correct because 'Configure run after' allows a flow action to execute based on the outcome (success, failure, skipped, or timed out) of a preceding action. This is the primary mechanism in Power Automate for handling errors by defining conditional execution paths after an action completes.

Answer

Parallel branches

Answer

Retry policy

Question 8

A Power Automate flow uses the trigger configuration shown. Users report that the flow does not start when a new order is added with Status = 'Pending'. What is the most likely cause?

Accepted Answer

The trigger condition only allows items with Status = 'New'. Option D is correct because the trigger condition explicitly filters for items where Status equals 'New'. When a new order is added with Status = 'Pending', the condition evaluates to false, so the flow does not trigger. Trigger conditions in Power Automate act as a pre-filter on the trigger event, preventing the flow from running if the condition is not met.

Answer

The SharePoint dataset URL is incorrect

Answer

The flow is paused or turned off

Answer

The trigger only fires on modification, not creation

Question 9

You review a failed flow run with the log shown. The flow is supposed to send an email when a SharePoint item is created. What is the most likely issue?

Accepted Answer

The email connector is not properly configured or the SMTP server is down. The flow log shows a failure in the 'Send an email' action, not the trigger. Since the trigger (SharePoint 'When an item is created') successfully initiated the flow, the issue lies with the email connector. The most likely cause is that the email connector (e.g., Office 365 Outlook, SMTP) is misconfigured—such as incorrect SMTP server, port, authentication, or the SMTP server being unreachable—preventing the email from being sent.

Answer

The SharePoint trigger did not fire

Answer

The scope 'SendNotification' failed due to a missing variable

Answer

The SharePoint list permissions are incorrect

Question 10

You are a Power Platform administrator for a large enterprise. You have created a Power Automate cloud flow that sends an approval email to the manager whenever a new employee is added to the HR system. The flow uses a SharePoint list as the trigger and a Common Data Service (CDS) connector to update the employee record. Recently, the flow has been failing intermittently with the error: 'The request failed due to a network error. The server returned an error: GatewayTimeout'. You check the flow run history and see that the error occurs on the CDS update action. The SharePoint trigger and approval actions complete successfully. The flow runs with a concurrency setting of 10. The CDS environment is in another region. You need to resolve the timeout issue. What should you do?

Accepted Answer

Increase the timeout setting for the CDS update action in the flow.. Option A is correct because the GatewayTimeout error indicates that the CDS update action is taking longer than the default timeout (typically 2 minutes) to complete, especially given the cross-region latency. Increasing the timeout setting for the CDS action allows the flow to wait longer for the response, resolving the intermittent failure without altering the flow's logic or concurrency.

Answer

Split the flow into two: one for the SharePoint trigger and one for the CDS update, and trigger the second via HTTP request.

Answer

Restart the CDS environment to clear any temporary issues.

Answer

Reduce the concurrency setting to 1 to prevent multiple simultaneous requests.