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: Disable duplicate detection

Duplicate detection has rules for sending emails.

Box 2: Disable all workflows, plug-ins, and Power Platform admin center

Box 3: Disable auditing

Auditing affects the size of the log file.

Scenario: Agents need a way to track reservation issues.

Use Dynamics 365 Customer Service to:

Track customer issues through cases

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: Microsoft Teams

Maintenance supervisors must not have access to Dynamics 365 Customer Service. The supervisors must be able to communicate with the contracts team about contracts.

Box 2: Dynamics 365 Workspace

Aircraft maintenance vendors must have only view and upload privileges to their invoices and receipts.

The Expense management mobile workspace lets users capture and upload a receipt, so that they can attach it to an expense report later.

Scenario: The security rule for agents must contain the privileges in the default Customer Service

Representative security role.

Create a security role by Copy Role:

Step 1 (E): Copy the Customer Service Representative role.

Step 2 (F): Select the New Role Name.

Step 3: (B): When Copying Role is complete, navigate to each tab, ie Core Records, Business Management, Customization, etc.

Set the privileges on each tab.

Box 1: Yes

This can be done with Dataverse flows: The When a row is added, modified or deleted trigger runs a flow whenever a row of a selected table and scope changes or is created.

Box 2: Yes

AI Builder is a Microsoft Power Platform capability that provides AI models that are designed to optimize your business processes. AI Builder enables your business to use AI to automate processes and glean insights from your data in Power Apps and Power Automate.

Dataverse includes a web application tool called Import Data Wizard. You use this tool to import data records from one or more comma-separated values (.csv), XML Spreadsheet 2003 (.xml), or text files.

Use transformation mapping to modify data before importing it. For example, split a full name that is contained

in the source file into a first name and a last name to match the target columns for a table.

Note:

To implement data import, you typically do the following:

Create a comma-separated values (CSV), XML Spreadsheet 2003 (XMLSS), or text source file.

Create a data map or use an existing data map.

Create a comma-separated values (CSV), XML Spreadsheet 2003 (XMLSS), or text source file.

Create a data map or use an existing data map.

Associate an import file with a data map.

Upload the content from a source file to the associated import file.

Parse the import file.

Transform the parsed data.

Upload the transformed data into the target Dataverse server.

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.

Field-level security is managed by the security profiles. To implement field-level security, a system administrator performs the following tasks.

Enable field security on one or more fields for a given entity.

Associate one more existing security profiles, or create one or more new security profiles to grant the appropriate access to specific users or teams.

Controls that require extra data beyond the primary record produce the most strain on form responsiveness and loading speed. These controls fetch data over the network and often involve a waiting period (seen as progress indicators) because it can take time to transmit the data.

Keep only the most frequently used of these controls on the default tab.

Box 1: Security role

Microsoft Dataverse uses a role-based security model to help secure access to the database.

Scenario:

You must prevent users from changing inspection order data once an inspection is marked as final.

Supervisors must be able to modify standard checklists. Other employees must be prevented from modifying checklists.

Box 2: Data flow

Dataflows are a self-service, cloud-based, data preparation technology. Dataflows enable customers to ingest, transform, and load data into Microsoft Dataverse environments, Power BI workspaces, or your organization's Azure Data Lake Storage account.

Scenario: Provide a visual representation of the testing measurement limits for each step. Include an indication of how the measured value compares to measurement limits and whether the measurement is within tolerance. Users must be able to configure the visualizations to display the minimum value and maximum value, and whether the reading is within the tolerance of a single targeted value. It must also be able to be used for maintenance inspections once the machine has been installed.

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:

To control data access, you must set up an organizational structure that both protects sensitive data and enables collaboration. You do this by setting up business units, security roles, and field security profiles.

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.

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.

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.

Need to store the image in the table.

Scenario: The company uses photos of employees to generate employee badges. Photos are uploaded into Microsoft 365 user profiles.

Box 1: Field security profile

Record-level permissions are granted at the entity level, but you may have certain fields associated with an entity that contain data that is more sensitive than the other fields. For these situations, you use field-level security to control access to specific fields.

Field-level security is available for the default fields on most out-of-box entities, custom fields, and custom fields on custom entities. Field-level security is managed by the security profiles.

Box 2: Compliancy policy

Compliance policy settings – Tenant-wide settings that are like a built-in compliance policy that every device receives. Compliance policy settings set a baseline for how compliance policy works in your Intune environment, including whether devices that haven’t received any device compliance policies are compliant or noncompliant.

Note: Mobile device management (MDM) solutions like Intune can help protect organizational data by requiring users and devices to meet some requirements. In Intune, this feature is called compliance policies.

Compliance policies in Intune:

Define the rules and settings that users and devices must meet to be compliant.

Include actions that apply to devices that are noncompliant. Actions for noncompliance can alert users to the conditions of noncompliance and safeguard data on noncompliant devices.

Can be combined with Conditional Access, which can then block users and devices that don't meet the rules.

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

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.

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

Microsoft Dynamics 365 Customer Service is a module for customer service automation that streamlines case and knowledge management, enables personalized customer service with a 360-degree customer view, and provides visibility into customer service department performance with dashboards and reports.

Scenario:

Customers can select a meal when they make a reservation and can save the meal choices as a customer preference.

The company offers two types of meals: standard and vegetarian. Meal types can be temporarily unavailable. The airline is considering offering other meal types, such as gluten-free and low-sodium options.

In PowerApps Option set is one of the field types you can use in your Entity. The information type that Option Set stores is a list of text values. And here comes the Option Set advantage – once you define its text values you can centrally managed it.

Example:

Scenario: IT staff needs a mobile solution to see IT cases at the top of the menu since this is their primary focus.

Managers need to see all customer dashboards at the top of their menu on their mobile device.

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.

Use business process flows to define a set of steps for people to follow to take them to a desired outcome.

With business processes flows available as an entity, you can now use advanced finds, views, charts, and dashboards sourced from business process flow data for a given entity, such as a lead or opportunity.

Scenario:

Agents need a solution to replace paper reservation checklists.

Agents need dashboards to show a current count of all reservations on the entity.

Agents need a way to track reservation issues.

Agents need a visual indicator in the interface to determine the reservation step to provide a seamless customer experience.

Scenario: IT specialists want to design Power BI reports. They need to understand the underlying table relationships of the system.

Business process modeler (BPM) in Microsoft Dynamics Lifecycle Services (LCS) is a tool that you can use to create, view, and modify repeatable implementations that are based on business process libraries. BPM helps you align your business processes with industry-standard processes that are described by the American Productivity & Quality Center (APQC)

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