Reference:
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/data-platform-entity-lookup 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
Relecloud provides regional air service in North Americ
a. The company uses a variety of systems, apps, and services to manage the business. You are hired to design a new solution to manage passenger information, reservations, and maintenance.
Topic 3, Fabrikam, inc.
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.

Reference:
https://docs.microsoft.com/en-us/microsoft-365/commerce/subscriptions/self-service-purchase-faq
https://docs.microsoft.com/en-us/azure/active-directory/external-identities/what-is-b2b
https://docs.microsoft.com/en-us/dynamics365/field-service/overview

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

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/microsoft-365/solutions/empower-people-to-work-remotely
https://docs.microsoft.com/en-us/microsoftteams/business-voice/whats-business-voice