nerdexam
Microsoft

PL-500 · Question #10

Case Study 2: City Power and Light Background City Power and Light is one of the biggest energy companies in North America. They extract, produce and transport oil. The company has more than 50…

The correct answer is D. Create an environment variable. Update each desktop flow action to read the variable. This question tests the best approach for centrally managing run mode settings across multiple desktop flow actions without manual updates.

Develop automations

Question

Case Study 2: City Power and Light Background City Power and Light is one of the biggest energy companies in North America. They extract, produce and transport oil. The company has more than 50 offices and 100 oil extraction facilities throughout the United States, Canada, and Mexico. They use railways, trucks, and pipelines to move oil and gas from their facilities. The company provides the following services:

  • Produce oil from oil sands safely, responsibly, and reliably.
  • Refine crude of into high-quality products.
  • Develop and manage wind power facilities.
  • Transport oil to different countries/regions.

City Power and Light uses various Microsoft software products to manage is daily actives and run its machine-critical applications. Requirements ManagePipelineMaintenanceTasks A user named Admin1 creates a cloud flow named ManagePipelineMaintenanceTasks. Admin1 applies a data loss prevention (DLP) policy to the flow. Admin1 shares the flow with a user named PipelineManager1 as co-owner. You must determine the actions that PipelineManager1 can perform. You create a cloud flow that uses a desktop flow. The desktop flow connects to third-party services to fetch information. You must not permit the desktop flow to run for more than 20 minutes. You must configure sharing for MaintenanceScheduler to meet the following requirements:

  • User1 mustbe able to work with you to modify the desktop flow.
  • User2 must be able to access and review the run history for the flow.
  • You must grant User3 permissions to run but not modify the desktop flow.

ERPDataOperations flow City Power and light uses an enterprise resource planning (ERP) system. The ERP system does not have an API. Each day the company receives an email that contains an attachment. The attachment lists orders from the company's rail transportation partners. You must create an automation solution that reads the contents of the email and writes records to the ERP system. The solution must pass credential from a cloud flow to a desktop flow. RailStatusUpdater City Power and Light actively monitors all products in transit. You must create a flow named RailStatusUpdater that manages communications with railways that transport the company's products. RailStatusUpdater includes five desktop flow actions. You must run the desktop flows in attended mode during testing. You must run the desktop flows in unattended mode after you deploy the solution. You must minimize administrative efforts. Packaging You must package the automations in a solution. All required components must be included in the solution. Issues ProductionMonitor flow You create a cloud flow named ProductionMonitor which uses the Manually trigger a flow trigger. You plan to trigger ProductionMonitor from a cloud flow named ProdManager. You add a Run a Child flow action in ProdManager to trigger ProductionMonitor. When you attempt to save ProdManager the following error message displays:

Request to XRM API failed with error: 'Message:Flow client error returned with status code "Bad request" and details "("error": {"code":ChildFlowUnsupportedForinvokerConnections", "message":

The workflow with id 8d3bcde7-7e98-eb11-b1ac-000d3a32d53f", named FlowA cannot be used as a child workflow because child workflows only support embedded connections. "}}"Code" 0x80060467 InnerError.' CapacityPlanning flow Developers within the company use could flows to access data from an on-premises capacity planning system. You observe significant increases to the volume of traffic that the on-premises data gateway processes each day. You must minimize gateway failures. DataCollector flow You have a desktop flow that interacts with a web form. The flow must write data to several fields on the form. You are testing the flow. The flow fails when attempting to write data to any field on the web form. RailStatusUpdater flow The RailStatusUpdater flow occasionally fails due to machine connection errors. You can usually get the desktop flow to complete by resubmitting the cloud flow run. You must automate the retry process to ensure that you do not need to manually resubmit the cloud flow when machine connection errors occur. Question You need to configure the RailStatusUpdater cloud flow. What should you do?

Options

  • ACreate a JavaScript function to update the run mode values of each action within the desktop
  • BManually update each desktop flow action to change the run mode.
  • CCreate a desktop flow to update the run mode values of each action within the cloud flow.
  • DCreate an environment variable. Update each desktop flow action to read the variable.

How the community answered

(31 responses)
  • A
    3% (1)
  • B
    16% (5)
  • C
    10% (3)
  • D
    71% (22)

Why each option

This question tests the best approach for centrally managing run mode settings across multiple desktop flow actions without manual updates.

ACreate a JavaScript function to update the run mode values of each action within the desktop

JavaScript cannot directly interact with or update desktop flow action configurations; desktop flows use Power Automate Desktop scripts, not JavaScript.

BManually update each desktop flow action to change the run mode.

Manually updating each action is error-prone and time-consuming, violating the automation and consistency requirements described in the scenario.

CCreate a desktop flow to update the run mode values of each action within the cloud flow.

A desktop flow cannot modify the configuration of another desktop flow's actions at runtime; flow action properties are design-time settings.

DCreate an environment variable. Update each desktop flow action to read the variable.Correct

Creating an environment variable and configuring each desktop flow action to read from it centralizes the run mode value in one place, so changing the variable automatically propagates to all actions without editing each one individually, which is maintainable and scalable.

Concept tested: Environment variables for desktop flow run mode management

Source: https://learn.microsoft.com/en-us/power-automate/desktop-flows/manage-variables

Topics

#Power Automate Desktop#Environment Variables#Attended/Unattended Mode#Flow Configuration

Community Discussion

No community discussion yet for this question.

Full PL-500 Practice