Microsoft

PL-500 Free Practice Questions — Page 5

Question 51

You have an automation solution that uses a desktop flow. The flow reads data from a file that is stored on a UserA’s machine and writes the data to an application. You import the solution to an environment that is connected to UserB’s machine. UserB reports that the flow fails. An alert indicates that the path to a file does not exist. You confirm that the file present on the UserB’s desktop. You need to resolve the issue. What should UserB do?

A. Delete and recreate the file.
B. Use the Get Windows environment variable action to read the USERNAME environment variable and use the value in the path to the user's desktop.
C. Modify the action to retry if the process cannot find the file.
D. Change access rights for the file to allow read operations for the PAD process.
Show Answer
Correct Answer: B
Explanation:
The desktop flow was built with a hard-coded file path that includes UserA’s username (for example, C:\Users\UserA\Desktop). When imported and run on UserB’s machine, that path does not exist even though the file is on UserB’s desktop. The correct fix is to make the path dynamic by retrieving the current USERNAME (or user profile) via a Windows environment variable and constructing the desktop path accordingly. This ensures the flow works for any user and machine.

Question 52

You have an automation solution that uses a desktop flow. The flow reads data from a file that is stored on a UserA’s machine and writes the data to an application. You import the solution to an environment that is connected to UserB’s machine. UserB reports that the flow fails. An alert indicates that the path to a file does not exist. You confirm that the file present on the UserB’s desktop. You need to resolve the issue. What should UserB do?

A. Delete and recreate the file.
B. Change access rights for the file to allow read operations for the PAD process.
C. Change the location of the file to a specific path that is not dependent on the signed-in user.
D. Modify the action to retry if the process cannot find the file.
Show Answer
Correct Answer: C
Explanation:
The desktop flow was created using a file path that is user-specific (for example, a desktop path tied to UserA). When the solution is imported and run on UserB’s machine, that exact path does not exist, even though the file is on UserB’s desktop. To make the flow portable across users and machines, the file should be stored in a fixed, non–user-dependent location (such as a shared or absolute path).

Question 53

