PL-100 Online Practice Questions and Answers

Correct Answer:

Box 1: Choice

Students select one main cuisine to specialize in when applying for enrollment.

A choice (picklist) is a type of column that can be included in a table. It defines a set of options. When a choice is displayed in a form it uses a drop-down list control. When displayed in Advanced Find it uses a picklist control. Sometimes

choices are called picklists by developers.

You can define a choice to use a set of options defined within itself (locally) or it can use a set of options defined elsewhere (globally) which can be used by other choice columns.

Global choices are useful when you have a standard set of categories that can apply to more than one column. Maintaining two separate choices with the same values is difficult and if they are not synchronized you can see errors, especially if

you are mapping table columns in a one-to-many table relationship.

Note: If you define every choice as a global choice your list of global choices will grow and could be difficult to manage. If you know that the set of options will only be used in one place, use a local choice.

Box 2: Global choice

The college generates a QR code for high-volume subscribers to allow staff to vote for their favorite dishes.

Subscribers should be able to mark a dish as favorite directly from their order.

Box 3: Whole number

Dish votes are counted based on the number of people who marked the dish as a favorite.

Reference: https://docs.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-global-option-sets

Correct Answer: A

Manage environment in the Power Platform admin center.

Reference: https://docs.microsoft.com/en-us/power-platform/admin/create-environment

Correct Answer: D

You can view the details of all solution operations including solution import with the solution history feature. To view these operations, select See history on the solutions page.

View the history of a solution

You can view details about solution operations from the Solutions area of Power Apps. An operation can be a solution import, export, or uninstall. The solution history displays information such as solution version, solution publisher, type of

operation, operation start and end time, and operation status.

View solution operation error details

Below the Details area is the More details area that has additional information about the solution and, when a solution operation has a failure, the information includes:

The Error code of the error returned from the operation.

The Exception message, which can help diagnose the underlying cause for the operation failure. Some errors, including solution dependency errors, may also include links to solution layers to make it easier for you to diagnose the issue.

The Activity Id can be useful in cases where you need to contact Microsoft Customer Support.

Incorrect:

* Solution dependencies Solution components often depend on other solution components. You can't delete any solution component that has dependencies on another solution component. For example, a customized ribbon typically requires image or script web resources to display icons and perform actions using scripts. As long as the customized ribbon is in the solution, the specific web resources it uses are required. Before you can delete the web resources you must remove references to them in the customized ribbon. These solution component dependencies can be viewed in the application by clicking Show Dependencies.

As a result of dependency tracking the following behaviors are enforced:

Deletion of a component is prevented if another component in the system depends on it.

Export of a solution warns the user if there are any missing components that could cause failure when importing that solution in another system.

Warnings during export can be ignored if the solution developer intends that the solution is only to be installed in an organization where dependent components are expected to exist. For example, when you create a solution that is designed

to be installed over a pre-installed "base" solution.

Import of a solution fails if all required components aren't included in the solution and also don't exist in the target system.

Additionally, when you import a managed solution all required components must match the package type of the solution. A component in a managed solution can only depend on another managed component.

Reference: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/solution-history

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/import-update-export-solutions https://learn.microsoft.com/en-us/power-platform/alm/dependency-tracking-solution-components

Correct Answer: CD

The quick view must be based on the Customer table, which has the required column Best Time.

Note: A main form that displays the details of a row can use a quick view component to display read-only details of a related row (lookup). The data displayed by the quick view component is defined by the quick view form of the related table.

When there is no related row, such as a lookup, the quick view component is automatically hidden.

Reference: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/form-designer-add-configure-quickview

Correct Answer: CD

C: You can create a table in Dataverse and fill that table with data from an OData feed by using Power Query. You can use the same techniques to integrate data from these online and on-premises sources, among others:

1.

SQL Server

2.

Salesforce

3.

IBM DB2

4.

Access

5.

Excel

6.

Web APIs

7.

OData feeds

8.

Text files

D: You can create a new Dataverse table that stores all the metadata from the dataflow run. For every refresh of a dataflow, a record is added to this table. You can also store metadata for multiple dataflow runs in the same table.

Reference: https://docs.microsoft.com/en-us/power-query/dataflows/load-dataflow-metadata-into-dataverse-table https://docs.microsoft.com/en-us/power-query/dataflows/add-data-power-query

Correct Answer: C

Reference: https://powerapps.microsoft.com/en-us/blog/introducing-simplified-ai-builder-experience-in-power-automate/

Correct Answer: B

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.

Reference: https://powerusers.microsoft.com/t5/Power-Apps-Pro-Dev-ISV/Managed-vs-Unmanaged/td-p/495685

Correct Answer: C

There are two designers you can use to create and edit 1:N (one-to-many) or N:1 (many-to-one) relationships:

1.

You can create and edit 1:N (one-to-many) or N:1 (many-to-one) entity relationships in Power Apps portal

2.

You can create and edit create and edit 1:N (one-to-many) or N:1 (many-to-one) entity relationships using solution explorer

Reference: https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/create-edit-1n-relationships

Correct Answer: B

Reference: https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/reference-properties

Correct Answer: A

Suppose you want your report readers to be able to look at overall sales metrics, but also highlight performance for individual district managers and different time frames. You could create separate reports or comparative charts. You could

add filters in the Filters pane. Or you could use slicers. Slicers are another way of filtering. They're displayed on the report page, and narrow the portion of the dataset that's shown in the other report visualizations.

When to use a slicer

Slicers are a great choice when you want to:

Display commonly used or important filters on the report canvas for easier access.

Make it easier to see the current filtered state without having to open a drop-down list.

Filter by columns that are unneeded and hidden in the data tables.

Create more focused reports by putting slicers next to important visuals.

Reference:

https://learn.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-slicers