PL-900 Practice Question: Manage the Microsoft Power Platform environment
A company wants to ensure that changes to a Power Platform solution are tracked and can be rolled back if necessary. The development team uses source control. What should the administrator configure to enable solution lifecycle management?
⚠ Common exam trap
PL-900 often tests the confusion between backup (data recovery) and source control (solution versioning), leading candidates to pick 'backup the environment' as if it enabled rollback of solution changes.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use managed solutions and export to source control
Solution lifecycle management in Power Platform relies on the ALM pattern: develop in an unmanaged solution, export it as a managed solution, and store the solution source (including the .zip and unpacked XML) in a source control repository such as Azure DevOps or GitHub. Managed solutions are immutable in target environments, preventing out-of-band edits, and the source-controlled artifacts enable versioning, diffing, and rollback by re-importing a prior version.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use managed solutions and export to source control
Why this is correct
Managed solutions are locked, so changes are made only in a development environment and shipped as versioned artefacts. Exporting them to source control gives traceable history and enables rollback to a prior solution version, meeting the lifecycle management requirement.
- ✗
Backup the environment daily
Why it's wrong here
Daily environment backups capture state, not the versioned solution artefacts the development team already manages; rollback of a solution requires exporting and importing managed or unmanaged solutions through pipelines tied to source control. Backups tempt because they restore an environment wholesale after corruption, which is a different recovery scenario from solution versioning.
- ✗
Share the app with the team
Why it's wrong here
Sharing grants users access to run an app; it neither versions solution components nor records changes, so rollback remains impossible. It tempts because sharing is the usual step when a team must collaborate on a canvas app, but collaboration on usage differs from lifecycle management of the solution itself.
- ✗
Disable sharing to prevent changes
Why it's wrong here
Disabling sharing restricts who can run the app; it does not track component changes or provide any rollback path, and it blocks legitimate users. It tempts as a crude change-control measure, yet source-controlled solution pipelines are what record versions, not access restrictions on the published app.
Go deeper
Related to this question
About these practice questions
One of 701 original PL-900 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
This PL-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-900 exam.