Solutions and ALM Flashcards

(49 cards)

1
Q

What is the primary purpose of a solution in Microsoft Power Platform?

A

It serves as a container for related resources to support application lifecycle management (ALM).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Name three benefits of using solutions with cloud flows.

A

Simplified management of related resources; Easy transport between environments via export/import; Use of connection references and environment variables to reduce environment‑specific edits; Version tracking through source control exports.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Which Power Platform products are covered by solutions for ALM?

A

Power Apps, Power Automate, and Power Virtual Agents.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Where can solutions be created?

A

Only in environments that have Microsoft Dataverse provisioned.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the two default solutions provided in every Dataverse environment?

A

Default and Common Data Services Default Solution.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Why should you create a custom solution publisher?

A

To apply a unique prefix that clearly identifies components belonging to your organization or product.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

How can you add a new cloud flow directly into a solution?

A

Open the solution, select + New, and choose Automated, Instant, or Scheduled cloud flow.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What happens when you add the same flow to multiple solutions?

A

Each solution contains a reference to the single flow definition—changes made in one solution appear in all.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What occurs when you add an existing flow created outside a solution?

A

The flow is converted and its definition is stored in Dataverse, then associated with the new solution.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Difference between ‘Remove from this solution’ and ‘Delete from this environment’ for a flow?

A

‘Remove’ only detaches the flow from the current solution; ‘Delete’ removes the definition entirely from the environment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What problem do connection references solve?

A

They abstract environment‑specific connections so the flow definition doesn’t need to be edited after deployment.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Where are connection references listed in a solution?

A

Alongside cloud flows in the solution component list.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

When importing a solution with a new connection reference, what prompt appears?

A

The importer is prompted to choose or create a connection for that reference.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Can multiple cloud flows share a single connection reference?

A

Yes, and changing the reference’s connection will affect all flows that use it.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the two parts of an environment variable?

A

Definition (type + default) and Current Value (environment‑specific override).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

How do environment variables support ALM best practices?

A

They allow each environment to provide its own values without editing the flow definition.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

What should you do after providing a development Current Value to avoid exporting it?

A

Remove the Current Value from the solution (keep it only in the environment).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Name two special data types for environment variables.

A

Data source and Secret.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Which solution type should you export for deployment to test or production?

A

Managed.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Which solution type should you always keep as a backup and for source control?

21
Q

Why is it recommended to export both managed and unmanaged versions during a release?

A

Managed is deployed downstream; unmanaged is retained as editable backup and for source control unpacking.

22
Q

What does the ‘Publish all changes’ option do before exporting a solution?

A

Publishes UI customizations that require publishing so they’re included correctly in the export.

23
Q

What happens if you import an unmanaged solution into an environment where components already exist?

A

Components are merged and overwritten additively; the action cannot be undone by removing the solution.

24
Q

How does importing a managed solution differ from unmanaged regarding layering?

A

Managed solutions create their own layer; upgrades replace earlier managed versions and can remove deleted components.

25
During import, when are you prompted for environment variables?
If the variable definition has no Current Value in the target environment.
26
To override a hard‑coded value per environment without editing the flow, what should you use?
An environment variable.
27
When exporting a solution for a non‑development environment, which export type do you pick?
Managed.
28
Does using solutions make cloud flows run faster?
No; performance is not a listed benefit.
29
Can you convert every flow created outside Dataverse into a solution component?
Not always; some flows are subject to known limitations and may not appear in the add‑existing list.
30
What tool can unpack an unmanaged solution into individual files for source control?
SolutionPackager or Power Platform CLI.
31
Name the four primary Power Platform environment types used in ALM.
Sandbox, Production, Developer (formerly Community), and Default.
32
Which environment type is created automatically for every tenant and shared by all users?
The Default environment.
33
What is the recommended minimum set of environments for healthy ALM?
At least Development and Production, but ideally Development, Test, and Production.
34
Who should have access to a Development environment versus a Production environment?
Development: app makers/developers (Environment Maker role) but not app users; Production: admins and end‑users only—makers and devs have no or minimal rights.
35
When creating an environment, why should you avoid installing Dynamics 365 apps unless required?
Because they cannot be uninstalled later and may introduce dependencies that complicate solution moves.
36
What are the three key areas of ALM as defined by Microsoft?
Governance, Application Development, and Maintenance.
37
List the four foundational pillars needed to implement ALM on Power Platform.
Environments, Solutions, Source control, and Automation (CI/CD).
38
Why is source control considered the 'single source of truth' in healthy ALM?
It centrally tracks every change, supports collaboration, and allows rollback—preventing environments from becoming the only copy of work.
39
Give two common ways to store solutions in source control.
1) Store the unpacked unmanaged solution and generate managed builds via a pipeline; 2) Store both unmanaged and managed packed files side‑by‑side.
40
What does branching and merging mean in source control, and name one strategy.
Branching creates parallel lines of work; merging combines them. Strategies include trunk‑based, release branching, or feature branching.
41
Which two Microsoft platforms are highlighted for building CI/CD pipelines for Power Platform?
GitHub and Azure DevOps.
42
Why must every environment participating in ALM include a Dataverse database?
Because solutions, pipelines, and key ALM features rely on Dataverse to store artifacts and metadata.
43
Can you import a solution into an environment running an older platform version than where it was exported?
Not reliably—imports should target environments on the same or newer version to avoid missing components.
44
What alignment rule helps multi‑geo organizations avoid version conflicts during solution import?
Place development environments in the same or an earlier service‑update station than production (e.g., develop in station 5 if prod is in stations 2 & 5).
45
Which admin portal lets you manage environments, data policies, and analytics for Power Platform?
The Power Platform admin center.
46
What in‑product feature lets makers deploy solutions between environments with one click?
Power Platform Pipelines.
47
Name three developer‑focused ALM tools for Power Platform.
Solution Packager, Power Platform CLI, and Azure DevOps Power Platform Build Tools (also accept Package Deployer).
48
Define application lifecycle management (ALM) in one sentence.
ALM is the governance, development, deployment, and maintenance of applications through repeatable, predictable processes.
49
Why should you avoid building customizations directly in the Default solutions?
Default solutions can’t be exported, use the random default publisher prefix, and mixing work there risks missing components during deployment.