Microsoft Power Platform App Maker Exam (PL-100) - Microsoft

Scenario: The completed app and all supporting components must be provided to Tailwind Traders. Tailwind Traders must not be able to make changes to any of the components. Managed Solution: A managed solution is a finalized solution that can be distributed and installed. They are created by exporting an unmanaged solution by setting restrictions to prevent any further customizations. The whole point of Managed is locking down the Component states so they cannot be edited. Deleting the Managed Solution will remove all its customisations as well as data contained. Managed Solutions become read only once deployed so they cannot be manipulated.<br />
<br />
Reference: https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/Managed-vs-Unmanaged/td- p/495685

<img src="https://examsqa.com/storage/question-images/microsoft-power-platform-app-maker-exam-pl-100_page_6_Im5.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
Box 1: App Checker Scenario: Several sales representatives have accessibility restrictions. User2 is visually impaired and cannot see images. User3 is unable to use a mouse. Users who have vision, hearing, or other impairments can use your canvas app more easily and successfully if you consider accessibility as you design how the app looks and behaves. If you're not sure how to make your app more accessible, you can run the AppChecker Accessibility checker in Power Apps Studio. Box 2: Solution Checker Scenario: Before deploying the app to production, you must ensure that the app conforms to Microsoft accessibility and performance guidelines. Use solution checker to validate your model-driven apps in Power Apps.<br />
<br />
Reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/accessibility-checker https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/use-powerapps-checker

<img src="https://examsqa.com/storage/question-images/microsoft-power-platform-app-maker-exam-pl-100_page_8_Im7.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
Box 1: Fill Scenario: You must display a visual indicator in the app so that sales representatives know whether the app is offline before submitting reports. Fill – The background color of a control.<br />
<br />
Incorrect Answers: DisplayMode - The mode to use for data cards and controls within the form control. Box 2: SubmitForm Scenario: When data is submitted offline, the data must be stored in the app until the app is back online. Use the SubmitForm function in the OnSelect property of a Button control to save any changes in a Form control to the data source.<br />
<br />
Reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/controls/control-screen https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/functions/function-form

<img src="https://examsqa.com/storage/question-images/microsoft-power-platform-app-maker-exam-pl-100_page_10_Im9.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
Box 1: 1.0.0.0 When identifying versions of the app solution, all dependencies, entities, and user interfaces components must be identified to avoid any unintentional issues caused by reverting individual components to a previous version. A solution’s version has the following format: major.minor.build.revision. An update must have a higher major, minor, build or revision number than the parent solution. For example, for a base solution version 3.1.5.7, a small update could be a version 3.1.5.8 or a slightly more signficant update could have version 3.1.7.0. A substantially more significant update could be version 3.2.0.0. Box 2: 20.11.1.1<br />
<br />
Scenario:<br />
<br />
You must use the following version control numbering scheme:<br />
<br />
- Major: The last two digits of the year the app is packaged<br />
<br />
- Minor: Two digits that represent the month when the app is packaged<br />
<br />
- Build: A number that is incremented to represent significant changes to the app<br />
<br />
- Revision: The incremented revision for a package<br />
New versions of the application must completely replace previous versions of the app.<br />
<br />
Reference: https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/update-solutions

<img src="https://examsqa.com/storage/question-images/microsoft-power-platform-app-maker-exam-pl-100_page_12_Im11.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
Box 1: View the sessions details page for the app in Power Apps Studio Use PowerApps Studio, select the App, and choose and you will be directed to the app’s Versions tab in PowerApps portal. There should be one version marked Live.<br />
<br />
<img src="https://examsqa.com/storage/question-images/microsoft-power-platform-app-maker-exam-pl-100_page_12_Im12.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
Box 2: Select Restore on the previous version of the app. Restore an app from your account Open powerapps.com, and then click or tap Apps in the left navigation bar. Near the right edge, click or tap the info icon for the app that you want to restore. Click or tap the Versions tab, and then click or tap Restore for the version that you want to restore.<br />
<br />
<img src="https://examsqa.com/storage/question-images/microsoft-power-platform-app-maker-exam-pl-100_page_13_Im13.jpg" alt="Exhibit" style="max-width: 100%; height: auto;" /><br />
<br />
Reference: https://powerapps.microsoft.com/sk-sk/blog/saveandpublish/ https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/restore-an-app