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

Question 1

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?

10 minute time limit — choose an answer to begin.

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'. 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 2

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

Accepted Answer

Configure run after. Configure run after (A) is correct because it allows an action to run based on the success, failure, or timeout of a previous action. Scope (B) is correct because it groups actions and can be used with 'Configure run after' to implement error handling patterns. Retry policy (D) is correct because it automatically retries an action upon failure, defining the number of retries and interval. Parallel branches (C) is not an error-handling feature; it runs actions concurrently. Try-catch-finally pattern using scopes (E) is a user-designed pattern, not a built-in error-handling option in Power Automate.

Answer

Parallel branches

Answer

Try-catch-finally pattern using scopes

Question 3

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 4

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.. 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.

Question 5

Which TWO scenarios are suitable for using a scheduled cloud flow in Power Automate?

Accepted Answer

Backing up a database to a cloud storage every night at midnight. Option B is correct because backing up a database every night at midnight is a recurring, time-based task that fits a scheduled cloud flow, which uses a Recurrence trigger with a daily schedule at 12:00 AM. Option E is correct because generating a daily report every morning at 8 AM is also a time-driven, recurring operation, matching a scheduled flow with a Recurrence trigger set to daily at 8:00 AM. Options A, C, and D are not suitable because they are event-driven scenarios: A requires a OneDrive 'When a file is created' trigger, C requires a SharePoint/Dataverse 'When an item is created' trigger for the expense report, and D requires an immediate event trigger such as a new user sign-up, none of which are scheduled.

Answer

Creating a file in SharePoint whenever a new file is uploaded to a OneDrive folder

Answer

Sending an approval request to a manager when a new expense report is submitted

Answer

Sending a welcome email to a new user immediately after they sign up

Question 6

Refer to the exhibit. The flow fails to send the email. What is the most likely cause?

Accepted Answer

The email action does not include the list of opportunities in the body. The flow's email action is configured to send a static email body without including the dynamic content from the 'List rows' action. Even if the trigger and filter are correct, the email will not contain the list of opportunities, so the flow appears to fail in its purpose. Power Automate requires explicit insertion of dynamic content (e.g., the 'value' array from Dataverse) into the email body to transmit the data.

Answer

The filter condition 'statecode eq 0' is invalid

Answer

The recurrence trigger is incorrectly configured

Answer

The connections to Dataverse and Office 365 are not established

Question 7

Match each Power Apps license type to its description.

Accepted Answer

Power Apps per user plan: A user can run unlimited custom apps and access premium connectors.. Correct matches: Per user plan gives unlimited app access and premium connectors; per app plan is for a single app; Office 365 plan offers limited standard connector usage. Common confusions involve swapping the per user and per app definitions or overstating the Office 365 capabilities.

Answer

Power Apps per user plan: A user can run only one specific app.

Answer

Power Apps for Office 365: A user can run unlimited custom apps with premium connectors.

Question 8

Your organization uses Power Automate to automate approval workflows in SharePoint. When a user creates a new item in a SharePoint list, an approval request should be sent to their manager. However, some approvals are not being triggered. What is the most likely cause?

Accepted Answer

The trigger is set to 'When an item is created or modified' and the item is being created and then modified immediately.. The SharePoint trigger 'When an item is created' must be set to trigger only on new items, not on changes. A common misconfiguration is setting the trigger to 'When an item is created or modified', which can cause missed triggers if the item is created and then quickly modified. Option A is incorrect because SharePoint triggers do not require a premium license for basic actions. Option C is incorrect because permissions to the list do not affect the trigger's ability to fire. Option D is incorrect because the delay is unrelated to the trigger configuration.

Answer

The flow requires a premium Power Automate license.

Answer

The user does not have permission to view the SharePoint list.

Answer

The flow has a 'Delay' action before the approval step.

Question 9

A company wants to automate sending a welcome email to new users added to Microsoft Entra ID. Which Power Automate trigger should they use?

Accepted Answer

When a new user is created (Office 365 Users). The 'When a new user is created (Office 365 Users)' trigger in Power Automate fires when a new user account is created in Microsoft Entra ID (formerly Azure AD). This is the correct trigger to automate sending a welcome email to new users. The Office 365 Users connector provides this trigger specifically for user creation events.

Answer

When a user is deleted (Microsoft Entra ID)

Answer

When a user is added to a group

Answer

When a user is modified (Microsoft Entra ID)

Question 10

Refer to the exhibit. You have a Power Automate flow that sends an approval email and then checks if the email was sent successfully. If successful, it updates a SharePoint item status to 'Approved'. Otherwise, it sends a rejection email. However, the flow always updates the SharePoint item to 'Approved' even when the approval email fails. What is the likely issue?

Accepted Answer

The flow uses 'Send an email' instead of a proper approval action.. The flow uses the 'Send an email' action, which only sends an email message; it does not implement an approval process. The 'Succeeded' status indicates the email was sent, not that the recipient approved. To create an approval, you must use the 'Start and wait for an approval' action, which pauses the flow until the recipient responds. Options A, B, and D are incorrect because they do not address the core issue: the lack of a proper approval action.

Answer

The 'email/To' parameter is missing the recipient's email.

Answer

The condition expression is incorrectly formatted.

Answer

The 'body' function should be 'outputs' instead.