PL-600 Microsoft Power Platform Solution Architect Questions and Answers

Scenario: Ensure that employees can sign in to all Microsoft apps by using one set of credentials per employee.

Synchronized identity. Synchronize on-premises directory objects with Microsoft 365 and manage your users on-premises. You can also synchronize passwords so that the users have the same password on-premises and in the cloud, but they will have to sign in again to use Microsoft 365.

Box 1: Create and embed a Power Bi radial gauge

A radial gauge chart has a circular arc and shows a single value that measures progress toward a goal or a Key Performance Indicator (KPI). The line (or needle) represents the goal or target value. The shading represents the progress toward that goal. The value inside the arc represents the progress value. Power BI spreads all possible values evenly along the arc, from the minimum (left-most value) to the maximum (right-most value).

In this example, you're a car retailer tracking the sales team's average sales per month. The needle represents a 140 cars sales goal. The minimum possible average sales is 0 and the maximum is 200. The blue shading shows that the team is averaging approximately 120 sales this month.

Box 2: Add an inspection order to the work order form

You can add inspections to work orders in Dynamics 365 Field Service.

Field Service inspections are digital forms that technicians use to quickly and easily answer a list of questions as part of a work order. The list of questions can include safety protocols, pass-and-fail tests for a customer asset, an interview with a customer, or other audits and assessments performed before, during, or after a work order.

Example:

Box 1: Create a lookup to Dynamics 365 Field Service

Scenario: Machines are assigned serial numbers and placed in stock until they are shipped to customers.

Entity lookup: Allows technicians to choose a Dynamics 365 record. In the inspection designer interface, admins must select an entity and a field to display. For a chosen entity, the Name field and mandatory fields are the entity attributes that can be displayed in the lookup.

Box 2: Create a one-to-many relationship and set the behavior to Parental

Scenario: Inspection orders must:

Allow entry of quality ratings of passed or failed for each quality metric identified for the machine being rated.

Be automatically marked as failed if one inspection step rating is marked as failed.

Each inspection order can have one or many inspection steps, and each inspection step has a rating.

Note: Each pair of tables that are eligible to have a 1:N relationship can have multiple 1:N relationships between them. Yet usually only one of those relationships can be considered a parental table relationship.

Box 1: Field controls

You must standardize the format used by agents to enter customer phone numbers.

Box 2: Workflow

Log issues as cases. The case form must show variable sections based on the case type.

Box 1: Schedule board

The Dynamics 365 Field Service schedule board provides an overview of resource availability and bookings you can make.

Box 2: Azure IoT Central connector

Information about each machine produced must be transferred to Dynamics 365 Field Service.

The difference between IoT hub and IoT central is that IoT is an application platform that simplifies the creation of Internet of Things solutions. IoT central helps to reduce the challenges of implementing IoT development, operations, and management. IoT Central is a fully managed Software as a Service solution.

Note: There are three ways you can use to connect IoT-enabled devices into the Field Service solution:

Connected Field Service for Azure IoT Central

Connected Field Service for Azure IoT Hub

Connected Field Service for non-Azure IoT providers using the extensible IoT provider framework

Scenario: Information about each machine produced must be transferred to Dynamics 365 Field Service.

Use the Microsoft Dataverse connector when connecting to the Microsoft Dataverse used for Microsoft Dynamics 365 Sales, Microsoft Dynamics 365 Customer Service, Microsoft Dynamics 365 Field Service, Microsoft Dynamics 365 Marketing, and Microsoft Dynamics 365 Project Service Automation.

Business rule can create business recommendations based on business intelligence.

Scenario: Analytics and reporting

The solution must:

Provide metrics including existing and upcoming demand by inspection station, average time spent per user at a station, and average time a machine spends at each inspection point.

Provide metrics per inspector including number of inspections performed by month, and number of inspections per rating type (pass, fail).

Provide a printed quality certificate to be included with each machine.

Box 1: Schedule board

Note: The Dynamics 365 Field Service schedule board provides an overview of resource availability and bookings you can make.

When you’re looking at the schedule board for the current day, you’ll see a blue line that indicates the current time of day. You can also see a picture of all the resources listed on the schedule board. To quickly view contact information for a resource, hover over their name to view the contact card.

Box 2: Azure IoT Central connector

Azure IoT Central makes it easy to connect, monitor, and manage your IoT devices at scale. With the IoT Central V3 connector, you can trigger workflows when a rule has fired, and take actions by executing commands, updating properties, getting telemetry from devices, and more. Use this connector with your Azure IoT Central V3 application.

This connector is available in the following products and regions:

Scenario: Standardized checklists must be stored in the solution for use by inspectors. A copy must be created when a new inspection is initiated.

Dataverse for Teams – built on Microsoft Dataverse – provides relational data storage, rich data types, enterprise-grade governance, and one-click solution deployment to the Microsoft Teams app store.

Dataverse for teams table creation has all of the things that are great about Microsoft Lists, without the major downsides.

Box 1: Power Automate flow

Scenario: Inspection orders must be automatically marked for re-inspection should a machine fail inspection. The new inspection order must be created by using the originating inspection order as a template.

Box 2: Business rule

By combining conditions and actions, you can do any of the following with business rules:

Set column values

Clear column values

Set column requirement levels

Show or hide columns

Enable or disable columns