DRAG DROP - Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question. Background - Contoso Pharmaceuticals distributes specialty pharmaceuticals, ingredients, and raw materials throughout North America. The company has 33 offices and 12 warehouses across the US, Mexico, and Canada. As their customers’ needs grow in sophistication, Contoso wants to delight customers with breakthrough products, exceptional service, and on-time delivery of materials. They want to automate time consuming and manual processes that are prone to error. Contoso wants to consolidate and automate ordering and fulfillment processes. • The company has a fleet of 500 delivery trucks. The company has 150 drivers and uses third-party contractors to deliver goods. • The company has 400 warehouse workers and 30 finance clerks. • Contoso has 85 sales representatives and 50 customer service representatives. Sales representatives spend most of their time on the road visiting customers or prospects. • The IT department consists of four system administrators and six system analysts. Current environment - Overview - Contoso Pharmaceuticals has a custom enterprise resource management (ERP) system. It is difficult to integrate other applications and services with the system. Office staff manually key in purchase orders, customer orders, and invoices after they receive a scan or hard copy of an agreement. Applications - • The company uses a custom supplier management system named SMSApps that runs on each user’s workstation. The system is costly to run and maintain. SMSApp does not have an API. • Sales representatives manage customer requests by using Dynamics 365 Sales. • Contoso has Microsoft Power Platform development, user acceptance testing (UAT), and production environments. • Administrators create one Accounts Payable (AP) mailbox for each environment to support testing. • The use of a DLP policy and Desktop Flow development is specified as part of the automation requirements. Security - You assign all users one or more Microsoft Dataverse security roles. Business Process - 1. Sales representatives create quotes by using a Microsoft Word document template. The template allows representatives to include product, quantity, and cost estimation details that will be needed to fulfil an order. The representative converts quotes to a PDF file and emails the file to the customer for approval. 2. The sales representative alerts the finance team about the new order and emails the finance team a copy of the quote for processing. 3. The finance team prints the quote and manually creates a purchase order (PO) into SMSApp to request materials from a known and trusted vendor. 4. The SMSApp distributes the PO to stakeholders. The system sends a copy to a shared finance team mailbox. 5. Once a PO is fulfilled by a vendor, the system sends an email to the finance mailbox. The finance team releases an order to the warehouse. 6. Materials are shipped from the vendor to one of Contoso’s warehouses. Warehouse workers enter key information from the waybill into SMSApp. The materials are unloaded and racked in the warehouse until they are shipped to customers. 7. Upon checking for new daily orders in SMSApp, they see an open order is pending that is awaiting the newly received materials. 8. The Warehouse worker loads an order onto a truck for delivery and marks the order as complete in SMSApp. 9. Sales representatives provide fulfillment status and tracking information for orders. 10. A finance clerk prepares an invoice and sends the invoice to the customer by email. The clerk sends a copy of the email to the shared AP mailbox. 11. The AP team monitors the shared mailbox to confirm that the customer has paid the invoice. Requirements - Functional requirements - • Large volume orders must be processed before other orders. • Invoices must be cross-checked with received items against packing slip for shipments. • The finance team must be able to analyze patterns in transactional data to conduct fraud prevention activities. • You must automate the process of entering data about incoming orders into SMSApp. • The solution must follow the principle of least privilege. Purchase Order Quantity flow - • You must create an unmanaged solution to update purchase order details in SMSApp. The flow must use a manual trigger. • Members of Accounts Payable team will be testers for the solution. They must be able to access the Purchase Order Quantity flow. Flow for processing invoice data • You must create a flow to monitor the AP mailbox. When an invoice arrives as an attachment in the inbox, the flow must automatically process the invoice data by using a form processing model. The flow must cross-check the received items against the packing slip. • You must use different Accounts Payable email addresses for development, user acceptance testing (UAT), and production environments. • You must use an environment variable to represent the Accounts Payable mailbox for the environment in use. • You must be able to use the environment variable across multiple cloud flows, a custom connector, and a canvas app. Technical requirements - • Users must only be allowed to connect to and access systems that are required for the employee to perform required job tasks. • All automation flows must be either co-owned or shared between staff. • All employees must be able to access the new environment to build personal productivity automations. • You must distribute the workload for desktop flows to optimize productivity. • A DLP policy must be created and applied to the Development environment. Connectors required by the data entry automation flow must be added to the policy. Order fulfillment flow - You must automate the customer communication process by using an unattended desktop flow. The flow must check the fulfilment status of each active order in SMSApp. If an order is fulfilled, the flow must send the customer an email that includes tracking information for their order. Monitor flows - • All data extracted from Invoices should be stored in a custom Dataverse table. • You must assign users from the finance to the Finance business unit. You must add these users to a new security role named Finance. • Finance users must be prevented from creating or deleting invoice records. • All users must be able to view invoices. Issues - Invoice data - All users report that they can see and modify invoice data. New environment - • The IT department creates a new environment that includes Microsoft Dataverse. An employee reports operational issues in Power Platform Admin center. • A user switch to the new environment and creates a cloud flow named FlowA that triggers a desktop flow. The user reports that the cloud flow does not trigger the desktop flow to run. • A user attempts to create a Desktop flow in the default environment. A Dataverse error message displays. Data entry automation flow - An administrator runs a new desktop flow in the development environment to automate data entry into SMSApp. The flow automatically reverts to a suspended state. Order fulfillment flow - The warehouse team observers that the order fulfillment flow has stopped working. Orders are flowing into SMSApp but customers do not receive tracking emails. A system administrator is troubleshooting the flow on the target machine. You need to implement a solution to manage the priority of incoming orders. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Illustration for PL-500 question 53
Show Answer
Correct Answer: Edit the cloud flow and add conditional logic for the order volume. Modify the Run a flow built by Power Automate Desktop action. Set the priority value based on the volume of the order.
Explanation:
Order priority for desktop flows is controlled from the cloud flow that triggers them. First, the cloud flow must evaluate order volume. Then the Run a desktop flow action is configured to accept a priority parameter. Finally, the priority value is set dynamically so high‑volume orders are queued and processed before others.

