PL-100 Microsoft Power Platform App Maker Question and Answers

Graphical user interface, text, application Description automatically generated

Box 1: Business process flow

A business process flow is a visual guide meant to help users complete a business process by using a set of predefined stages. Users are not limited on how long they run a business process or how long they have a stage open.

Box 2: Business rule

Box 3: Power Automate

A Power Automate flow does not have any visual components like a business process flow. Power Automate flows can be configured to work with many different data sources, and a flow can connect to many different data sources within the same flow. A flow can be configured to time out if it is not completed in a certain time and can be triggered to move between steps based on data or user interaction.

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.

Graphical user interface, text, application Description automatically generated

Box 1: Power Apps mobile app

Scenario:

User1 often works in a warehouse that does not have internet connectivity.

User1 needs to edit an existing status report and submit a new status report.

The app must be able to run both online and offline. If the mobile device on which the app runs is connected to the internet, the app must immediately submit the status report.

You can build offline capabilities in your PowerApps app so your app users can access some data or save some data even when they don't have an internet connection.

Box 2: Connector

Scenario: Azure SQL Database is used to store other data

Use the SQL Server connector to connect to SQL Server, in either Azure or an on-premises database, so that you can manage your data with create, read, update, and delete operations.

Scenario: 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.

Power Apps has added components to the rule set that encourages best practices in the Power Apps Checker. You can check your canvas apps and flows that are included in solutions and then review all issues in a single, consolidated report.

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.

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.

Graphical user interface, text, application Description automatically generated

Box 1: AccessibleLabel

Scenario: Before deploying the app to production, you must ensure that the app conforms to Microsoft accessibility and performance guidelines.

User2 is visually impaired and cannot see images.

AccessibleLabel is a label for screen readers.

An empty value for Image, Icon, and Shape controls will hide the controls from screen reader users.

Box 2: TabIndex

User3 is unable to use a mouse.

TabIndex determines if the control participates in keyboard navigation.

Keyboard navigation is an important aspect of any app. For many, the keyboard is more efficient than using touch or a mouse. The navigation order should:

Mirror what is seen visually.

Only have a tab stop at controls that are interactive.

Follow either an intuitive across and then down "Z" order or a down and then across "reverse-N" order.

Graphical user interface, text, application, email Description automatically generated

Box 1: Business Process

Scenario: If a sales representative submits a status report and assigns the At Risk status to a process, the app must prompt the sales representative to enter a detailed description for the risk. This information must be emailed to the regional manager.

Business process flows provide a guide for people to get work done. They provide a streamlined user experience that leads people through the processes their organization has defined for interactions that need to be advanced to a conclusion of some kind. This user experience can be tailored so that people with different security roles can have an experience that best suits the work they do.

Box 2: Common Data Service when a record is created

The Microsoft Dataverse (Common Data Service) connector provides the following triggers to help you define when your flows start:

When a row is created, updated, or deleted

When an action is performed

When a flow step is run from a business process flow

An accessible canvas app will allow users with vision, hearing, and other impairments to successfully use the app. In addition to being a requirement for many governments and organizations, following the below guidelines increases usability for all users, regardless of their abilities.

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.

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.

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.

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

Scenario:

You must use the following version control numbering scheme:

- Major: The last two digits of the year the app is packaged

- Minor: Two digits that represent the month when the app is packaged

- Build: A number that is incremented to represent significant changes to the app

- Revision: The incremented revision for a package

New versions of the application must completely replace previous versions of the app.

Scenario: The app must be able to run both online and offline. If the mobile device on which the app runs is connected to the internet, the app must immediately submit the status report.

When data is submitted offline, the data must be stored in the app until the app is back online.

Mobile users often need to be productive even when they have limited or no connectivity.

LoadData and SaveData combine to form a simple mechanism to store small amounts of data on a local device. By using these functions, you can add simple offline capabilities to your app.

The SaveData function stores a collection for later use under a name.

The LoadData function reloads a collection by name that was previously saved with SaveData. You can't use this function to load a collection from another source.

Salespeople often do not set status of RFQs in the Sales Log to Won when a sale is closed and the customer purchase order is received.

Include a dashboard that shows all currently active quotes, their status in the sales cycle, the probability of closing, and estimated manufacturing and installation dates, by customer, product division, status, and salesperson.

QUSTION NO: 9 HOTSPOT

You need to identify which business logic options to implement.

Which options should you choose? To answer, select the appropriate options in the answer area.

NOTE: Each correct selection is worth one point.

C:\Users\Waqas Shahid\Desktop\Mudassir\Untitled.jpg

Answer:

QUSTION NO: 10

