DRAG DROP (Drag and Drop is not supported)You make the following customizations to a Microsoft Dataverse environment:● Create a new table.● Add data to the new table.● Delete an unused area from the site map.The components must be transported to a different environment.You need to determine the method required to transport each component.Which method should you use? To answer, move the appropriate methods to the correct components. Each method 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:
Answer(s): A
Box 1: SolutionCreate a new table.View and edit tables representing solution objectsSome standard tables in Dataverse represent the structure and instances of solution objects.Power Apps offers standard "out-of-the-box" tables to cover typical scenarios within an organization (such as tracking appointments), but there may be times when you need to create custom tables to store data that's specific to your organization.Note: Create a table.Sign in to Power Apps at https://make.powerapps.com.Create a table1.In the navigation pane, expand Data, and then select Tables.2.On the command bar, select New table.3.Etc.Box 2: Configuration Migration toolAdd data to the new table.The Configuration Migration tool is used to transport configuration and test data from one environment to another. It provides the means to capture such data, use that data in source control, and use that data to automate testing.Box 3: SolutionPackagerDelete an unused area from the site map.SolutionPackager is a tool that can reversibly decompose a Microsoft Dataverse compressed solution file into multiple XML files and other files so that these files can be easily managed by a source control system.
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-create-entity https://learn.microsoft.com/en-us/power-platform/alm/configure-and-deploy-tools
You must create a new table to support a new feature for an app. Records for the table must be associated with a business unit. The table must be visible when specifying a security role.You need to configure table ownership.Which table ownership type should you use?
Answer(s): D
Table/record ownershipDataverse supports two types of record ownership. Organization owned, and User or Team owned. This is a choice that happens at the time the table is created and can’t be changed. For security purposes, records that are organization owned, the only access level choices is either the user can do the operation or can’t. For user and team owned records, the access level choices for most privileges are tiered Organization, Business Unit, Business Unit and Child Business Unit or only the user’s own records. That means for read privilege on contact, I could set user owned, and the user would only see their own records.Note: Owning Business UnitEach record has an Owning Business Unit column which determines which business unit owns the record. This column defaults to the user’s business unit when the record is created and cannot be changed except when the feature switch is turned ON.
https://learn.microsoft.com/en-us/power-platform/admin/wp-security-cds
You plan to implement Microsoft Dataverse.You must track changes for two columns in the Account table. You must maintain a historical log of changes for the two columns and track only what is necessary. You configure the appropriate organization settings.You need to configure the system to track changes for the two columns.Which two actions should you perform? Each correct answer presents part of the solution.Note: Each correct selection is worth one point.
Answer(s): B
The two steps required to set up the system to track changes for the two specific columns are:1. Enable auditing for the Account table.2. Enable auditing for the two specific columns.To maintain a historical log of changes within Microsoft Dataverse, auditing must be enabled at three levels: environment, table, and column.Why Auditing and not Change Tracking: The requirement asks for a historical log of changes. Change Tracking is used to synchronize incremental data changes with external systems and does not maintain a user-viewable historical log.Minimizing necessary logging: Since the prompt mentions the environment (organization) settings are already set up, you must enable auditing on the Account table itself first, and then explicitly configure it for only the two specific columns to limit tracking to what is strictly necessary.
https://learn.microsoft.com/en-us/power-apps/developer/data-platform/use-change-tracking-synchronize-data-external-systems
HOTSPOT (Drag and Drop is not supported)A company must be able to monitor changes to records and support integration with external systems. The solution must provide the following functionality:● Maintain a history of changes to records.● Allow external systems to detect data updates.You need to configure table properties.How should you configure the properties? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
Box 1: Enable auditing at the table levelYou need to enable auditing at the table level to maintain a historical log of record changes.Maintain History: Auditing in Microsoft Dataverse explicitly records data changes (creates, updates, and deletes) to provide a chronological history and audit trail of what changed, who changed it, and when.Box 2: Enable change tracking at the table levelTo support integration with external systems and allow them to detect data updates, you must enable Change Tracking at the table level.Change tracking is optimized for data synchronization and external data warehouses (keeping external stores updated efficiently), and not for presenting a human-readable historical log of record changes.
You create a parent entity and a child entity. The parent entity has a 1:N relationship with the child entity.You need to ensure that when the owner changes on the parent record that all child records are assigned to the new owner.You need to configure the relationship behavior type.What should you use?
To automatically assign all child records to a new owner when the parent record's owner changes, you must use a Parental relationship behavior type, or a Configurable Cascading relationship behavior type with the Assign action set to Cascade All.
https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/create-and-edit-1n-relationships
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.