PL-100 · Question #326
A company uses Microsoft Power Platform. You create a solution with components. You deploy the solution in the production environment. Users report issues with a process. You open the last imported…
The correct answer is D. History. The Solution History view records all import operations and their outcomes, making it the correct place to investigate issues after a solution deployment.
Question
Options
- ASolution dependencies
- BSolution classic view
- CSolution status overview
- DHistory
How the community answered
(35 responses)- A9% (3)
- B14% (5)
- C6% (2)
- D71% (25)
Why each option
The Solution History view records all import operations and their outcomes, making it the correct place to investigate issues after a solution deployment.
Solution dependencies show which other components or solutions the current solution relies on, not the runtime or import errors that caused the reported issue.
Classic view is an alternative UI rendering mode for the solution components list and provides no troubleshooting or diagnostic information.
There is no standard Solution status overview feature in Power Platform that provides troubleshooting details for a recently imported solution.
Solution History in the Power Platform maker portal displays a log of all solution import and export operations, including timestamps, status codes, and error details. This allows makers to review exactly what occurred during the last import and identify failures or warnings that may have caused the reported process issue. It is the primary diagnostic tool for post-deployment solution troubleshooting.
Concept tested: Troubleshooting solution import history in Power Platform
Source: https://learn.microsoft.com/en-us/power-platform/alm/solution-history
Topics
Community Discussion
No community discussion yet for this question.