2026/January Latest Braindump2go PL-500 Exam Dumps with PDF and VCE Free Updated Today! Following are some new Braindump2go PL-500 Real Exam Questions!
QUESTION 133
You are using the Microsoft Power Apps maker portal to begin deployment of a solution. You are preparing for deployment of updates from a test environment to production.
You need to deploy the solution.
Which three actions should you perform? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
A. Set the solution version.
B. Create the environment.
C. Delete the solution.
D. Apply the solution upgrade.
E. Import the solution.
Answer: ADE
QUESTION 134
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:
![]()
You need to install Windows updates on the desktop flow machines.
What should you do?
A. Set the machine group in maintenance mode.
B. Enable maintenance mode on all machines.
C. Disable the banker desktop cloud flow.
D. Enable maintenance mode on each machine separately.
E. Update the connected environment on the running machines.
Answer: A
QUESTION 135
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:
![]()
You need to set up a policy for the developer to perform desktop flow testing.
Which two actions should you do? Each correct answer presents a part of the solution.
NOTE: Each correct selection is worth one point.
A. Create a tenant-level Microsoft Power Platform data loss prevention (DLP) policy.
B. Add the custom connector to the Non-business connector group.
C. Create a Microsoft Power Platform data loss prevention (DLP) policy in the development environment.
D. Add the custom connector to the Business connector group.
E. Move the SharePoint connector to the Non-business connector group
Answer: DE
QUESTION 136
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:
![]()
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.
Answer: CD
QUESTION 137
Hotspot Question
You are performing machine registration for your environment and assigning security roles to users.
Several Power Automate desktop flows will run across several machines.
You must restrict which users on the team can register, share, and modify the machines.
You need to assign permissions to users by using out-of-the-box desktop flow security roles.
Which security role should you use for each action? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
![]()
Answer:
![]()
QUESTION 138
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:
![]()
Hotspot Question
You need to identify the values or the behavior for the pattern added to the tenant Microsoft Power Platform data loss prevention (DIP) policy.
What should you identify? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
![]()
Answer:
![]()
QUESTION 139
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:
![]()
QUESTION 140
You are developing an RPA solution that requires browser automation.
You are testing the flow. You observe that the flow does not interact with web page elements in Microsoft Edge.
You need to troubleshoot the issue.
What should you do?
A. Ensure the Power Automate for desktop browser extension is downloaded and enabled in Microsoft Edge.
B. Open Power Automate machine runtime and select Troubleshoot.
C. Ensure the UI flows/Selenium extension is downloaded and enabled in Microsoft Edge.
D. Enable error handling on the action to retry on failure.
Answer: A
Explanation:
For Power Automate Desktop to interact with web elements in a browser (like Microsoft Edge), the “Power Automate for desktop” browser extension must be installed and enabled. Without this extension, the automation flow will not be able to access or interact with web page elements, which would cause the issue described.
QUESTION 141
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. Move the file to the user’s documents folder.
B. Change the location of the file to a specific path that is not dependent on the signed-in user.
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.
Answer: B
QUESTION 142
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.
Answer: B
QUESTION 143
You have an automation solution that uses a desktop flow. The flow reads data from a file that is stored on UserA’s machine and writes 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 the file does not exist. You confirm that the file is present on UserB’s desktop.
You need to resolve the issue.
What should UserB do?
A. Move the file to the user’s documents folder.
B. Modify the action to retry if the process cannot find the file.
C. 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.
D. Change the access rights for the file to allow read operations for the current user.
Answer: C
QUESTION 144
Case Study 4: First Up Consultants
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:
o Storage for project-level information, such as start date, end date and client data.
o A 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.
o Information regarding internal and external consultants is stored within a custom table called Resources.
o Information 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:
o dpStartDate: A date picker control to indicate the start date of the time entry.
o dpEndDate: A date picker control to indicate the end date of the time entry.
o inptDescription: 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
You need to recommend a solution for the project closure steps.
Which solution should you recommend?
A. Classic workflow
B. Desktop flow
C. Cloud flow
D. Document Automation Toolkit
Answer: B
QUESTION 145
Case Study 4: First Up Consultants
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:
o Storage for project-level information, such as start date, end date and client data.
o A 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.
o Information regarding internal and external consultants is stored within a custom table called Resources.
o Information 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:
o dpStartDate: A date picker control to indicate the start date of the time entry.
o dpEndDate: A date picker control to indicate the end date of the time entry.
o inptDescription: 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
You need to determine the correct action to use for the time entry automation.
Which action should you use?
A. HTTP
B. Invoke web service
C. HTTP with Azure AD
D. Invoke SOAP web service
Answer: B
QUESTION 146
Case Study 4: First Up Consultants
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:
o Storage for project-level information, such as start date, end date and client data.
o A 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.
o Information regarding internal and external consultants is stored within a custom table called Resources.
o Information 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:
o dpStartDate: A date picker control to indicate the start date of the time entry.
o dpEndDate: A date picker control to indicate the end date of the time entry.
o inptDescription: 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
Drag and Drop Question
You need to recommend a solution to address the requirements and issues.
Which feature should you recommend? To answer, move the appropriate feature to the correct requirement or issue. You may use feature once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
![]()
Answer:
![]()
QUESTION 147
Case Study 4: First Up Consultants
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:
o Storage for project-level information, such as start date, end date and client data.
o A 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.
o Information regarding internal and external consultants is stored within a custom table called Resources.
o Information 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:
o dpStartDate: A date picker control to indicate the start date of the time entry.
o dpEndDate: A date picker control to indicate the end date of the time entry.
o inptDescription: 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
Drag and Drop Question
You need to implement the expressions for the Time Entry Application automation.
Which expressions should you use to address the requirements and issues? To answer, move the appropriate expression to the correct requirement or issue. You may use each expression once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
![]()
Answer:
![]()
QUESTION 148
Case Study 4: First Up Consultants
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:
o Storage for project-level information, such as start date, end date and client data.
o A 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.
o Information regarding internal and external consultants is stored within a custom table called Resources.
o Information 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:
o dpStartDate: A date picker control to indicate the start date of the time entry.
o dpEndDate: A date picker control to indicate the end date of the time entry.
o inptDescription: 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
Drag and Drop Question
You need to build the automation for Time Entry Application.
Which four 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.
![]()
Answer:
![]()
QUESTION 149
Case Study 4: First Up Consultants
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:
o Storage for project-level information, such as start date, end date and client data.
o A 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.
o Information regarding internal and external consultants is stored within a custom table called Resources.
o Information 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:
o dpStartDate: A date picker control to indicate the start date of the time entry.
o dpEndDate: A date picker control to indicate the end date of the time entry.
o inptDescription: 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
You need to determine the formula to use for the time entry posting automation.
Which formula should you use?
A. ‘Submit Time Entry’.Run(dpStartDate.InputTextPlaceholder, dpEndDate.InputTextPlaceholder, inptDescription.Text)
B. ‘Submit Time Entry’.Run(dpStartDate.SelectedDate, dpEndDate.SelectedDate, inptDescription.Text)
C. ‘Submit Time Entry’.Run(dpStartDate.InputTextPlaceholder, dpEndDate.InputTextPlaceholder, varUserName)
D. ‘Submit Time Entry’.Run(dpStartDate.SelectedDate, dpEndDate.SelectedDate, varUserName)
Answer: B
QUESTION 150
Case Study 4: First Up Consultants
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:
o Storage for project-level information, such as start date, end date and client data.
o A 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.
o Information regarding internal and external consultants is stored within a custom table called Resources.
o Information 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:
o dpStartDate: A date picker control to indicate the start date of the time entry.
o dpEndDate: A date picker control to indicate the end date of the time entry.
o inptDescription: 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
You need to resolve the issue with the profile information system automation.
What should you do?
A. Set HTTP host URL.
B. Set query string parameter.
C. Define a policy.
D. Define a data loss prevention policy
E. Create custom code.
Answer: B
QUESTION 151
Case Study 4: First Up Consultants
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:
o Storage for project-level information, such as start date, end date and client data.
o A 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.
o Information regarding internal and external consultants is stored within a custom table called Resources.
o Information 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:
o dpStartDate: A date picker control to indicate the start date of the time entry.
o dpEndDate: A date picker control to indicate the end date of the time entry.
o inptDescription: 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
You need to identify the components required to deploy the automation for Project Planning Application.
Which three components should you identify? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.
A. Application ID
B. Client secret
C. Username
D. Tenant ID
E. Password
Answer: BCE
QUESTION 152
Case Study 4: First Up Consultants
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:
o Storage for project-level information, such as start date, end date and client data.
o A 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.
o Information regarding internal and external consultants is stored within a custom table called Resources.
o Information 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:
o dpStartDate: A date picker control to indicate the start date of the time entry.
o dpEndDate: A date picker control to indicate the end date of the time entry.
o inptDescription: 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
Drag and Drop Question
You need to determine the correct group for each connector used in the automations.
Which groups should you use? To answer, move the appropriate connector to the correct group. You may use each group once, more than once, or not at all.
You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
![]()
Answer:
![]()
QUESTION 153
Case Study 4: First Up Consultants
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:
o Storage for project-level information, such as start date, end date and client data.
o A 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.
o Information regarding internal and external consultants is stored within a custom table called Resources.
o Information 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:
o dpStartDate: A date picker control to indicate the start date of the time entry.
o dpEndDate: A date picker control to indicate the end date of the time entry.
o inptDescription: 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
Hotspot Question
You need to resolve the issue with the IT support team.
Where should you direct them to resolve the problem? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
![]()
Answer:
![]()
QUESTION 154
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
A procurement department is using email to collect large volumes of quotes from vendors.
Data from quotes, including vendor data and quote terms, must be stored in Microsoft Dataverse.
You need to create a solution to automate the process.
Solution: Cloud flow using the Extract most relevant words and phrases from text AI Builder model
Does the solution meet the goal?
A. Yes
B. No
Answer: B
Explanation:
Reference:
https://learn.microsoft.com/en-us/ai-builder/form-processing-model-in-flow
QUESTION 155
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
A procurement department is using email to collect large volumes of quotes from vendors.
Data from quotes, including vendor data and quote terms, must be stored in Microsoft Dataverse.
You need to create a solution to automate the process.
Solution: Extract custom information from documents AI Builder model.
Does the solution meet the goal?
A. Yes
B. No
Answer: A
Explanation:
Reference:
https://learn.microsoft.com/en-us/ai-builder/form-processing-model-in-flow
QUESTION 156
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
A procurement department is using email to collect large volumes of quotes from vendors.
Data from quotes, including vendor data and quote terms, must be stored in Microsoft Dataverse.
You need to create a solution to automate the process.
Solution: Cloud flow using the Extract information from invoices AI Builder model.
Does the solution meet the goal?
A. Yes
B. No
Answer: B
Explanation:
Reference:
https://learn.microsoft.com/en-us/ai-builder/form-processing-model-in-flow
Resources From:
1.2026 Latest Braindump2go PL-500 Exam Dumps (PDF & VCE) Free Share:
https://www.braindump2go.com/pl-500.html
2.2026 Latest Braindump2go PL-500 PDF and PL-500 VCE Dumps Free Share:
https://drive.google.com/drive/folders/1hOwA31eoEP2dL206T4q3J2cvBrCUUHlg?usp=sharing
3.2026 Free Braindump2go PL-500 Exam Questions Download:
https://www.braindump2go.com/free-online-pdf/PL-500-VCE-Dumps(133-156).pdf
Free Resources from Braindump2go,We Devoted to Helping You 100% Pass All Exams!