nerdexam
Microsoft

PL-200 · Question #327

You are creating a model-driven app that has an embedded Power BI report. Another functional consultant set up an environment variable for the report. You add the dashboard to a solution in the…

The correct answer is B. Remove the environment variable current value. When a managed solution carries a development environment variable current value into production, you must remove that current value from the development environment before redeploying so each environment maintains its own independent value.

Configure Microsoft Dataverse

Question

You are creating a model-driven app that has an embedded Power BI report. Another functional consultant set up an environment variable for the report. You add the dashboard to a solution in the development environment and then import the changes to a production environment as a managed solution. When you test the report, the data appears the same as it did in the development environment. You delete the solution in production. You need to resolve the development environment issue before redeploying the solution. What should you do?

Options

  • AUpdate the environment variable current value
  • BRemove the environment variable current value.
  • CUpdate the environment variable default value.
  • DCreate a new environment variable.

How the community answered

(43 responses)
  • A
    2% (1)
  • B
    77% (33)
  • C
    7% (3)
  • D
    14% (6)

Why each option

When a managed solution carries a development environment variable current value into production, you must remove that current value from the development environment before redeploying so each environment maintains its own independent value.

AUpdate the environment variable current value

Updating the current value in development still includes that value in the exported solution, continuing to overwrite the production environment's value on the next import.

BRemove the environment variable current value.Correct

Environment variable current values are environment-specific overrides; if a current value exists in the development environment it gets packaged into the solution and overwrites the production value on import. Removing the current value from development ensures production can define its own current value independently, resolving the data bleed between environments.

CUpdate the environment variable default value.

Updating the default value affects all environments uniformly and does not resolve the per-environment isolation issue caused by the current value being included in the solution package.

DCreate a new environment variable.

Creating a new environment variable does not fix the existing variable's scoping problem and would require reconfiguring the embedded Power BI report reference throughout the solution.

Concept tested: Environment variable current value isolation across managed solution environments

Source: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables

Topics

#Environment variables#Managed solutions#Application Lifecycle Management (ALM)

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PL-200 Practice