EnglishDeutschFrançaisEspañolPortuguês

Retired

Microsoft · PL-500 · Associate

Microsoft Power Automate RPA Developer

The PL-500 certification validates skills in designing, developing, and deploying robotic process automation (RPA) solutions using Microsoft Power Automate.

This exam has been retired.

50Mock exam questions
100minTime limit
700/ 1000Passing score

Overview

About the exam

The PL-500 certification validates skills in designing, developing, and deploying robotic process automation (RPA) solutions using Microsoft Power Automate. It covers desktop flow creation with Power Automate for desktop, cloud flow integration, process mining, AI Builder integration, exception handling, and managing automation solutions across development and production environments.

This certification is designed for RPA developers and automation engineers who build attended and unattended desktop flows to automate repetitive business processes. Candidates should have experience with Power Automate cloud and desktop flows, process analysis, and implementing automation solutions that integrate legacy desktop applications with cloud services.

Try the practice preview

Try five PL-500 questions

Try five practice questions from the app’s current Microsoft Power Automate RPA Developer question bank, with answers and explanations.

Deploy and manage automations1 / 5

A company is implementing hosted machine groups for unattended desktop flow automation. They have 10 Hosted Process licenses assigned to the environment and three hosted machine groups configured. During peak hours, all three groups need to run simultaneously. What feature ensures efficient resource utilization?

AlexFull explanation from Alex

Per Microsoft docs, hosted machine groups automatically provision Azure-hosted bots and distribute desktop flow runs using automatic load balancing based on real-time queue depth. This ensures efficient utilization when multiple groups share Hosted Process licenses. Manual machine assignment contradicts the automated nature — admins set max/committed bots but don't manually assign machines. Round-robin scheduling is wrong because distribution is demand-based, not fixed rotation. Static allocation is incorrect because hosted groups dynamically scale based on demand, not through pre-assigned mappings. The key benefit is elastic scaling without infrastructure management.

Sourcelearn.microsoft.com

Develop automations2 / 5

You need to add conditional logic in a Power Automate desktop flow that executes different actions based on the value of a variable. The variable can have five possible values. Which flow control action is most appropriate?

AlexFull explanation from Alex

Per Microsoft docs, the Switch action in Power Automate for desktop "dispatches execution to different parts of the switch body based on the value of the expression." It is designed for branching on a single variable across multiple values. A While loop is for repeated execution while a condition is true, not branching. A For each loop iterates over collections, unrelated to conditional logic. An If/Else If chain can work but becomes unwieldy with five cases, reducing readability. Microsoft docs explicitly state: "Use Switch conditionals to compare a single variable with multiple possible values." Switch provides cleaner multi-case logic with a default handler for unmatched values.

Sourcelearn.microsoft.com

Design automations3 / 5

A developer is configuring Power Automate to use process mining to analyze a business process before automating it. What is the primary purpose of process mining in the context of RPA design?

AlexFull explanation from Alex

Per Microsoft docs, process mining "helps businesses understand their real processes, how they're operated, and identify opportunities for improvement, automation, and digitalization." It extracts event data from systems of record to visualize actual process execution paths. Validating custom connectors uses different tools in the connector wizard. Generating desktop flows automatically describes task recording, not process mining — process mining analyzes but doesn't auto-generate code. Monitoring deployed bots describes the Power Automate monitoring dashboard. Process mining is specifically a pre-automation analysis tool that reveals bottlenecks, variations, and inefficiencies before development begins.

Sourcelearn.microsoft.com

Develop automations4 / 5

A developer is designing an automation for a legacy Windows application. The application has a multi-step wizard with Next, Back, and Finish buttons. The developer needs to ensure the flow handles cases where a wizard step takes longer than usual to load. Which design pattern is most resilient?

AlexFull explanation from Alex

