Instantly download AB-410 updated real questions

Drag and Drop Question
A company uses a cloud flow to process customer records in Dataverse.
The flow must:
- Retrieve a customer record.
- Store the customer email address for later use.
- Use the stored value in an email action.
You need to configure flow actions.
Which four 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.
NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.

Explanation:
Step 1: Get a row by ID (Dataverse)
Retrieve the specific customer record.
Step 2: Initialize a variable
Create a string variable to hold the email address.
Step 3: Set variable
Store the customer's email address in the initialized variable
Step 4: Send an email
Pass the stored email variable into the "To" field of the email action
Reference:
https://learn.microsoft.com/en-us/power-automate/create-variable-store-values

Hotspot Question
You are configuring a dashboard in a model-driven app for sales managers. The dashboard displays opportunity pipeline data from the Opportunities table.
The company requires the following functionality:
- Show how each sales stage contributes to the total pipeline for each
sales region.
- Ensure a newly created chart is available to users in the app.
- Use the My Open Opportunities dataset when the dashboard component
loads.
- Prevent users from switching to a different chart at runtime.
You need to create and configure the chart and dashboard component.
How should you configure the requirements? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.

Explanation:
Box 1: Configure a stacked column chart.
To show how each sales stage contributes to the total pipeline for each sales region, you need to create a Stacked Column or Stacked Bar chart on the Opportunities table and add it to a dashboard.
Box 2: Select the chart for the table in the app designer
To ensure the newly created chart is available to sales managers in the model-driven app, you must select the chart for the table in the app designer.
In Power Apps model-driven apps, assets like tables, views, forms, and charts are not automatically included in an app just because they exist in the Dataverse environment.
The App Designer Rule: You must explicitly check the box next to your new chart under the Opportunity table components within the App Designer. If it is not selected there, users will not be able to see or interact with it inside that specific app.
The Dashboard Component: When you add a chart component to a dashboard, you also configure its properties. While "Enable Display Chart selection" allows users to toggle between different charts on the dashboard, the chart itself must still be a part of the app's included components to function correctly.
Box 3: Set the Default View
To set the "My Open Opportunities" dataset as the default view when your dashboard loads, you must configure the Default View property for the list or chart component within the dashboard designer.
Box 4: Clear display Chart selection
To meet this requirement, you must clear the "Show chart selection" checkbox in the dashboard component properties within the Power Apps app designer. This action locks the specific chart to the dashboard visual and prevents sales managers from changing it at runtime.
Reference:
https://learn.microsoft.com/en-us/dynamics365/sales/opportunity-pipeline-view-for-admins
https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/set-properties-chart-list-included-dashboard

A company tracks order processing duration using a model-driven app.
The company requires a system that provides the following functionality:
- The age of the order, based on the created date, must be displayed on forms and views.
- The value must update dynamically when viewed without storing the
result.
- The value must NOT be stored in the database.
You need to configure the column types.
Which two column types should you use? Each correct answer presents part of the solution.
NOTE: Each correct selection is worth one point.

• A. Formula
• B. Calculated
• C. BigInt
• D. Prompt

