Ultimate Guide to Prepare PL-600 Certification Exam for Microsoft Certified in 2024 [Q89-Q105]

Need a relationship table.
N:N (Many-to-Many): A table relationship that depends on a special Relationship table, sometimes called an
Intersect table, so that many rows of one table can be related to many rows of another table.
When viewing rows of either table in a N:N relationship you can see a list of any rows of the other table that are
related to it.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-entity-relationships

Explanation
Graphical user interface, text, application, chat or text message Description automatically generated

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.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-virtual-entities
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-entity-relationships

Reference:
https://docs.microsoft.com/en-us/dynamics365/common-scheduler/schedule-anything-with-universal-resource-scheduling

Reference:
https://docs.microsoft.com/en-us/learn/modules/work-with-requirements/3-functional-requirements
https://docs.microsoft.com/en-us/learn/modules/work-with-requirements/4-non-functional-requirements

Explanation
Graphical user interface, text, application, chat or text message Description automatically generated

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.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-virtual-entities
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/create-edit-entity-relationships

Reference:
https://docs.microsoft.com/en-us/powerapps/developer/data-platform/field-security-entities

Explanation

Box 1: Microsoft Power Automate, Microsoft Dataverse connector, and Microsoft 365 Outlook connector Use Microsoft Dataverse as the data source.
While Power Automate is a robust tool with ever-expanding capabilities, it also handles simple tasks with grace. A universal business need for many organizations is the ability to automate email notifications based on certain criteria: an opportunity is won, send an email to the sales manager; a case is closed, send an email to the customer; a work order is completed, send an email to the customer.
Power Automate can easily accommodate this using the Microsoft 365 Outlook connector.
Box 2: Microsoft Power Automate, Power Bi data alerts, and Microsoft 365 connector Data alerts in the Power BI service: Set alerts to notify you when data in your dashboards changes beyond limits you set.
Box 3: Microsoft Power Automate, Power BI, Power Apps, and Microsoft Dataverse connector Reference:
https://www.velosio.com/blog/2021/01/27/tracking-emails-the-right-way-with-power-automate/
https://docs.microsoft.com/en-us/power-bi/create-reports/service-set-data-alerts

Explanation
Graphical user interface, text, application, chat or text message Description automatically generated

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.
Reference:
https://docs.microsoft.com/en-us/power-bi/collaborate-share/service-troubleshoot-sharing
https://docs.microsoft.com/en-us/power-bi/connect-data/service-gateway-onprem
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/use-powerapps-checker
Topic 3, Fabrikam, inc.
Case study
This is a case study. Case studies are not timed separately. You can use as much exam time as you would like to complete each case. However, there may be additional case studies and sections on this exam. You must manage your time to ensure that you are able to complete all questions included on this exam in the time provided.
To answer the questions included in a case study, you will need to reference information that is provided in the case study. Case studies might contain exhibits and other resources that provide more information about the scenario that is described in the case study. Each question is independent of the other questions in this case study.
At the end of this case study, a review screen will appear. This screen allows you to review your answers and to make changes before you move to the next section of the exam. After you begin a new section, you cannot return to this section.
To start the case study
To display the first question in this case study, click the Next button. Use the buttons in the left pane to explore the content of the case study before you answer the questions. Clicking these buttons displays information such as business requirements, existing environment, and problem statements. If the case study has an All Information tab, note that the information displayed is identical to the information displayed on the subsequent tabs. When you are ready to answer a question, click the Question button to return to the question.
Background
Fabrikam, Inc. manufactures industrial metal cutting machines. The company installs and services the machines for customers.
Fabrikam has manufacturing plants in Canada, France, and China. The company also has regional service organizations that are responsible for installation and maintenance of the machines.
Current environment
Overview
Operations for the company are managed very informally. Only a small number of long-term employees are aware of all manufacturing processes. The company has been experiencing quality issues associated with its manufacturing operations and installations.
The company wants to implement a way to capture quality inspection results for each machine produced.
Current inspection checklists are stored in the Files section of a Teams channel for inspectors. Inspectors commonly print the incorrect inspection checklist.
The company has specific inspection stations for certain inspection steps. Each station has the gauges and equipment required for related inspection steps. There is often a backlog at specific inspection stations. This results in delays in shipping machines to customers.
Accounting system
The current system does not handle shop floor or manufacturing planning functionality.
Machines are assigned serial numbers and placed in stock until they are shipped to customers.
Employee information is maintained only within the accounting system. Access to the information is strictly controlled due to privacy regulations and company policies.
Other systems
The company has an enterprise Microsoft 365 subscription. The company uses Microsoft 365 only for sending and receiving email. The company uses photos of employees to generate employee badges.
Photos are uploaded into Microsoft 365 user profiles.
The company recently started using Dynamics 365 Field Service to manage and maintain the machines that it installs for its customers. The app has not been customized.
The company has added roles, skills, and certification proficiencies to Dynamics 365 Field Service resources to support both customer onsite inspections and final manufacturing inspections.
Requirements
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.
Inspection orders
Inspection orders must:
Allow entry of quality ratings of passed or failed for each quality metric identified for the machine being rated.
Include information about the person who performed each inspection step and any comments made by the inspector.
Be automatically marked as failed if one inspection step rating is marked as failed.
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.
Inspectors must fill in findings comments and upload at least one photo for any inspection step that is marked as failed.
Inspection standardization
Standardized checklists must be stored in the solution for use by inspectors. A copy must be created when a new inspection is initiated. The solution must:
Prevent an inspector from proceeding to the next step of the checklist until required information for a step is entered.
Support the addition of steps to inspections to support custom features added to a machine for a customer.
Support the direct input of measurements from testing gauges to avoid incorrect readings being entered by inspectors.
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.
Support the ability to store photo references within each inspection step to document defects found during inspections.
Security
Users must be active employees of Fabrikam.
When a user signs into the inspection solution, the solution must display a picture of the employee who has signed in.
Supervisors must be able to modify standard checklists. Other employees must be prevented from modifying checklists.
You must prevent users from changing inspection order data once an inspection is marked as final.
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.
Issues
During initial testing of the solution, testers report that they cannot see the photos taken during a previously failed inspection.

Explanation

Box 1: Functional
Functional requirements describe what the solution needs to do or its behaviors.
Box 2: Non-functional
Non-functional requirements commonly describe non-behavior aspects of the solution such as performance requirements.
Box 3: Non-functional
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
Reference:
https://docs.microsoft.com/en-us/learn/modules/work-with-requirements/3-functional-requirements
https://docs.microsoft.com/en-us/learn/modules/work-with-requirements/4-non-functional-requirements

Explanation

Explanation

Box 1: Increase multithreading and/or batch size settings
Box 2: Ensure you are loading data in a specific order.
Load the base tables in the hierarchies first.

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

Explanation

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.
Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/data-platform-entity-lookup

Reference:
https://docs.microsoft.com/en-us/power-bi/visuals/power-bi-visualization-radial-gauge-charts
https://docs.microsoft.com/en-us/dynamics365/field-service/inspections

Reference:
https://docs.microsoft.com/en-us/power-platform/admin/wp-data-loss-prevention
https://docs.microsoft.com/en-us/power-platform/admin/control-user-access

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:

Reference:
https://michalguzowski.pl/how-to-work-with-option-set-in-powerapps/

Explanation

https://learn.microsoft.com/en-us/power-platform/admin/manage-configuration-data