Question 54

HOTSPOT - Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question. Background - Woodgrove Bank is a large, member-owned bank in the United States Woodgrove Bank provides financial products with low customer fees and direct customer service. Woodgrove Bank has 177 branches across the United States with 5.000 branch staff and supervisors serving over 750,000 members. The primary languages used by most members include English and Spanish when interacting with customer service representatives. The Woodgrove Bank headquarters is in California and has 450 office workers. The office workers include financial advisors, customer service representatives, finance clerks, and IT personnel. Current environment. Bank applications • An application named Banker Desktop. The branch employees use this desktop app to review business transactions and to perform core banking updates. • An application named Member Management System. This application is a custom customer relationship management (CRM) that integrates with other systems by using an API interface. • An application named Fraud Finder. This application is a mission-critical, fraud management application that runs on the employees' desktops. The bank has experienced challenges integrating the application with other systems and is expensive to support. • SharePoint Online provides an employee intranet as well as a member document management system that includes polices, contracts, statements, and financial planning documents. • Microsoft Excel is used to perform calculations and run macros. Branch employees may have multiple Microsoft Excel workbooks open on their desktop simultaneously. Current environment. Bank devices • All supervisors are provided with a mobile device that can be used to access company email and respond to approval requests. • All branch employees and supervisors are provided with a Windows workstation. Requirements. New member enrollment Woodgrove Bank requires new members to sign up online to start the onboarding process. The bank requires some manual steps to be performed during the onboarding process. First step: • Members complete an online Woodgrove Bank document and email the PDF attachment to the bank’s shared mailbox for processing. Second step: • Members are asked to provide secondary identification to their local branch, such as a utility bill, to validate their physical address. • Branch staff scan the secondary identification in English or Spanish using optical character recognition (OCR) technology. Third step: • A branch supervisor approves the members’ application from their mobile device. • Only supervisors are authorized to complete application approvals. Fourth step: • Data that is received from applications must be validated to ensure it adheres to the bank's naming standards. The bank has the following requirements for the members’ data: • New members must be enrolled by using the document automation solution. • Member data is subject to regulatory requirements and should not be used for non-business purposes. • A desktop workflow is required to retrieve member information from the Member Management System on-demand or by using a cloud flow. Requirements. Bank fees - The process for calculating bank fees include: • using a shared Excel fee workbook with an embedded macro, and • an attended desktop flow that is required to automate the fee workbook process. The flow should open an Excel workbook and calculate the members' fees based on the number of products. Requirements. Fraud detection - The bank has the following requirements to minimize fraud: • Branch employees must use the Fraud Finder application during onboarding to validate a member’s identity with other third-party systems. • Branch employees must be able to search for a member in the Fraud Finder application by using a member's full name or physical address. • If fraudulent activity is identified, a notification with member details must be sent to the internal fraud investigation team. Requirements. Technical - The bank has the following technical requirements: Flows - • The Fraud Finder application uses a custom connector with Power Automate to run fraud checks. • The application approval process triggers a cloud flow, then starts an attended desktop flow on the branch employee s workstation and completes the approval. • The banker desktop flow runs using the default priority • An IT administrator is the co-owner of the banker desktop flow. • The IT department will be installing the required OCR language packs. • The Extract text with OCR action is used to import the members' secondary identification Member Management System - • A secure Azure function requires a subscription key to retrieve members’ information. • Production flows must connect to the Member Management System with a custom connector. The connector uses the Azure function to perform programmatic retrievals, creates, and updates. • The host URL has been added to the custom connector as a new pattern. • A tenant-level Microsoft Power Platform data loss prevention (DLP) policy has been created to manage the production environment. • A developer creates a desktop flow to automate data entry into a test instance of the Member Management System. • A developer creates an on-demand attended desktop flow to connect to a data validation site and retrieve the most current information for a member. Banker desktop application - • A banker desktop flow is required to update the core banking system with other systems. • When a transaction is complete, the branch employee submits the request by using a submit button. • After submitting the request, an instant cloud flow calls an unattended desktop flow to complete the core banking update. • The banker desktop flow must be prioritized for all future transactions. Deployment & testing - • Development data must be confined to the development environment until the data is ready for user acceptance testing (UAT). • The production environment in SharePoint Online must connect to the development instance of the Member Management System. • Developers must be able to deploy software every two weeks during a scheduled maintenance window. • The banker desktop flow must continue to run during any planned maintenance. • The fraud custom connector requires a policy operation named EscalateForFraud with a parameter that uses the members' full name in the request. Scalability - • The bank requires a machine group to distribute the automation workload and to optimize productivity. • The IT administrator needs to silently register 20 new machines to Power Automate and then add them to the machine group. Security - • The IT administrator uses a service principal account for machine connection. • The IT administrator has the Desktop Flow Machine Owner role. Issues - A branch staff member reports the document automation solution is not processing new members’ data and emails are not being sent for approvals. An IT administrator reports that the banker desktop flow has become unresponsive from data that is queued in another flow. Code - A Power Automate developer created the following script for the Member Management System desktop flow: You need to identify which automation technology to use for the application approval process. What should you use? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

