PL-500 · Question #6
Case Study 1: Contoso Pharmaceuticals Background: Contoso Pharmaceuticals distributes specialty pharmaceuticals, ingredients, and raw materials throughout North America. The company has 33 offices…
The correct answer is A. Set the current value for the accounts payable mailbox in the environment. C. Turn off and then turn on the cloud flows. D. Use separate environment variables for the cloud flow and the canvas app. This question tests how to correctly configure and activate environment variables for a mailbox setting used across both cloud flows and a canvas app.
Question
Options
- ASet the current value for the accounts payable mailbox in the environment.
- BSet the default value for the accounts payable mailbox in the environment.
- CTurn off and then turn on the cloud flows.
- DUse separate environment variables for the cloud flow and the canvas app.
- EUse one environment variable for both the cloud flows and the canvas app.
How the community answered
(23 responses)- A78% (18)
- B9% (2)
- E13% (3)
Why each option
This question tests how to correctly configure and activate environment variables for a mailbox setting used across both cloud flows and a canvas app.
Setting the current value overrides the default value at the environment level, which is required to supply the actual accounts payable mailbox address used at runtime without altering the solution's portable default.
Setting the default value modifies the solution-level default, which is intended to be environment-agnostic and would not correctly isolate the runtime mailbox address per environment.
Cloud flows cache environment variable values at activation time, so turning them off and back on forces the flows to re-read the newly set current value and apply it.
Using separate environment variables for the cloud flow and canvas app allows each component to reference and be updated independently, preventing unintended side effects when one component's mailbox changes.
Sharing one environment variable between both components creates tight coupling, meaning a change for one component unintentionally affects the other.
Concept tested: Power Platform environment variable current vs default values
Source: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables
Community Discussion
No community discussion yet for this question.