You need to ensure that the salespeople can save measurements. What should you do?

A. Publish the app with a new version number.

B. Update the security role assigned to the app to include missing permissions on the quote table.

C. Update the security role assigned to the app to include missing permissions on the custom table.

Answer: C

Scenario: The operations manager asks that the time tracking app display the employee’s photo once they have scanned their badge.

Image control in Power Apps is a control that shows an image from, for example, a local file or a data source.

Box 1: Timer

A Timer control in Power Apps is a control that can determine how your app responds after a certain amount of time passes.

Box 2: Barcode scanner

The Barcode scanner control for canvas apps scans barcodes, QR codes, and data-matrix codes on an Android or iOS device.

Box 3: Image

Image control in Power Apps is a control that shows an image from, for example, a local file or a data source.

If you add one or more Image controls to your app, you can show individual images that aren't part of a data set, or you can incorporate images from records in data sources.

Scenario: Users report that the customer request number is difficult to interpret. They request that you change the number to a system generated sequential number.

Autonumber columns are columns that automatically generate alphanumeric strings whenever they are created.

Scenario: The Job Setup entity must store its data in the existing on-premises SQL Server instance.

The on-premises data gateway acts as a bridge to provide quick and secure data transfer between onpremises data (data that isn't in the cloud) and several Microsoft cloud services. These cloud services include Power BI, Power Apps, Power Automate, Azure Analysis Services, and Azure Logic Apps. By using a gateway, organizations can keep databases and other data sources on their on-premises networks, yet securely use that on-premises data in cloud services.

Scenario: Requests for quotes are currently stored in a Sales Log workbook. The workbook includes the following information:

Status of the Request for Quote (RFQ) with the values of Won, Lost, No Bid, and Cancelled

Salespeople often do not set status of RFQs in the Sales Log to Won when a sale is closed and the customer purchase order is received.

You can create business rules and recommendations to apply logic and validations without writing code or creating plug-ins. Business rules provide a simple interface to implement and maintain fast-changing and commonly used rules.

Business rules defined for an entity apply to both canvas apps and model-driven apps if the entity is used in the app.

Box 1: 1:N

Scenario: A sortable listing of all in-process jobs from the Job Setup table, by customer, start date, and product.

Box 2: User or Team owned

Scenario: Employees must only be able to access their own time tracking records from the app.

User or team: Data belongs to a user or a team. Actions that can be performed on these records can be controlled on a user level.

Box 1: PowerBI Desktop

The Sales dashboard must reside in the Sales channel and must include information about active quotes, sales pipeline, and year-to-date sales KPIs for sales quotas by region.

PowerBI Desktop to support many data source.

Box 2: PowerBI Desktop or Power BI Service on

A dashboard that shows a capacity Heat map by month as well as expected sales that are likely to close for the next month.

Both support visualizations.

Scenario: Automatically perform the following actions immediately when a sale is won:

Generate a sequential job number.

Copy key sales information to the Job Setup entity used by manufacturing.

Scenario Issue: Users want to be able to see their weekly total time entered from all screens.

A component library provides a centralized and managed repository of components for reusability.

Graphical user interface, text, application, email Description automatically generated

Box 1: Security role

Scenario: Employees must only be able to access their own time tracking records from the app.

Testers report that they can see time entries in the Time Tracker app, not just their own.

Box 2: Field-level security

Scenario: Employees must only be able to modify time records for the current and previous day.

Testers report that they can edit any existing time entries.

Box 3: Hierarchical security

You use field security tables to apply field-level security, which restricts field access to specified users and teams.

Graphical user interface, application Description automatically generated

Box 1: Use a Business Process flow

Scenario: The Sales Log app must enforce process standards related to the completion of estimates and supporting materials needed during the sales lifecycle.

Box 2: Use a formula to set the DisplayMode property

DisplayMode - The mode to use for data cards and controls within the form control.

Derived from the Mode property based and cannot be set independently:

Graphical user interface, text, application, email Description automatically generated

Graphical user interface, text, application, email Description automatically generated

Box 1: Model-driven app

The Sales app must meet the following requirements:

Provide a central location for all sales pipeline and quote information that is easily accessible and maintains all of the versions of the estimate, quote, and engineering documents.

Compared to canvas apps, model-driven apps in PowerApps are based on underlying data — specifically, the data stored in Common Data Service (CDS).

Box 2: Power BI Desktop

You can create a KPI in Power BI Desktop.

Open your report editor in Power BI Desktop then select a report on which you are working.

On your right, you will see a Visualizations pane and a Fields pane.

From the Visualizations pane, select the KPI visual.

Etc.

Box 3: Power Automate