Free PL-500 Exam Braindumps

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

MaintenanceScheduler
You create a cloud 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 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
You must package the automations in a solution. All required components 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:



CapacityPlanning flow
Developers within the company use could 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.

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.

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.

Monitor flows
-All data extracted from Invoices should be stored in a custom Dataverse entity. Only employees who are part of Finance role should be able to edit all Invoice data but must be prevented from creating or deleting one.

Issues

Invoice data
All users report that they can see and modify invoice data.

New environment
-The IT department creates a new environment. A user creates a cloud flow named FlowA in the environment that triggers a desktop flow. A user reports that the cloud flow does not trigger the desktop flow to run.
-Microsoft Dataverse is not provisioned in the new environment. You attempt to create a Desktop flow in the default environment but receive a Dataverse error message and cannot proceed.

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

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:

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
First Up Consultants is a professional services organization headquartered in Europe, with offices in North America. The company supports small- to medium-sized and enterprise organizations with a range of information technology, project management, change management, and finance management consultancy needs. The organization employs 500 full-time consultants and engages with over 1,000 external contractors to support the delivery of its various projects.

Current environment
The company has been using Microsoft Power Platform for several years and currently has the following implemented:

-A model-driven app named Project Planning Application that is used by the project management office (PMO) team within the company to plan, schedule and collate information for each client project. The application supports the following functionality areas:
oStorage for project-level information, such as start date, end date and client data.
oA series of inputs to capture detailed information for statements of work as part of a standard document format. This information is manually entered by the PMO team.
oInformation regarding internal and external consultants is stored within a custom table called Resources.
oInformation within the Resources table regarding full-time consultants is typically populated manually by the PMO team. For external consultants, the company regularly attends industry events and collates business cards for potential new employees or external contractors. Information regarding these individuals is then manually entered into the application. The PMO team then asks suitable candidates to complete an application form in Microsoft Word standard format and upload it via a secure URL. Again, the PMO team then manually enters the data into Project Planning Application.

•A canvas app named Time Entry Application is used by the employees and external contractors to capture the time worked on projects. The application has been configured with the following defined controls:

odpStartDate: A date picker control to indicate the start date of the time entry.
odpEndDate: A date picker control to indicate the end date of the time entry.
oinptDescription: A control used to indicate the type of activity and project worked on.
•A mobile app stores the current user's email address as part of a variable called varUserName.

The company uses Microsoft SharePoint on premises to store all sensitive documents. Company policy mandates that all client-related documents are stored within this environment only.

The company uses SAP as its back-end accounting system. The company maintains separate SAP systems in each legal jurisdiction where it is based. The system is relied upon for the following critical business processes:
•External contractors working on a project send their invoices to a dedicated mailbox that is monitored by the company's accounting team. The accounting team must then manually process these invoices into SAP at the end of each month. Due to the number of external contractors, hundreds of invoices must be processes monthly.
•Basic API access for the SAP system is provided via a mixture of native application APIs and a middleware Simple Object Access Protocol (SOAP) API hosted on premises. The middleware API supports the ability to post time entries against the relevant projects in any SAP system by specifying the system and client ID as a query parameter in the URL. The middleware API was developed several years ago, and the source code is no longer available. Data is returned in XML format, which can then be analyzed further.
•When a project enters the closure phase, members of the PMO team need to navigate to SAP, enter some details, and then capture information from a PDF that is generated and opened on the screen, such as the final settlement amount. This information is then manually entered into Project Planning Application.

The company maintains a separate system containing detailed profile information regarding internal employees. The PMO team currently manually enters information from this system into the Resources table. Developers in the company have created a modern REST API for this system, which is actively maintained. The system contains highly sensitive personal information (PI) regarding each employee.

The company has several on-premises Windows environments that it has identified as suitable for usage because they exist within the same physical network as SAP and the middleware API. These environments must be patched regularly, and all activities targeting these environments must be automated.

Project Planning Application
•Rather than manually populating the statement of work information, users should place it in a SharePoint folder for this information to be extracted and mapped to the correct inputs.
•A new automation is required to integrate with the profile information system. Because the company plans to consume this data in several ways, a streamlined mechanism for working with the API is required to improve reusability.
•An automation is required to handle the project closure steps in SAP and to store the relevant information from SAP into the app.
•Once a new candidate uploads a completed application form, information from the form should be copied automatically into Project Planning Application.


Time Entry Application
•Time Entry Application needs to be extended to integrate alongside SAP, ensuring postings for time entries are processed successfully. When a time entry is submitted, the entry should be posted automatically to SAP.
•Time entries must always be submitted with relevant text that indicates the type of activity and project worked on.
•The automation should be able to detect and handle any errors that occur when posting individual time entries.

Invoice Processing
•Invoices sent to the account’s mailbox must be processed automatically and created as invoices within SAP.

General
•Development efforts should be avoided or mitigated when there is native functionality already available.
•Reusability of components is desired to assist citizen developers in creating any solutions in future.
•All automation activities should run without disruption during an outage or a patching cycle.
•Use of username and password credentials should be avoided.
•Automations should not rely on human intervention to execute.
•Use of public cloud file services should be restricted.
•Where possible, JSON should be the preferred format when transferring data.

Issues
•Users within the PMO team report that it takes many hours to put the data from each business card into the system.
•You create the automation to process the time entries, called Submit Time Entry, and add it to the application. Users report issues with the formula used to connect to the automation.
•During a monthly patch cycle, IT support team members cannot identify the correct steps to patch the machine without disrupting any automation.
•While performing an audit of the new solution during the test phase, the company's information security team identifies that users can freely save confidential documents to OneDrive for Business.
•When creating the automation for the project closure process, you discover that some of the required information needs to be exported via the SAP GUI and extracted from a comma-separated value (CSV) file.
•When building the automation for the profile information system, you identify that all requests into the API will fail unless the following HTTP header value is specified:
o Accept: application/json