Q01 - Question
Two managed solutions are installed in a Dataverse environment. Solution B was installed after Solution A, and both define the same component differently. Users see the behavior from Solution B. What happens if you uninstall Solution B?
Domain: Build Power Platform solutions (10–15%) Type: Single choice
- A. The managed solution below it takes effect, which is Solution A.
- B. The system solution defaults apply, even though Solution A remains installed.
- C. The unmanaged layer takes effect because it holds the previous customizations.
- D. Both solutions are removed because they define the same component.
A is correct.
Explanation: In Dataverse, managed layers stack in their installation order, meaning the last one installed sits above the earlier ones. When you uninstall Solution B, the managed solution directly below it takes effect, which is Solution A in this scenario. System defaults apply only after all managed solutions are uninstalled.
B is incorrect: System solution defaults apply only when you uninstall all managed solutions, and Solution A is still installed in this environment.
C is incorrect: The unmanaged layer holds unmanaged solutions and impromptu customizations, and it is not the layer directly beneath a managed solution.
D is incorrect: Uninstalling one managed solution does not remove another; the solution below it takes effect, so Solution A remains installed and active.
Q02 - Question
A developer must export a solution that contains only a changed form and view for one table. The developer wants granular development and wants to avoid dependency issues. Which approach should the developer use when adding the table to the solution?
Domain: Build Power Platform solutions (10–15%) Type: Single choice
- A. Select Add All Assets so every table asset is included.
- B. Select only the required assets, such as the form and view.
- C. Create a patch solution and delete the unneeded components.
- D. Export the solution and remove assets from the zip file.
B is correct.
Explanation: Solution segmentation allows you to export solutions with selected table assets, such as specific columns, forms, and views. Selecting only the required form and view enables granular development and avoids the dependency issues that frequently occur when you include every asset from the table.
A is incorrect: Choosing the Add All Assets option often leads to dependency issues and defeats the purpose of segmentation for granular development.
C is incorrect: A patch solution contains only changes for a parent-managed solution, and you cannot delete components with a patch to achieve segmentation.
D is incorrect: Editing the exported zip file is not a supported segmentation technique; segmentation requires selecting specific table assets before exporting the solution.
Q03 - Question
A parent managed solution is in production. A team must add one new component and later remove an obsolete component. They plan to use a patch solution for both changes. Which statement correctly describes the result?
Domain: Build Power Platform solutions (10–15%) Type: Single choice
- A. The patch can add the component and delete the obsolete one.
- B. The patch replaces the parent solution and removes its layer.
- C. The patch can add the component but can't delete components.
- D. The patch is placed below the parent solution when imported.
C is correct.
Explanation: A patch solution contains only the changes for a parent-managed solution, such as adding or editing components and assets. While patches are useful for making small updates like hotfixes, you cannot delete components with a patch. The team must use a different update method to remove the obsolete component.
A is incorrect: A patch solution can add or edit components, but the platform strictly restricts you from deleting existing components with a patch.
B is incorrect: A patch contains only specific changes and is layered on top of the parent solution rather than completely replacing the parent layer.
D is incorrect: When patches are imported into a Dataverse environment, they are layered on top of the parent solution, not placed below it.
Q04 - Question
A team stores an exported solution .zip file in source control. The schema definition is in one large customizations.xml file, which is hard to maintain. They want output that a source control system can maintain more readily. What should they use?
Domain: Build Power Platform solutions (10–15%) Type: Single choice
- A. The solution pack command to rebuild the .zip file
- B. The solution upgrade process to optimize the import
- C. The Power Apps admin center to split the schema file
- D. The Power Platform CLI solution unpack command
D is correct.
Explanation: The solution unpack command reversibly decomposes a solution zip file by dividing it into a logical folder structure. This process splits the massive schema definition file into smaller files, producing an output that can be more readily maintained by a source control system.
A is incorrect: The solution pack command is not used to decompose a zip file; unpack is the command that creates the logical folder structure.
B is incorrect: The solution upgrade process optimizes the import of managed solutions, but it does not decompose an exported zip file for source control.
C is incorrect: The Microsoft Power Platform CLI provides the solution unpack command; the admin center does not divide the solution into a folder structure.
Q05 - Question
An administrator imports several unmanaged solutions into a Dataverse environment. Some also modify forms and site maps. The administrator needs to know how these unmanaged customizations affect runtime behavior for those component types. Which statement is correct?
Domain: Build Power Platform solutions (10–15%) Type: Single choice
- A. Each unmanaged solution has its own layer, and the last one wins.
- B. Unmanaged solutions sit below the system layer and are overridden.
- C. Unmanaged solutions share one layer, and forms and site maps merge.
- D. Unmanaged solutions are ignored when managed solutions are installed.
C is correct.
Explanation: All imported unmanaged solutions and impromptu customizations share a single, unmanaged layer in Dataverse. For certain components like site maps and forms, each layer is merged to produce the runtime behavior. This merge logic applies as opposed to a strict last layer wins behavior.
A is incorrect: Unmanaged solutions do not each have a distinct layer; they share a single unmanaged layer, and components like forms use merge behavior.
B is incorrect: The system layer is at the base of the managed layers level, and unmanaged solutions do not sit below this system layer.
D is incorrect: Unmanaged solutions and impromptu customizations exist at the unmanaged layer and are not ignored when managed solutions are installed in the environment.
Q06 - Question
A team built a canvas app and a flow in a development environment. They must move the app and its table definitions to a test environment. A manager expects the existing table records to arrive in test too. What should you tell the team?
Domain: Build Power Platform solutions (10–15%) Type: Single choice
- A. The solution transports metadata only, so the records must be moved separately.
- B. The solution transports table records when you export it as managed.
- C. The solution transports records only for tables that a model-driven app uses.
- D. The solution transports records when the flow is included in the solution.
A is correct.
Explanation: Solutions transport only metadata, such as tables, their columns, and configuration data. No business data is transported. The test environment receives the table definitions and the app, but the existing records stay in the source environment. You must inform the manager that business data requires a separate migration process.
B is incorrect: Exporting as managed changes the solution type for deployment, but business data still is not transported with the solution.
C is incorrect: The documented behavior has no exception for model-driven apps. Only metadata is transported, not business data, for any table.
D is incorrect: Adding a flow packages the flow as a component. It does not cause table records to be included in the solution.
Q07 - Question
You created a solution named Volunteer Request in Power Apps. A flow and a table already exist outside the solution. You want both items in the solution without rebuilding them. Which action should you use in the solution?
Domain: Build Power Platform solutions (10–15%) Type: Single choice
- A. Select + New, and then create a flow and a table.
- B. Select + Add existing, and then select Flow and Table.
- C. Select Export solution, and then select the flow and the table.
- D. Select Import, and then select the flow and the table.
B is correct.
Explanation: Inside the solution, the + Add existing menu lets you incorporate existing apps, tables, and flows. You select Table for existing tables and Flow for existing flows. This action brings the current items into the solution container without requiring you to recreate them from scratch.
A is incorrect: + New creates new items in the solution, so it would produce duplicates instead of using the existing flow and table.
C is incorrect: Export solution packages a solution into a zip file for another environment. It does not add existing items to the solution.
D is incorrect: Import brings a solution zip file into an environment. It does not add existing flows or tables to a solution.
Q08 - Question
A maker must review the columns, relationships, and business rules of a table in the Volunteer Request solution. The maker is in Power Apps and has opened Solutions. What should the maker do next?
Domain: Build Power Platform solutions (10–15%) Type: Single choice
- A. Select the flow, and then select Edit.
- B. Select the canvas app, and then select Edit.
- C. Select Volunteer Request, select the table, and then select Edit.
- D. Select Export solution, and then open the downloaded zip file.
C is correct.
Explanation: You must open the solution first, because editing solution-aware items starts from within the solution container. Selecting the table and then choosing Edit opens the specific area where you can view the columns, relationships, business rules, and other table details required by the maker.
A is incorrect: Selecting Edit on a flow opens the flow edit mode, which does not display the table columns, relationships, or business rules.
B is incorrect: Selecting Edit on a canvas app opens Power Apps studio, which is used for the app interface and not the table definition.
D is incorrect: Exporting creates a zip file for transport to another environment. It is not the correct way to view or edit table columns.
Q09 - Question
You export a solution from a development environment to deploy to a production environment. Base version is 1.0.0.0. The update is a small change. Which export type and version meet the requirements?
Domain: Build Power Platform solutions (10–15%) Type: Single choice
- A. Export as unmanaged with version 1.0.0.0.
- B. Export as unmanaged with version 0.9.0.0.
- C. Export as managed with version 1.0.0.0.
- D. Export as managed with version 1.0.0.1.
D is correct.
Explanation: Production is a destination where you must select Managed, which is the recommended option for downstream environments. Furthermore, an update must have a higher major, minor, build, or revision number than the parent solution. Therefore, version 1.0.0.1 is a valid small update to the 1.0.0.0 base.
A is incorrect: Unmanaged is used for moving to another development environment, and the 1.0.0.0 version number is not higher than the parent version.
B is incorrect: Unmanaged is not the correct choice for production deployments, and 0.9.0.0 is lower than the parent solution version, which is invalid.
C is incorrect: Managed is correct for production, but 1.0.0.0 does not exceed the parent version, so it is not a valid update number.
Q10 - Question
A team exports a solution as one compressed file and checks it into source control. Reviewers can see that the file changed but not which component changed. The team uses Power Platform Build Tools. Which task should they add before check-in?
Domain: Build Power Platform solutions (10–15%) Type: Single choice
- A. Unpack Solution
- B. Pack Solution
- C. Set Solution Version
- D. Import Solution
A is correct.
Explanation: The Unpack Solution task breaks the compressed solution file into individual files for each component. Checking those separate files into source control gives the team a detailed log of exactly what changed, instead of showing only that the single large file was modified during the export process.
B is incorrect: Pack Solution builds a solution.zip file from source control for import. It does the reverse of what the reviewers need in this scenario.
C is incorrect: Set Solution Version updates the version number to implement a consistent versioning strategy. It does not split the compressed file into components.
D is incorrect: Import Solution loads a solution into a target environment. It does not create per-component files for checking into a source control system.