Illustration for PL-500 question 54 Illustration for PL-500 question 54
Show Answer
Correct Answer: Instant flow Branch shared machine Authenticated and unlocked
Explanation:
The approval is initiated manually, so a button-triggered instant cloud flow is required. The cloud flow starts an attended desktop flow on a branch employee workstation, which is a shared branch machine. Attended desktop flows require a signed-in user with the session unlocked.

Question 55

You create an unattended Office 365 automation. The automation stops running. You suspect that the runtime identity used by the automation caused the automation to stop running. Which two issues can the runtime identity cause in this scenario? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.

A. The location of a specific user interface element has changed.
B. The automation is attempting to open files that cannot be opened or edited based on per-user access permissions.
C. The unattended automation process suppressed an alert that was generated.
D. The automation is not set up to handle an additional sign-in UI element.
Show Answer
Correct Answer: B, D
Explanation:
In unattended Office 365 automation, the runtime identity determines what resources and UI the automation can access. If the identity lacks proper per-user permissions, the automation may fail when opening or editing files (B). Additionally, unattended runs often encounter extra or different sign-in prompts; if the automation is not designed to handle an additional sign-in UI element, it can stop running (D).

Question 56

Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question. Background - Woodgrove Bank is a large, member-owned bank in the United States Woodgrove Bank provides financial products with low customer fees and direct customer service. Woodgrove Bank has 177 branches across the United States with 5.000 branch staff and supervisors serving over 750,000 members. The primary languages used by most members include English and Spanish when interacting with customer service representatives. The Woodgrove Bank headquarters is in California and has 450 office workers. The office workers include financial advisors, customer service representatives, finance clerks, and IT personnel. Current environment. Bank applications • An application named Banker Desktop. The branch employees use this desktop app to review business transactions and to perform core banking updates. • An application named Member Management System. This application is a custom customer relationship management (CRM) that integrates with other systems by using an API interface. • An application named Fraud Finder. This application is a mission-critical, fraud management application that runs on the employees' desktops. The bank has experienced challenges integrating the application with other systems and is expensive to support. • SharePoint Online provides an employee intranet as well as a member document management system that includes polices, contracts, statements, and financial planning documents. • Microsoft Excel is used to perform calculations and run macros. Branch employees may have multiple Microsoft Excel workbooks open on their desktop simultaneously. Current environment. Bank devices • All supervisors are provided with a mobile device that can be used to access company email and respond to approval requests. • All branch employees and supervisors are provided with a Windows workstation. Requirements. New member enrollment Woodgrove Bank requires new members to sign up online to start the onboarding process. The bank requires some manual steps to be performed during the onboarding process. First step: • Members complete an online Woodgrove Bank document and email the PDF attachment to the bank’s shared mailbox for processing. Second step: • Members are asked to provide secondary identification to their local branch, such as a utility bill, to validate their physical address. • Branch staff scan the secondary identification in English or Spanish using optical character recognition (OCR) technology. Third step: • A branch supervisor approves the members’ application from their mobile device. • Only supervisors are authorized to complete application approvals. Fourth step: • Data that is received from applications must be validated to ensure it adheres to the bank's naming standards. The bank has the following requirements for the members’ data: • New members must be enrolled by using the document automation solution. • Member data is subject to regulatory requirements and should not be used for non-business purposes. • A desktop workflow is required to retrieve member information from the Member Management System on-demand or by using a cloud flow. Requirements. Bank fees - The process for calculating bank fees include: • using a shared Excel fee workbook with an embedded macro, and • an attended desktop flow that is required to automate the fee workbook process. The flow should open an Excel workbook and calculate the members' fees based on the number of products. Requirements. Fraud detection - The bank has the following requirements to minimize fraud: • Branch employees must use the Fraud Finder application during onboarding to validate a member’s identity with other third-party systems. • Branch employees must be able to search for a member in the Fraud Finder application by using a member's full name or physical address. • If fraudulent activity is identified, a notification with member details must be sent to the internal fraud investigation team. Requirements. Technical - The bank has the following technical requirements: Flows - • The Fraud Finder application uses a custom connector with Power Automate to run fraud checks. • The application approval process triggers a cloud flow, then starts an attended desktop flow on the branch employee s workstation and completes the approval. • The banker desktop flow runs using the default priority • An IT administrator is the co-owner of the banker desktop flow. • The IT department will be installing the required OCR language packs. • The Extract text with OCR action is used to import the members' secondary identification Member Management System - • A secure Azure function requires a subscription key to retrieve members’ information. • Production flows must connect to the Member Management System with a custom connector. The connector uses the Azure function to perform programmatic retrievals, creates, and updates. • The host URL has been added to the custom connector as a new pattern. • A tenant-level Microsoft Power Platform data loss prevention (DLP) policy has been created to manage the production environment. • A developer creates a desktop flow to automate data entry into a test instance of the Member Management System. • A developer creates an on-demand attended desktop flow to connect to a data validation site and retrieve the most current information for a member. Banker desktop application - • A banker desktop flow is required to update the core banking system with other systems. • When a transaction is complete, the branch employee submits the request by using a submit button. • After submitting the request, an instant cloud flow calls an unattended desktop flow to complete the core banking update. • The banker desktop flow must be prioritized for all future transactions. Deployment & testing - • Development data must be confined to the development environment until the data is ready for user acceptance testing (UAT). • The production environment in SharePoint Online must connect to the development instance of the Member Management System. • Developers must be able to deploy software every two weeks during a scheduled maintenance window. • The banker desktop flow must continue to run during any planned maintenance. • The fraud custom connector requires a policy operation named EscalateForFraud with a parameter that uses the members' full name in the request. Scalability - • The bank requires a machine group to distribute the automation workload and to optimize productivity. • The IT administrator needs to silently register 20 new machines to Power Automate and then add them to the machine group. Security - • The IT administrator uses a service principal account for machine connection. • The IT administrator has the Desktop Flow Machine Owner role. Issues - A branch staff member reports the document automation solution is not processing new members’ data and emails are not being sent for approvals. An IT administrator reports that the banker desktop flow has become unresponsive from data that is queued in another flow. Code - A Power Automate developer created the following script for the Member Management System desktop flow: You need to resolve the banker desktop flow issue. Which two actions should you do? Each correct answer presents a complete solution. NOTE: Each correct selection is worth one point.

