Build Power Platform solutions — PL-400 Practice Quiz

Question 1

Your team maintains a Dataverse solution called SalesCore in a dedicated Dev environment. You are building an Azure DevOps YAML pipeline using the Power Platform Build Tools to automate deployment to Test and Production. The goal is to ensure that the artifact deployed to downstream environments cannot be edited directly in those environments, while keeping the unmanaged source in Dev available for continued development. Which sequence of Build Tools tasks should the CI pipeline perform against the Dev environment?

Accepted Answer

Export the solution as managed from Dev and store the managed artifact, keeping the unmanaged solution in Dev for ongoing development.

Answer

Export the solution as unmanaged, then check it into source control and import the unmanaged solution into Test and Production.

Answer

Export the solution as managed from Dev, publish customizations, then import the managed solution directly into Dev before deploying.

Answer

Clone the solution as a patch, export the patch as unmanaged, and import it into Test and Production as the deployable artifact.

Question 2

Your team ships a managed solution named 'SalesCore' to production. A critical bug requires an urgent field change, but the full development solution contains many in-progress, untested components you cannot release yet. You need to deploy only the single fixed component to production quickly, while preserving the ability to later roll the fix into the base solution. Which ALM action should you take?

Accepted Answer

Use 'Clone a Patch' to create a patch of SalesCore, add only the fixed component, then export and import it as a managed patch to production.

Answer

Use 'Clone Solution' to produce a new base version of SalesCore containing all current components and deploy it to production.

Answer

Manually edit the fixed component directly in the production environment through the maker portal.

Answer

Create a brand-new unmanaged solution containing only the fixed component and import it as unmanaged into production.

Question 3

Your organization uses Power Platform Pipelines to move solutions from a development environment to test and then to production. The compliance team requires that a designated reviewer must explicitly approve every deployment into the production environment before the artifacts are imported, but deployments to the test environment should remain fully automated. As the maker responsible for the pipeline, what should you configure to meet this requirement?

Accepted Answer

Add a deployment stage pre-deployment approval on the production stage in the pipeline configuration, assigning the reviewer as the approver.

Answer

Export the solution as managed and manually import it into production only after the reviewer emails their approval.

Answer

Create a Dataverse security role that removes solution import privileges from all users except the reviewer in the production environment.

Answer

Configure a DLP policy on the production environment that blocks the pipeline connector until the reviewer grants an exception.

Question 4

Your team uses Azure DevOps with the Power Platform Build Tools to automate deployment of a managed solution from a build environment to a QA environment. After a release, testers report that a recently removed workflow is still active in QA. Investigation shows the solution export/import pipeline succeeded, but the workflow persists across releases. You need to ensure that components deleted from the solution in the source environment are also removed from the target during automated import. Which action should you take in the pipeline configuration?

Accepted Answer

Export and import the solution as a solution upgrade (using stage-and-upgrade) rather than a solution update.

Answer

Enable the 'Overwrite Unmanaged Customizations' option on the Import Solution task.

Answer

Use the 'Import Solution' task with a managed solution and enable the 'Convert to Managed' setting.

Answer

Add a 'Publish Customizations' task after the import to force removal of orphaned components.

Question 5

Your team has five Power Platform developers building customizations for the same managed solution that will eventually be deployed to production. You want to minimize the risk of developers overwriting each other's unmanaged changes, keep component authoring isolated, and still support a controlled path to a shared build environment. Which environment strategy should you adopt?

Accepted Answer

Give each developer their own isolated development environment, then merge their exported unmanaged solutions into a shared build/integration environment before packaging as managed.

Answer

Have all five developers work directly in a single shared development environment with the unmanaged solution, then export to production.

Answer

Have all developers work in the production environment using an unmanaged solution and rely on solution layering to resolve conflicts at runtime.

Answer

Use a single default environment for all developers and back up the environment nightly to recover from overwrites.

Question 6

Your team maintains a Dataverse solution that includes a cloud flow calling an external REST service. The service endpoint URL differs between the Development, Test, and Production environments. When you export the managed solution and import it into Test, you must ensure the flow automatically points to the correct Test endpoint without editing the flow after each deployment. What is the recommended ALM approach?

Accepted Answer

Add an environment variable to the solution for the endpoint URL and supply the environment-specific value during solution import

Answer

Hard-code the Test endpoint in the flow before export, then re-import a separate flow copy into each environment

Answer

Store the endpoint in a Dataverse configuration table row and include the row as sample data in the managed solution

Answer

Create a connection reference and set its value to the Test endpoint URL when configuring the connection

Question 7

You maintain a managed solution that contains an environment variable used to store an API base URL. In your development environment you set both a default value and a current value while testing. When you export the solution as managed and import it into the production environment, you want production administrators to be able to supply their own value without your development test value overriding it. What should you do before exporting the solution?

Accepted Answer

Export the solution with only the environment variable's default value populated and remove the current value in the development environment.

Answer

