Free Microsoft PL-100 Practice Exam with Questions & Answers

Instead use a calculated field.

Need to calculate the exchange rate in USD.

Calculated columns are calculated in real-time when they are retrieved.

Graphical user interface, application Description automatically generated

Box 1: Power BI Desktop

You can define roles and rules within Power BI Desktop. When you publish to Power BI, it also publishes the role definitions.

To define security roles, follow these steps.

Import data into your Power BI Desktop report, or configure a DirectQuery connection.

From the Modeling tab, select Manage Roles.

From the Manage roles window, select Create.

Etc.

Box 2: Power BI Service

After you save your report in Power BI Report Server, you manage security and add or remove members on the server.

1. In Power BI Desktop, save the report to Power BI Report Server. You need to use the version of Power BI Desktop for Power BI Report Server.

2. In Power BI Report Service, select the ellipsis (…) next to the report.

3. Select Manage > Row-level security.

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

On the Row-level security page, you add members to a role you created in Power BI Desktop.

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.

A: DevOps is the combining of two historically disparate disciplines: software development and IT operations. The primary goal of DevOps is to shorten the software development lifecycle and provide continuous integration and continuous delivery (CI/CD) with high software quality. You can use Power Apps build tools to automate common build and deployment tasks related to Power Apps if your DevOps platform is Azure DevOps.

D: Microsoft AppSource is now embedded in the Dynamics 365 home page and throughout the common navigation. It now includes a private gallery of apps available to you within your company. Select Get more apps from the home page or task pane, and navigate to the My Organization tab to see apps that are available to you.

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.

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