Microsoft PL-100 Exam Dumps

ununmanaged solution that includes all customizations

Unmanaged Solution: The beginning state of solution is the unmanaged solution state. During this phase, you
can add, edit, update, remove, delete, and test any of the components of the solution.
Reference:
https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/Managed-vs-Unmanaged/td-p/495685

Accessibility

The Accessibility checker classifies each issue as an error, a warning, or a tip based the issue's severity.
Issues include:
Focus isn't showing
When the FocusBorderThickness of a control is set to 0. It is good practice to ensure a proper color-contrast
ratio between the focus border and the control itself so it's clearly visible.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/accessibility-checker

pie

column

line

You can use line charts, pie charts, and bar charts to display your data in a canvas app.
Add a bar chart to display your data:
1. On the Home tab, add a screen.
2. On the Insert tab, select Charts, and then select Column Chart.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/use-line-pie-bar-chart

The default solution cannot be exported and distributed to another environment

Default Solution. This is a special solution that contains all components in the system. The default solution is
useful for discovering all the components and configurations in your system.
Why you shouldn't use the default solutions to manage customizations
There are a few reasons why you shouldn't create apps and make customizations in either of the default
solutions:
The default solution can't be exported; therefore, you can't distribute the default solution to another
environment.
The default solution contains all components and customizations from all solutions in the environment.
By default, all enabled users can create apps and customize components in the Common Data Services Default
Solution.
It's difficult to locate or identify the customizations you've made in the environment by using either default
solution.
When you use either default solution to create components, you'll also use the default publisher assigned to the
solution. This often results in the wrong publisher prefix being applied to some components.
Reference:
https://docs.microsoft.com/en-us/power-platform/alm/use-solutions-for-your-customizations