Validate data and show error messages

Create business recommendations based on business intelligence.

Non-functional requirements capture the elements that users might not directly care about but are important to support the proposed architecture and operational viability of the solution. Non-functional requirements often influence user adoption and perceived satisfaction with the solution.

Examples of common non-functional requirement types include:

Availability

Compliance/regulatory

Data retention/residency

Performance (response time, and so on)

Privacy

Recovery time

Security

Scalability

Import data that's stored somewhere else into your model-drvien app using the import feature in Power Apps.

Every table has required columns that must exist in your input file. It's recommended that you download an

Excel template, add your data, and then import the file to your app. The template saves time and effort. Don't

add or modify columns in the template to avoid issues during the import.

Note:

Step 1: Download an Excel template

To avoid mapping issue, it's recommended that you use an Excel template that you can download from your

app. Once the template is downloaded add your data and then import the file back to your app. Remember

don't add or modify columns in the template to avoid issues during the import process.

Step 2: Import your data

Use the template that you downloaded in the previous step (modified with your data) and import the file to your app.

Box 1: Assign: Cascade None

Scenario: Worker still records must be archived after ten years and are then removed from the main system.

Assign: The referenced table record owner is changed.

Cascade None: Do nothing.

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.

Scenario: The testing team reports that one of the canvas apps is not working as expected. An error message displays as specific pages load.

A: The App checker is now available to help provide a clear list of formula issues in your app, and to provide items to fix to make your app accessible. The App checker is an area that the PowerApps team will continue to invest in, and build on in order help to make debugging, performance and best practice decisions an easier and more guided experience.

C: With the solution checker feature, you can perform a rich static analysis check on your solutions against a set of best practice rules and quickly identify these problematic patterns. After the check completes, you receive a detailed report that lists the issues identified, the components and code affected, and links to documentation that describes how to resolve each issue.

Office 365 Users lets you access user profiles in your organization using your Office 365 account. You can use the Use the connection in your Power Platform app.

Dataverse is part of the Microsoft 365 collaboration and productivity tools. Using federation, applications can connect to Dataverse using the same system user identities and credentials available in an Azure Active Directory based network.

Scenario:

Users must be active employees of Fabrikam.

Quality inspection app: Fabrikam is evaluating Microsoft Power Platform to determine whether it can meet the company’s requirements for a manufacturing defect and quality inspection solution. Each machine produced must be subjected to a quality inspection at various points during production. Each machine must undergo a more extensive quality inspection before the machine can be shipped to the customer.

Box 1: Power Automate

Self-service purchase is available for Power Platform (Power BI, Power Apps, and Power Automate), Project, and Visio.

Box 2: Azure Active Directory B2B

Scenario: First Up Consulting recruits information technology (IT) workers for temporary or permanent positions at client companies.

Azure Active Directory (Azure AD) business-to-business (B2B) collaboration is a feature within External Identities that lets you invite guest users to collaborate with your organization. With B2B collaboration, you can securely share your company's applications and services with guest users from any other organization, while maintaining control over your own corporate data. Work safely and securely with external partners, large or small, even if they don't have Azure AD or an IT department. A simple invitation and redemption process lets partners use their own credentials to access your company's resources.

Note, Scenario:

Workers must be able to sign into a portal by using their own email address. Workers must be required to use a secure method of authentication to be able to view their data.

User security roles must be customized to ensure that users are able to interact only with the specific data in which they need access.

Box 3: Dynamics 365 Field Service

Dynamics 365 Field Service functionality include:

An interactive schedule board helps dispatchers assign work orders to the best resources based on location, availability, skill set, priority, and more. This is done via a manual drag-and-drop method, a semi-automated scheduling assistant, or fully automated with Resource Scheduling Optimization.

The schedule board displays each resource--whether an employee, contractor, or equipment--and their scheduled work orders. Resources and their assigned jobs are also displayed on a map along with routes and traffic patterns in real time.

Box 1: Microsoft Teams

First up employees must be able to contact each other by using a secure system to ask and answer questions about medical cases.

Microsoft Teams key capabilities:

Connected

Secure

Managed

Collaborative and productive

Box 2: Microsoft 365 Business Voice

Workers must be able to communicate in near real-time with worker support agents.

Microsoft 365 Business Voice makes it easy for small and medium organizations to turn Microsoft Teams into a powerful and flexible telephone system. It's a replacement for traditional telephony providers and in-house phone systems that can be difficult and costly to manage.

Scenario:

Audit teams must have the ability to view worker information on their mobile devices.

Audit teams must be able to record data during visits to locations where workers are placed.

When you create an app, or someone shares an app with you, you can run that app on the Power Apps mobile app or in a web browser.

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.

Scenario:

The reporting and analytics team must be able to create reports that include data from all facilities and all workers.

Management reports must present an overview of the entire organization. Other reports may be limited to specific offices.

B: Power Apps apps can include reports that provide useful business information to the user. These reports are based on SQL Server Reporting Services and provide the same set of features that are available for typical SQL Server Reporting Services reports.

C: Microsoft Dynamics 365 online and Model-Driven PowerApps offers several advanced reporting options. Advanced reports are often necessary when business requirements demand complex calculations, returning multiple data sets, grouping large sets of data based on rules, and retrieving data from different data sources.

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.

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.