A. Perform a process mining trace on the flow.
B. Cancel the parent flow run.
C. Use the Move to top action.
D. Change the connector priority to high.
Show Answer
Correct Answer: C, D
Explanation:
The banker desktop flow is unresponsive because runs are being blocked by queued work from another flow. Using the **Move to top** action reprioritizes the banker desktop flow run in the desktop flow queue so it executes ahead of other queued runs. Changing the connector (desktop flow) priority to **High** ensures the banker desktop flow is prioritized for execution, as required for all future transactions. Together, these actions directly address queue contention and execution priority.

Question 57

DRAG DROP - A company plans to use Microsoft Power Platform. The company requires multiple test environments for users. The company wants to ensure that the Microsoft Power Platform environments are appropriate for the following cases: • UserA wants to test Microsoft Power Platform features for a limited time. • UserB wants to test solutions. You need to select the environment type for each use case. Which environment types should you select? To answer, drag the appropriate environment type to the correct scenarios. Each environment type may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point.

Illustration for PL-500 question 57
Show Answer
Correct Answer: Test features for a limited time: Trial (standard) Test solutions: Sandbox
Explanation:
Trial (standard) environments are time-limited and intended for exploring and evaluating Power Platform features. Sandbox environments are designed for development and testing of solutions without affecting production.

