DRAG DROP (Drag and Drop is not supported)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.Select and Place:
Answer(s): A
Box 1: One-to-manyTo 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-manyYou 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: ConnectionsTo 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.
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
HOTSPOT (Drag and Drop is not supported)You are creating a relationship between two Dataverse tables.You need to configure a one-to-many relationship between the Vendor and Shipment tables and ensure that all child records are deleted when the parent record is deleted.Which configuration methods should you use? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Add a lookup column to Shipment on the Vendor tableThe best action is to add a lookup column to the Shipment table that references the Vendor table.In relational database and Dataverse design, a single Vendor will typically provide multiple Shipments over time. This establishes a one-to-many (1:N) relationship between Vendors and Shipments.Establishes the Relationship: Adding a lookup column on the child table (Shipment) pointing to the parent table (Vendor) physically creates the 1:N relationship.Data Integrity: It ensures that every shipment is tied to a valid, existing vendor.Box 2: Cascade allTo ensure that all child records are automatically deleted when the parent record is deleted, you should use the Cascade All setup.In Microsoft Dataverse, this behavior is configured by adjusting the Delete behavior of the relationship to Cascade.Cascade AllDeletes all related Shipment (Child) records automatically.Incorrect:Remove LinkClears the Vendor lookup field on the Shipment records, leaving them as orphaned records.RestrictPrevents the Vendor from being deleted until all related Shipment records are deleted first.
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-entity-lookup
Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.You administer the Microsoft 365 and Microsoft Power Platform environments for Contoso, Ltd. The company has a model-driven app that is used to track customer interactions with employees. The app uses standard table types for customers. A user named Elisabeth Rice signs in to the app by using the following sign in name: Elisabeth.Rice@contoso.com.After marriage, Elisabeth changes her legal name to Elisabeth Mueller.You need to update the sign in name for the user without losing any application history.Solution: From Dynamics 365 Settings, select Email Configuration. In the active mailbox for the user, update the name.Does the solution meet the goal?
Answer(s): B
Correct:* Ask the Microsoft 365 administrator to sign in to the admin portal and change the user name.Changing the username (User Principal Name/UPN) in the Microsoft 365 admin center updates the credentials the user employs to sign into the model-driven app. Because Microsoft Power Platform and Dataverse map permissions and record histories to the underlying, immutable object identifier (GUID) of the user record, modifying the UPN:Preserves history: The system retains all ownership of records, historical timelines, and application tracking linked to that user account.Updates the sign-in name: The new name flows directly into Microsoft Entra ID and syncs automatically with the Power Platform environment.Incorrect:* Change Elizabeth’s username in the user record for the app.* From Dynamics 365 Settings, select Email Configuration. In the active mailbox for the user, update the name.
DRAG DROP (Drag and Drop is not supported)You are designing an app for a bank.You must create tables for the app and configure relationships between the tables:Which relationship types should you use? To answer, move the appropriate relationship types to the correct requirements. Each relationship type may be used 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.Select and Place:
Box 1: N:1You add a lookup column with a many-to-one relationship.Box 2: N:NBox 3: N:1
https://docs.microsoft.com/en-us/powerapps/maker/data-platform/data-platform-entity-lookup
A company is building an AI-enabled solution that includes prompts, cloud flows, and Dataverse components.The solution must be released to production through a controlled process to include the following requirements:● Validate changes before production release.● Ensure production stability.● Ensure that release steps are repeatable and governed.● Ensure that the production environment reflects only controlled and traceable changes.You need to determine the appropriate deployment strategy.What should you do?
The best deployment strategy to meet all the requirements is to export the solution as managed from your source environment and import it as a managed solution into the production environment.Managed solutions prevent users or administrators from making direct, accidental modifications to the components in production, ensuring system stability.By exporting as managed and versioning your solution in a source control system (like Git) before deploying, you ensure every change is tracked, auditable, and easily rolled back if necessary.Required Actions in the Production EnvironmentTo maintain strict control in your production environment, follow these execution steps:Import as Managed: Always import the solution package into Production as a managed solution.Do Not Make Unmanaged Customizations: Never edit cloud flows, prompts, or Dataverse tables directly in the production environment. Any direct edits create an "unmanaged layer" that blocks future updates.Use Environment Variables: Configure connection references and environment variables (such as API keys or URLs for your AI prompts/cloud flows) during the import step to ensure they point safely to production endpoints without altering the core package.
https://learn.microsoft.com/en-us/power-platform/guidance/adoption/application-modernization
Post your Comments and Discuss Microsoft AB-410 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AB-410 content, but please register or login to continue.