Explanation: Only visible for Exam-Killer members. You can sign-up / login (it's free).

Case Study 1 - Contoso, Ltd
Background
Contoso Ltd. is a global renewable energy provider that operates wind farms and solar installations. The company is modernizing its maintenance and operations platform. The company plans to implement a Microsoft Power Platform solution for the operations team. The implementation will include Microsoft Dataverse, a model-driven app, and Power Automate cloud flows.
The company is building and testing a new model-driven app named Operations. The solution will support operations managers, regional coordinators, and field technicians. The app must integrate with an external cloud-based system that manages onboarding of field technicians.
Contoso Ltd. plans to improve data quality and enforce consistent business logic across the app and automation processes.
Technical environment
Contoso Ltd. has an Identity and Access Management (IDAM) department that manages security.
The company has one Power Platform environment named Production, where all building and configuration take place. Auditing is disabled.
The Production environment has the following security configurations:
- IDAM has a Microsoft Entra security group named Contoso Ltd. QA. This security group will assign all members a Power Apps license.
- IDAM created a Quality Assurance security role that grants read and write access to all custom tables.
- IDAM also created a team named Testers in Dataverse, of a Microsoft Entra group team type.
The team is configured for the Contoso Ltd. QA security group. The Testers team is assigned the Quality Assurance security role.
Microsoft 365 environment
All Contoso Ltd. managers are included in a Microsoft 365 group named Managers. The group is NOT enabled for email.
The company shares a SharePoint list with a key customer: Alpine Ski House. Alpine Ski House staff members can add new maintenance requests, which are then checked and marked as reviewed by Contoso Ltd.
Current issue:
A new QA tester joins Contoso Ltd. The IDAM department adds the new tester to the Contoso Ltd. QA security group. However, the new tester is not listed in the Testers team as a member.
Other applications:
A separate software-as a-service (SaaS) solution named TechCheck manages technician onboarding. The TechCheck solution is set up as follows:
- TechCheck assigns a unique number named Ref to all technicians.
- Users cannot make changes to the TechCheck data model.
- Users cannot use the same TechCheck ref on more than one Technician row.
Automation requirements
Contoso plans to use Power Automate to develop a Maintenance Request Approval flow. The flow must meet the following requirements:
- Create a Maintenance Request row in Dataverse when either of the following occurs:
- An item is added to the SharePoint list by the customer with the Priority property set to High.
- Any item is checked and marked as reviewed by a Contoso Ltd. representative.
- Seek maintenance request approvals from managers through both email and a Microsoft Teams message after they have been reviewed:
- Requests require approval from all managers.
- If one manager rejects the request, approval must not be granted.
- The result of the approval request must be sent to the initial reviewer in an email. The subject line must set the response as either Approve or Reject.
Contoso Ltd. requires the following table logic:
- If a user tries to enter a price greater than the cost on a new Asset row, the row must display an inline error message.
- If a user tries to save changes to a Technician row where the TechCheck ref column is empty, the action must be prevented and a message explaining the action must be displayed.
Any updates made to Technician profiles in TechCheck must be mirrored in Dataverse by using a custom integration. The developers building the integration require an index for performant searches on the Technician table.
Data model and app design
Contoso Ltd. plans to use Dataverse as its central data platform. Log storage must be minimized.
Tables
The following tables are required for data modeling and the app design:
- Assets: Stores information about solar panels and wind turbines
- Maintenance Requests: Tracks issues and maintenance activities. The table must include the following columns:
- Request ID (auto-number)
- External Request Code (text)
- Assigned
- Technician (lookup to Technicians)
- Report (lookup to Maintenance Reports)
- Technician updated (Yes/No)
- Maintenance Reports: Tracks the results of maintenance reports
- Technicians: Stores technician assignment data. The table must include the following columns:
- Full Name (Text)
- Mobile phone number (Text)
- Email (Text)
- Seniority (Choice)
- TechCheck ref (Text)
Data modeling
The data model must provide the following functionality:
- Maintenance Requests must:
- be uniquely identifiable across systems.
- have two inactive statuses, Cancelled and Duplicate.
- If a new option is added to an existing set of options, it must be made available automatically for selection on all columns that use the set.
- A new column named Priority must be added to multiple tables. Users must be able to select only one option from the following set per row:
- Low
- Medium
- High
- Critical
Changes to the Technician column on Maintenance Requests must be tracked for compliance purposes. Rows must include the names of previous and current technicians and the time of the change.
Relationship requirements
- One asset can be related to many maintenance requests. A maintenance request can have many assets.
- A maintenance request can have only zero or one maintenance report.
- Only one Technician can be related to a Maintenance Request at a time.
- When a Maintenance Request is deleted, any Maintenance Reports associated with it must also be deleted, but this action should be prevented if there is value in the Technician lookup.
- When a Maintenance Request is assigned to a different owner, the Maintenance Report associated with it must be reassigned to the new owner as well, but the associated Technician should stay with the current owner.
App design
The Technicians table contains the following public views:
- Senior Technicians
- Junior Technicians
The Senior Technician view must be available through the table list view selector to a set of specific users only.
A tester creates a personal view named Hot Assets on the Assets table. The tester recognizes that the view is useful for the entire testing team. The view must be made accessible to the team.
Drag and Drop Question
You need to configure the Maintenance Request relationships to the other tables.
Which type of relationship behavior should you set? To answer, move the appropriate behavior types to the correct tables. You may use each behavior type once, more than once, or not at all.
You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

Explanation:
Box 1: Referential, Restrict Delete
If forced to choose the closest standard behavior that ensures the primary safety rule (preventing deletion if a technician is assigned) is met before any deletion happens, Referential, Restrict Delete Box 2: Referential, Restrict Delete The correct relationship type to use is Referential, Restrict Delete.' One-to-Many Structure: A technician can have multiple requests, but each request only links to one technician. This requires a standard lookup field on the Maintenance Request table.
Data Integrity: Restrict Delete prevents a technician record from being deleted if they are still assigned to active maintenance requests. This stops your data from becoming orphaned or broken.
Independent Lifecycles: A maintenance request should not be deleted just because a technician leaves the company (which rules out Parental).Historical Tracking: You want to keep the maintenance history intact rather than clearing the technician link blank (which rules out Remove link).
Scenario:
Relationship requirements
A maintenance request can have only zero or one maintenance report.
Only one Technician can be related to a Maintenance Request at a time.
When a Maintenance Request is deleted, any Maintenance Reports associated with it must also be deleted, but this action should be prevented if there is value in the Technician lookup.
When a Maintenance Request is assigned to a different owner, the Maintenance Report associated with it must be reassigned to the new owner as well, but the associated Technician should stay with the current owner.
Reference:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-entity-lookup

Drag and Drop Question
An insurance company is implementing a customer service solution in Microsoft Dataverse to track interactions and manage issue resolution. The data model includes tables for customer information, support cases, and agents.
The data model includes the following requirements:
- Link each support case to a customer.
- Provide information on the children of customers.
- Record history of agents assigned to customers.
You need to configure table relationships.
Which relationships should you use? To answer, move the appropriate relationship to the correct requirement. You may use each relationship once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.

Explanation:
Box 1: One-to-many
To link each support case to a specific customer in Microsoft Dataverse, you should use a One- to-many (1:N) relationship. This allows one customer (Account or Contact) to be associated with multiple support cases over time, while each individual case is linked to exactly one customer.
Box 2: One-to-many
You should use a One-to-many relationship.
Parent to Children: One customer (parent) can have multiple children.
Child to Parent: Each child belongs to only one customer (parent) in this specific structural context.
Note: Both the children parents could be customers, in which case a many-to-many relation could be considered.
Box 3: Connections
To record a history of multiple agents assigned to multiple customers over time, you should use Connections.
Tracks Historical Data: Standard Dataverse relationships (like One-to-Many) only show the current assignment. Connections let you keep a running log of past and present relationships.
Many-to-Many Behavior: An agent can be linked to many customers, and a customer can have many agents over time.
Adds Context: Connections allow you to assign "Connection Roles" (e.g., "Primary Agent,"
"Backup Agent," "Former Agent") and include start/end dates for when the agent was assigned.
Reference:
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-edit-entity-relationships
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/connection-entities