nerdexam
Microsoft

PL-200 · Question #335

Case Study 4 - Contoso Suites Background Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs…

The correct answer is Edit the resident form.; Add a form component.; Select the lookup. The correct sequence of actions configures the Resident form to display related food details by adding a Quick View Form component linked to the food lookup.

Create apps by using Microsoft Power Apps

Question

Case Study 4 - Contoso Suites Background Contoso Suites is an animal shelter that specializes in finding homes for dogs that have been given up by their owners. The shelter can house up to 20 dogs. The shelter is implementing one model-driven Power Apps app to track the dogs and schedule meetings with potential adopters. No other apps will be created. The model-driven app uses Dataverse with out-of-the-box functionality when possible. Dataverse is set up with the following configuration: - The solution prefix "cs" is used for all new components. - Only the root business unit is used. - All tables are stored in Dataverse and do not require rapid scaling. - Exchange server-side sync is not configured. Adopters - Adopter information is stored in a Contact table. - Contacts are considered to be duplicates if they have the same email address and last name. - Adopters are often late to meetings, so a reminder email is sent to them two hours before their meeting. - The email reminders must not be tracked in the system. Dogs - Dog information is stored in a Dog table, which is organization owned. - Breed, size, and weight are fields in the table. Dog residency - A Resident table tracks the stay of each dog. - Each resident record has a lookup for the dog and its food. - The food type and amount are logged on each resident record. Auto-posting is not configured for changes to food type and amount. - A fee of $120 is in a currency column named Adoption Fee. This fee can be changed depending on the adoption circumstances. - A formula column named Deposit is automatically populated with 20% of the adoption fee. - A resident record is generated automatically when a dog record is created. This is the only way a resident record can be created. Exercise and feedings - Exercise for the dogs is tracked in an Exercise table. - Feedings are tracked in a Feeding table. - Exercise and feeding records appear in a resident record timeline. Care staff - The care staff must be able to view who changed the food type and the amount that was given, for up to three months ago. - The staff must be able to update the weight of a dog on the resident record. - The staff report that the buttons are too small on the touch screen they use to log exercise and feeding. - The staff must be able to view who the adopters are for upcoming meetings. The staff must not be able to update adopter information. Administrative staff - Administrative staff must receive a weekly list of duplicate contacts. Duplicate alerts must not appear when a staff member saves a new contact. - When an adopter wants to adopt a dog, the staff must perform a series of adoption duties in order. The following duty list must be displayed on the screen: o Commitment: - Obtain adopter signature in a commitment document. - Collect deposit. o Pre-pickup: - Document spay or neutering date. - Perform spay or neutering. - Document pickup date. o Pickup: - Collect full payment. - Verify dog is picked up. o A dog must be picked up no sooner than two days after spaying or neutering. o A pop-up window must appear with an error message if the Pickup date is too soon. o Only administrative staff must be able to add new adopters and dogs. Drag and Drop Question You need to enable the care staff to update a dog's weight. Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order. Answer:

Exhibit

PL-200 question #335 exhibit

Answer Area

Drag items

Add a code component.Select the lookup.Edit the dog form.Edit the resident form.Add a form component.

Correct arrangement

  • Edit the resident form.
  • Add a form component.
  • Select the lookup.

Explanation

The correct sequence of actions configures the Resident form to display related food details by adding a Quick View Form component linked to the food lookup.

Approach. The case study describes a 'Resident table' that tracks dog stays and has a lookup for 'food'. It also states that 'food type and amount are logged on each resident record', implying these details should be accessible or displayed on the Resident form. The most appropriate way to display related record information (like food type and amount from the linked Food record) on a form in Power Apps model-driven apps is by using a Quick View Form component. The steps to achieve this are:

  1. Drag 'Edit the resident form.' to position 1: To make any modifications to the Resident form, you must first open it in the form editor within the Power Apps maker portal. This is the essential starting point for form customization related to the 'Resident' table.

  2. Drag 'Add a form component.' to position 2: After opening the form, if the goal is to display details from a related record (the food record via its lookup), you would add a Quick View Form component. A Quick View Form component is a type of 'form component' designed specifically for this purpose. It acts as a container to show fields from a record related via a lookup.

  3. Drag 'Select the lookup.' to position 3: Once the Quick View Form component has been added to the Resident form, you then need to configure it. A crucial configuration step for a Quick View Form component is to associate it with an existing lookup field on the current form. By 'selecting the lookup' (specifically the 'food' lookup in this context), you tell the Quick View Form component which related record's data it should retrieve and display (using a pre-defined Quick View Form from the looked-up Food table). This completes the setup for displaying related food details on the Resident form.

Common mistakes.

  • common_mistake. - Incorrect starting form: Dragging 'Edit the dog form.' to position 1 would be incorrect because the scenario explicitly mentions the 'Resident table' for dog residency and the requirement to log food type and amount 'on each resident record'. The context for configuration is clearly the Resident form.
  • Irrelevant actions: 'Add a code component.' is used for custom client-side JavaScript or TypeScript controls/logic, not for displaying related data through standard form elements like lookups or Quick View Forms. This action is not relevant to the described scenario.
  • Incorrect order: Swapping 'Add a form component.' and 'Select the lookup.' would be illogical. You first add the structural element (the form component, e.g., Quick View Form), and then you configure that component, which includes specifying the lookup field it should utilize. You cannot 'select a lookup' in this context as an independent first step of configuration for a complex component; rather, it's a step within the component's properties.

Concept tested. Form customization in Power Apps model-driven apps, specifically the use of Quick View Forms to display related record information via lookup fields, and the sequential steps involved in editing a form.

Topics

#Model-driven app forms#Quick View forms#Dataverse security roles#Dataverse relationships

Community Discussion

No community discussion yet for this question.

Full PL-200 Practice