Export the solution with the current value populated so production inherits it, then have admins edit the current value after import.

Answer

Delete the environment variable and hardcode the URL in the connection reference instead.

Answer

Set both default and current values, and mark the environment variable as required so production must change it.

Question 8

Your team ships a managed solution containing an environment variable named 'ApiBaseUrl' that has a default value pointing to the development endpoint. In the test environment, an administrator previously set a current value pointing to the test endpoint. After you import an updated version of the managed solution (which changes the default value to a new development endpoint), users report that the flows are still calling the old test endpoint. What is the cause of this behavior?

Accepted Answer

The environment variable's current value in the test environment takes precedence over the default value, and imports do not overwrite an existing current value.

Answer

Managed solution imports always reset environment variable current values to the default value, so the flow is misconfigured elsewhere.

Answer

Environment variables cannot be used inside cloud flows, so the URL must be hardcoded in the flow action.

Answer

The default value from the newest solution layer overrides the current value, so the flow should be calling the new development endpoint.

Question 9

Your organization has enabled a managed development environment where five developers build solutions collaboratively. The security team requires that developers can create, edit, and import solutions and customize entities, but must NOT be able to grant themselves or others administrative roles, manage environment settings, or delete the environment. As the Power Platform administrator, what is the most appropriate way to assign access following least-privilege principles?

Accepted Answer

Assign each developer the System Customizer security role and grant environment membership without adding them to the Environment Admin role.

Answer

Assign each developer the System Administrator security role in the environment so they have full flexibility during development.

Answer

Add each developer to the Environment Admin role in the Power Platform admin center and remove all Dataverse security roles.

Answer

Assign each developer the Basic User security role and create a sharing rule for the solution components.

Question 10

You built a PCF code component that reads and writes records in a custom Dataverse table named Contract Approvals. The component will be embedded on a form used by approvers. Security requirements state that approvers must have only the minimum privileges needed for the component to function, and they should not gain broad access to other tables. What should you do to grant the required Dataverse privileges following least privilege?

Accepted Answer

Create a custom security role granting only Read and Write privileges on the Contract Approvals table at the appropriate scope, and assign it to the approvers.

Answer

Assign the approvers the System Administrator security role so the PCF component can perform all operations reliably.

Answer

Add the Contract Approvals table privileges to the PCF component manifest so the control elevates permissions automatically at runtime.

Answer

Enable field-level security on all columns of the Contract Approvals table and assign approvers the System Customizer role.

Question 11

Your team maintains a Dataverse solution across three environments: Development, Test, and Production. Currently, developers manually export the managed solution from Development and import it into each downstream environment, which is error-prone and lacks approval controls. Leadership wants a low-code, governed deployment process that runs entirely inside Power Platform without requiring Azure DevOps or GitHub, and that allows a designated approver to sign off before Production deployment. What should you implement?

Accepted Answer

Configure Power Platform Pipelines in a dedicated host environment, defining Development as the source and Test and Production as target stages with a pre-deployment approval on the Production stage.

Answer

Create an Azure DevOps release pipeline using the Power Platform Build Tools tasks with an approval gate before the Production stage.

Answer

Use the Power Platform CLI (pac) in a scheduled script to export and import the solution, adding a manual email approval step.

Answer

Enable managed environments and rely on solution checker enforcement to gate deployment to Production.

Question 12

Your organization has two separate development teams. Team A builds and owns a set of Dataverse tables and a Custom API packaged in a solution called 'CoreServices'. Team B is building a canvas app in a solution called 'FieldApp' that must reference Team A's Custom API and one of their tables. Both teams work in isolated development environments and deploy through a shared Power Platform pipeline into Test and Production. What is the recommended way for Team B to develop against Team A's components while maintaining a clean ALM story?

Accepted Answer

Import Team A's 'CoreServices' solution as a managed solution into Team B's development environment, then add references to those components from the unmanaged 'FieldApp' solution.

Answer

Have Team B recreate the tables and Custom API directly inside their own unmanaged 'FieldApp' solution so there are no cross-solution dependencies.

Answer

Import Team A's 'CoreServices' solution as an unmanaged solution into Team B's development environment so Team B can edit the shared components as needed.

Answer

Merge both teams' work into a single unmanaged solution and have both teams develop in the same shared development environment.

Question 13

Your team maintains a managed solution for a model-driven app. During development, makers edited the app directly in the shared development environment, and their unmanaged customizations are now mixed together. You need to establish a repeatable ALM process so that future changes can be tracked, reviewed, and deployed reliably. Which approach should you adopt as the source of truth for the solution?

Accepted Answer

Export the unmanaged solution, unpack it with the Solution Packager (via Power Platform Build Tools), and commit the unpacked components to a source control repository as the source of truth.

Answer

Treat the development environment as the source of truth and export a managed solution manually whenever a release is needed.

Answer

Export the managed solution and store the .zip file directly in a document library that developers download before each change.

Answer

Enable auditing in the development environment and use the audit log to reconstruct changes when building each release.

