PL-600 Microsoft Exam Lab Questions

Box 1: Add users to Microsoft 365.

Scenario: Users cannot view Power BI reports within the Power Platform apps.

Issue: The people you share with may see a locked tile in a dashboard, or a "Permission required" message when they try to view a report.

Solution: You need to grant them permission to the underlying dataset.

Go to the All or the Datasets + dataflows tab in your content list.

Select More options (...) next to a dataset, then select Manage permissions.

Select Add user.

Enter the full email addresses for individuals, distribution groups, or security groups.

Select Grant access.

Box 2: Configure an on-premises data gateway.

Scenario: The company plans to reference historical data in the [on-premises] existing system. The records held in these systems will not be migrated to the new solution except for medication information.

The on-premises data gateway acts as a bridge to provide quick and secure data transfer between on-premises data (data that isn't in the cloud) and several Microsoft cloud services. These cloud services include Power BI, PowerApps, 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.

Box 1: Virtual Table

A virtual table is a custom table in Microsoft Dataverse that has columns containing data from an external data source. Virtual tables appear in your app to users as regular table rows, but contain data that is sourced from an external database, such as an Azure SQL Database. Rows based on virtual tables are available in all clients including custom clients developed using the Dataverse web services.

Scenario:

First Up uses an on-premises system to manage current and historical patient data including medications and medical visits.

The company plans to reference historical data in the existing system. The records held in these systems will not be migrated to the new solution except for medication information.

The solution must provide a worker appointment booking system that can access worker historical job placement data.

First Up staff members must be able to view and update worker records. They must be able to see current and historical job placement data on the same form in the new solution.

Box 2: Lookup (N:1)

Each worker can have many security clearances, so need a 1:N relationship.

Scenario: The solution must support tracking of security clearance information for a worker including the date, status, and certifying agency.

Box 1: Power Platform Local Business Owner Team

Owner team: An owner team owns records and has security roles assigned to the team. A user's privileges can come from their individual security roles, those of the teams that they're part of or the ones they inherit. A team has full access rights on the records that the team owns. Team members are added manually to the owner team.

Scenario: Employee authentication with the existing system is provided by an on-premises Active Directory instance that is linked to Azure Active Directory.

Box 2: Azure Active Directory Security Group Team

An Azure Active Directory (Azure AD) group team. Similar to owner team, an Azure AD group team can own records and can have security roles assigned to the team.

Note: The administration of app and data access for Microsoft Dataverse has been extended to allow administrators to use their organization's Azure Active Directory (Azure AD) groups to manage access rights for licensed Dataverse users.

Box 3: Azure Active Directory B2B Guest Access

An Azure AD B2B collaboration user is an external user, typically from a partner organization, that you invite to sign into your Azure AD organization using their own credentials. This B2B collaboration user (also generally referred to as a guest user) can then access the apps and resources you want to share with them. A user object is created for the B2B collaboration user in the same directory as your employees. B2B collaboration user objects have limited privileges in your directory by default, and they can be managed like employees, added to groups, and so on.

Scenario: Before First Up signs a contract to place workers at a client company, a member of the audit team visits the company and interviews company management. Audit members use different types of devices including Android and iOS devices. First Up has no plans to require the use of a single type of device.

A virtual table is a custom table in Microsoft Dataverse that has columns containing data from an external data source. Virtual tables appear in your app to users as regular table rows, but contain data that is sourced from an external database, such as an Azure SQL Database. Rows based on virtual tables are available in all clients including custom clients developed using the Dataverse web services.

Scenario:

First Up uses an on-premises system to manage current and historical patient data including medications and medical visits.

The company plans to reference historical data in the existing system. The records held in these systems will not be migrated to the new solution except for medication information.

The solution must provide a worker appointment booking system that can access worker historical job placement data.

First Up staff members must be able to view and update worker records. They must be able to see current and historical job placement data on the same form in the new solution.