Question 58

HOTSPOT - Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question. Background - City Power and Light is one of the biggest energy companies in North America. They extract, produce and transport oil. The company has more than 50 offices and 100 oil extraction facilities throughout the United States, Canada, and Mexico. They use railways, trucks, and pipelines to move oil and gas from their facilities. The company provides the following services: • Produce oil from oil sands safely, responsibly, and reliably. • Refine crude oil into high-quality products. • Develop and manage wind power facilities. • Transport oil to different countries/regions. City Power and Light uses various Microsoft software products to manage its daily actives and run its machine-critical applications. Requirements - ManagePipelineMaintenanceTasks - A user named Admin1 creates a cloud flow named ManagePipelineMaintenanceTasks. Admin1 applies a data loss prevention (DLP) policy to the flow. Admin1 shares the flow with a user named PipelineManager1 as co-owner. You must determine the actions that PipelineManager1 can perform. You create a cloud MaintenanceScheduler flow that uses a desktop flow. The desktop flow connects to third-party services to fetch information. You must not permit the desktop flow to run for more than 20 minutes. You must configure sharing for MaintenanceScheduler to meet the following requirements: • User1 must be able to work with you to modify the desktop flow. • User2 must be able to access and review the run history for the cloud flow. • You must grant User3 permissions to run but not modify the desktop flow. ERPDataOperations flow - City Power and light uses an enterprise resource planning (ERP) system. The ERP system does not have an API. Each day the company receives an email that contains an attachment. The attachment lists orders from the company’s rail transportation partners. You must create an automation solution that reads the contents of the email and writes records to the ERP system. The solution must pass credential from a cloud flow to a desktop flow. RailStatusUpdater - City Power and Light actively monitors all products in transit. You must create a flow named RailStatusUpdater that manages communications with railways that transport the company’s products. RailStatusUpdater includes five desktop flow actions. You must run the desktop flows in attended mode during testing. You must run the desktop flows in unattended mode after you deploy the solution. You must minimize administrative efforts. Packaging - All flow automations must be created in a solution. All required components to support the flows must be included in the solution. Issues - ProductionMonitor flow - You create a cloud flow named ProductionMonitor which uses the Manually trigger a flow trigger. You plan to trigger ProductionMonitor from a cloud flow named ProdManager. You add a Run a Child flow action in ProdManager to trigger ProductionMonitor. When you attempt to save ProdManager the following error message displays: Request to XRM API failed with error: 'Message:Flow client error returned with status code "Bad request" and details "("error": {"code":ChildFlowUnsupportedForinvokerConnections", "message": The workflow with id 8d3bcde7-7e98-eb11-b1ac-000d3a32d53f", named FlowA cannot be used as a child workflow because child workflows only support embedded connections. "}}"Code" 0x80060467 InnerError.' CapacityPlanning flow - Developers within the company use cloud flows to access data from an on-premises capacity planning system. You observe significant increases to the volume of traffic that the on-premises data gateway processes each day. You must minimize gateway failures. DataCollector flow - You have a desktop flow that interacts with a web form. The flow must write data to several fields on the form. You are testing the flow. The flow fails when attempting to write data to any field on the web form. RailStatusUpdater flow - The RailStatusUpdater flow occasionally fails due to machine connection errors. You can usually get the desktop flow to complete by resubmitting the cloud flow run. You must automate the retry process to ensure that you do not need to manually resubmit the cloud flow when machine connection errors occur. You need to configure sharing for MaintenanceScheduler. Which sharing methods should you use? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point.

