PL-500 Question #139: Real Exam Question with Answer & Explanation

Question

Case Study 3: Woodgrove Bank 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: Drag and Drop Question You need to configure the machine deployment for the IT administrator. 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. NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select. Answer:

Explanation

The user needs to correctly order the steps to set up new machines and add them to a Power Automate machine group.

Approach. The correct interaction is to drag the following actions into the 'Answer Area' in the specified order:

1. Use register operation to register the new machines. - Before machines can be part of a group or used by Power Automate, they must first be registered with the Power Automate service. This typically involves installing Power Automate for Desktop and signing in, which registers the machine.
2. Create the machine group in the Power Automate portal. - A logical container (the machine group) must exist in the Power Automate portal before individual machines can be added to it.
3. Add the machines to the machine group by using the join group operation. - Once machines are registered and the machine group is created, the machines can then be associated with that group using the 'join group' operation, making them available for unattended automation and load balancing within the group.

This sequence ensures that the machines are first recognized by Power Automate, then a logical grouping mechanism is established, and finally, the machines are assigned to that group.

Common mistakes.

• common_mistake. Other options are incorrect because they either describe a prerequisite (which is implied by registration but not an action in itself), a maintenance task, or an irrelevant operation for the initial setup of a new machine group:
• 'Add the new machines in the Power Automate machine runtime.': While installing the runtime is a prerequisite for registration, 'Use register operation to register the new machines' is the direct action that makes the machine available to the Power Automate service.
• 'Perform a machine group certificate renewal.': This is a maintenance task for existing machine groups, not part of the initial setup.
• 'Add the machine group and enable maintenance mode.': Enabling maintenance mode is for specific operational scenarios (e.g., patching, troubleshooting) on an existing group, not for initial group creation or machine setup.

Concept tested. Power Automate machine group management, including machine registration, machine group creation, and adding machines to a group for unattended desktop flows and high availability/load balancing.

No community discussion yet for this question.