Per Microsoft docs, "Wait for UI element" actions dynamically detect when page elements appear before proceeding, adapting to real-time loading conditions. This is the most resilient pattern for multi-step wizards. A single timeout at the beginning cannot handle variable step-by-step loading. Fixed 30-second delays waste time on fast loads and fail on slow ones — they don't adapt. Image-based recognition is brittle, breaking with resolution changes, theme updates, or minor UI variations. Microsoft troubleshooting docs explicitly recommend adding "Wait for window content" or "Wait for UI element" actions when elements aren't available at execution time, confirming this as the documented best practice.

Sourcelearn.microsoft.com

Deploy and manage automations5 / 5

A DLP policy classifies the Database action group as Business and the Excel action group as Non-business for desktop flows. A developer attempts to save a desktop flow that reads from a SQL database and writes results to an Excel spreadsheet. What happens?

AlexFull explanation from Alex

Per Microsoft docs, DLP policies classify desktop flow action groups as Business, Non-business, or Blocked. When a flow uses actions from both Business (Database) and Non-business (Excel) categories, it violates the policy. Current Power Automate for desktop versions prevent saving, debugging, or running violating flows. Only disabling Excel actions is wrong — DLP enforces at the flow level, not individual actions. DLP only applying to cloud flows is incorrect — Microsoft explicitly extends DLP to desktop flows. Saving but suspending describes legacy behavior from older versions where background enforcement suspended flows within 24 hours; current versions block at save time with a notification.

Sourcelearn.microsoft.com

Exam domains

What's on the exam

Exam blueprint: PL-500

Design automations28%

Design automations using Power Automate features, other Microsoft Power Platform capabilities, data/document analysis, and scripting languages

Develop automations47%

Develop cloud flows, desktop flows, implement logic, build custom connectors, perform automation infrastructure management, and test automations

Deploy and manage automations25%

Prepare target environments, assess DLP policies, implement access to RPA components, and implement machine groups and queues

Format

Exam format and question types

The exam consists of 40–60 questions to be completed in approximately 100 minutes (100 minutes if labs are included). Question types include multiple-choice, multiple-select, drag-and-drop, and hot area formats. Questions are scenario-based, testing your ability to design desktop flow automation, handle exceptions, and integrate desktop flows with cloud flows. Expect questions about process mining, machine configuration, and attended vs unattended runs.

Question types: PL-500

Multiple Choice36%

Select the single answer that best meets the question’s requirements.

Drag & Drop13%

Move items into the slots, groups, or sequence specified by the task.

Troubleshooting13%

Use the symptoms and constraints in a scenario to identify a cause or choose a fix.

Multiple Response11%

Select multiple answers. Follow the question’s instructions on how many to choose.

Dropdown11%

Choose options from dropdown menus to complete a statement or configuration.

Ordering9%

Arrange the steps in the sequence needed to complete the process.

True / False7%

Decide whether a statement is true or false, paying attention to its conditions and wording.

Study notes

Common pitfalls

Topics to review: PL-500

  1. 01Desktop Flow Actions

    Not understanding UI automation actions, web automation, Excel actions, and variable manipulation in Power Automate for desktop.

  2. 02Machine Configuration

    Struggling with machine registration, machine groups, and gateway setup for running unattended desktop flows at scale.

  3. 03Exception Handling

    Overlooking error handling patterns, retry policies, and compensation logic in desktop and cloud flow automation.

  4. 04Process Mining

    Confusing process mining capabilities and how to use process advisor to analyze and optimize business processes before automation.

  5. 05Solution Architecture

    Not designing proper ALM strategies for managing RPA solutions across development, test, and production environments.

Practice with questions and explanations in Pass-IT →

Questions

Frequently asked questions

How long is the Microsoft Power Automate RPA Developer exam?

The PL-500 exam has 50 questions and a 100-minute time limit.

What is the passing score for Microsoft Power Automate RPA Developer?

The passing score for the PL-500 exam is 700 / 1000.

Which pitfalls should I review when preparing for Microsoft Power Automate RPA Developer?

Topics to review include Desktop Flow Actions, Machine Configuration, Exception Handling, Process Mining, Solution Architecture. Work through examples to check that you understand the distinctions and can explain your answer.