Illustration for PL-500 question 58
Show Answer
Correct Answer: User1: Share as co-owner User2: Share as co-owner User3: Share as user
Explanation:
User1 must modify the desktop flow, which requires co-owner permissions. User2 must review run history of the cloud flow, which also requires co-owner access. User3 must be able to run but not modify the desktop flow; for cloud flows that invoke desktop flows, this is achieved by sharing as user rather than run-only.

Question 59

You create a custom connector that retrieves data from an API. The host URL of the API requires a connection with a dynamic subdirectory path. You need to ensure the custom connector's requests are completed successfully. Which two features should you use? Each correct answer presents a part of the solution. NOTE: Each correct selection is worth one point.

A. Use references
B. Define a base URL
C. Define a policy
D. Use custom code
Show Answer
Correct Answer: B, C
Explanation:
When an API requires a dynamic subdirectory path, the custom connector must be structured to handle URL variability correctly. Defining a base URL establishes the fixed host portion of the API, while allowing dynamic path segments to be appended per operation. Defining a policy allows you to control or transform requests at runtime (for example, modifying paths or handling dynamic behavior) to ensure requests are constructed and executed successfully. References and custom code are not required for this scenario.

Question 60

DRAG DROP - Case study - This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided. To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study. At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section. To start the case study - To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. When you are ready to answer a question, click the Question button to return to the question. Background - Woodgrove Bank is a large, member-owned bank in the United States Woodgrove Bank provides financial products with low customer fees and direct customer service. Woodgrove Bank has 177 branches across the United States with 5.000 branch staff and supervisors serving over 750,000 members. The primary languages used by most members include English and Spanish when interacting with customer service representatives. The Woodgrove Bank headquarters is in California and has 450 office workers. The office workers include financial advisors, customer service representatives, finance clerks, and IT personnel. Current environment. Bank applications • An application named Banker Desktop. The branch employees use this desktop app to review business transactions and to perform core banking updates. • An application named Member Management System. This application is a custom customer relationship management (CRM) that integrates with other systems by using an API interface. • An application named Fraud Finder. This application is a mission-critical, fraud management application that runs on the employees' desktops. The bank has experienced challenges integrating the application with other systems and is expensive to support. • SharePoint Online provides an employee intranet as well as a member document management system that includes polices, contracts, statements, and financial planning documents. • Microsoft Excel is used to perform calculations and run macros. Branch employees may have multiple Microsoft Excel workbooks open on their desktop simultaneously. Current environment. Bank devices • All supervisors are provided with a mobile device that can be used to access company email and respond to approval requests. • All branch employees and supervisors are provided with a Windows workstation. Requirements. New member enrollment Woodgrove Bank requires new members to sign up online to start the onboarding process. The bank requires some manual steps to be performed during the onboarding process. First step: • Members complete an online Woodgrove Bank document and email the PDF attachment to the bank’s shared mailbox for processing. Second step: • Members are asked to provide secondary identification to their local branch, such as a utility bill, to validate their physical address. • Branch staff scan the secondary identification in English or Spanish using optical character recognition (OCR) technology. Third step: • A branch supervisor approves the members’ application from their mobile device. • Only supervisors are authorized to complete application approvals. Fourth step: • Data that is received from applications must be validated to ensure it adheres to the bank's naming standards. The bank has the following requirements for the members’ data: • New members must be enrolled by using the document automation solution. • Member data is subject to regulatory requirements and should not be used for non-business purposes. • A desktop workflow is required to retrieve member information from the Member Management System on-demand or by using a cloud flow. Requirements. Bank fees - The process for calculating bank fees include: • using a shared Excel fee workbook with an embedded macro, and • an attended desktop flow that is required to automate the fee workbook process. The flow should open an Excel workbook and calculate the members' fees based on the number of products. Requirements. Fraud detection - The bank has the following requirements to minimize fraud: • Branch employees must use the Fraud Finder application during onboarding to validate a member’s identity with other third-party systems. • Branch employees must be able to search for a member in the Fraud Finder application by using a member's full name or physical address. • If fraudulent activity is identified, a notification with member details must be sent to the internal fraud investigation team. Requirements. Technical - The bank has the following technical requirements: Flows - • The Fraud Finder application uses a custom connector with Power Automate to run fraud checks. • The application approval process triggers a cloud flow, then starts an attended desktop flow on the branch employee s workstation and completes the approval. • The banker desktop flow runs using the default priority • An IT administrator is the co-owner of the banker desktop flow. • The IT department will be installing the required OCR language packs. • The Extract text with OCR action is used to import the members' secondary identification Member Management System - • A secure Azure function requires a subscription key to retrieve members’ information. • Production flows must connect to the Member Management System with a custom connector. The connector uses the Azure function to perform programmatic retrievals, creates, and updates. • The host URL has been added to the custom connector as a new pattern. • A tenant-level Microsoft Power Platform data loss prevention (DLP) policy has been created to manage the production environment. • A developer creates a desktop flow to automate data entry into a test instance of the Member Management System. • A developer creates an on-demand attended desktop flow to connect to a data validation site and retrieve the most current information for a member. Banker desktop application - • A banker desktop flow is required to update the core banking system with other systems. • When a transaction is complete, the branch employee submits the request by using a submit button. • After submitting the request, an instant cloud flow calls an unattended desktop flow to complete the core banking update. • The banker desktop flow must be prioritized for all future transactions. Deployment & testing - • Development data must be confined to the development environment until the data is ready for user acceptance testing (UAT). • The production environment in SharePoint Online must connect to the development instance of the Member Management System. • Developers must be able to deploy software every two weeks during a scheduled maintenance window. • The banker desktop flow must continue to run during any planned maintenance. • The fraud custom connector requires a policy operation named EscalateForFraud with a parameter that uses the members' full name in the request. Scalability - • The bank requires a machine group to distribute the automation workload and to optimize productivity. • The IT administrator needs to silently register 20 new machines to Power Automate and then add them to the machine group. Security - • The IT administrator uses a service principal account for machine connection. • The IT administrator has the Desktop Flow Machine Owner role. Issues - A branch staff member reports the document automation solution is not processing new members’ data and emails are not being sent for approvals. An IT administrator reports that the banker desktop flow has become unresponsive from data that is queued in another flow. Code - A Power Automate developer created the following script for the Member Management System desktop flow: You need to add a policy to the Fraud custom connector. Which five actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

Illustration for PL-500 question 60 Illustration for PL-500 question 60
Show Answer
Correct Answer: Create a new policy template within the custom connector. Select the Set query string parameter template. Select the EscalateForFraud operation. Add an override query parameter for the full name. Update the connector.
Explanation:
To add a policy to an existing custom connector, you first create a policy template, then choose the appropriate parameter template. The policy is scoped to the EscalateForFraud operation, configured to override the required full name query parameter, and finally the connector must be updated to apply the changes.

$19

Get all 157 questions with detailed answers and explanations

  • Instant download HTML + PDF delivered the moment payment clears.
  • Secure Stripe checkout we never see or store your card details.
  • 7-day refund if files are defective see our refund policy.