Question 14

Your team ships a managed solution named ContosoSales to a production environment. A support engineer, working directly in production, unmanaged-layered several form and column changes to hotfix an urgent issue. Now the next managed solution import is not showing your intended field label change because the production unmanaged layer sits on top. You want to permanently move that emergency fix back into your development ALM process and remove the unmanaged override in production so the managed layer takes effect again. What should you do?

Accepted Answer

In production, use 'Remove active customizations' on the affected components to delete the unmanaged layer, then reproduce the fix in the dev environment, and ship it through your normal managed solution pipeline.

Answer

Delete the managed ContosoSales solution from production and re-import it, which clears all layers including the unmanaged override.

Answer

Export the production environment as an unmanaged solution and import it into development so the hotfix becomes your new source of truth.

Answer

Increase the version number of the managed solution and re-import it; a higher version automatically supersedes any unmanaged layer in production.

Question 15

Your team ships a managed solution named 'FieldServiceCore' (version 2.0) to a customer's production environment. The customer reports a critical bug in a plugin. You must deliver a fix that patches only the affected plugin assembly, can be quickly applied on top of the currently installed managed solution, and can later be rolled up cleanly when version 3.0 ships. Which approach should you use?

Accepted Answer

Create a managed patch of FieldServiceCore containing only the updated plugin assembly and import it as an update to the installed solution.

Answer

Export the full FieldServiceCore solution as version 2.1 managed and import it using the 'Overwrite customizations' option.

Answer

Create a new unmanaged solution in production, add the plugin assembly, and edit it directly in the customer environment.

Answer

Uninstall FieldServiceCore version 2.0 from production and reinstall a rebuilt version 2.0 containing the corrected assembly.

Question 16

Your team uses Azure DevOps with the Power Platform Build Tools to automate solution deployments. The lead developer wants the CI pipeline to automatically analyze the unmanaged solution for coding issues, security vulnerabilities, and performance anti-patterns (such as plug-ins that call synchronous external services) before the artifact is exported and promoted. The build must fail if critical issues are detected. Which Build Tools task should you add to the pipeline to meet this requirement?

Accepted Answer

Power Platform Checker task configured with a rule set and a failure threshold for critical issues

Answer

Power Platform Export Solution task with the 'Export as Managed' option enabled

Answer

Power Platform Publish Customizations task run before the export step

Answer

Power Platform Set Solution Version task combined with a manual approval gate

Question 17

Your team maintains two managed solutions in a production environment: a 'CoreEntities' solution containing a custom table 'Contract', and a 'ContractApprovals' solution containing a model-driven app and a business process flow that both reference the 'Contract' table. A cleanup request asks you to delete the 'CoreEntities' solution from production because it is being retired. When you attempt the deletion, it fails with a dependency error. What is the correct first step to allow the deletion to proceed while preserving supported ALM practices?

Accepted Answer

Remove or uninstall the 'ContractApprovals' solution (or rework it to remove references to 'Contract') before deleting 'CoreEntities', since a managed solution cannot be deleted while another managed solution depends on its components.

Answer

Manually delete the 'Contract' table directly from the environment's default solution to break the dependency, then retry deleting 'CoreEntities'.

Answer

Export 'CoreEntities' as unmanaged, delete the component references, and re-import it as managed to strip the dependency chain.

Answer

Add the 'ContractApprovals' components into 'CoreEntities' as a single merged solution and then delete it in one operation.

Question 18

Your team maintains two managed solutions: 'CoreEntities' (contains custom tables and choice columns) and 'SalesApp' (contains a model-driven app and business rules that reference the CoreEntities tables). A junior developer attempts to import only the 'SalesApp' managed solution into a fresh production environment, and the import fails with a missing dependency error. What is the most appropriate way to resolve this while following ALM best practices?

Accepted Answer

Import the 'CoreEntities' managed solution into the production environment first, then import 'SalesApp'.

Answer

Merge both solutions into a single unmanaged solution and import that into production.

Answer

Export 'SalesApp' as an unmanaged solution so the missing components are included automatically.

Answer

Remove the business rules from 'SalesApp' so it no longer has a dependency on 'CoreEntities'.

Question 19

A managed solution from your vendor sets a form field to 'Business Recommended'. After a recent import, users report the field is now displaying as 'Optional' instead. You open the field's solution layers in the target environment and see two layers: the vendor's managed layer at the bottom, and an unmanaged layer on top that was created by a developer directly customizing the field in the environment. You need the field to honor the vendor's managed configuration going forward without losing any other legitimate unmanaged customizations. What should you do?

Accepted Answer

Remove the active unmanaged layer for that specific component so the managed layer becomes effective.

Answer

Delete the vendor's managed solution and reimport it to force the managed layer to the top.

Answer

Export the environment as a managed solution to collapse all layers into a single managed layer.

Answer

Increase the version number of the vendor's managed solution so its layer takes precedence.

More PL-400 practice