AB-410 Dataverse Foundations Practice Test 3 — 15 Questions

Question 1

A maker at Contoso creates a custom table named Project Tracker in Dataverse. The maker needs to prevent records from being deleted after they are created, while still allowing users to modify column values. Which table property should the maker configure?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Enable the table option to prevent delete operations.. The table-level option that blocks delete operations directly enforces record permanence while leaving update capability intact. Ownership, required columns, and alternate keys each serve different purposes and none of them prevent a user or integration from deleting a record. Only the delete-prevention setting on the table itself satisfies both halves of the requirement.

Answer

Configure an alternate key on the primary column.

Answer

Mark all columns as required at the table level.

Answer

Set the table's Ownership to User or Team.

Question 2

You are a Power Platform administrator. You need to create a new environment for a development team. The environment must be able to host Dataverse and must be isolated from production data. Which two environment types should you consider? (Choose two.)

Accepted Answer

Developer. Sandbox and Developer environments are both non-production, can host Dataverse, and are isolated from production data. Sandbox is suitable for team development and testing, while Developer is for individual developers. Production, Trial, and Default do not meet the requirements for isolation and persistence.

Answer

Trial

Answer

Production

Answer

Default

Question 3

You are creating a canvas app that connects to Dataverse. You need to display a list of active accounts and allow users to filter by name. Which Dataverse feature should you use to retrieve the data efficiently?

Accepted Answer

Use the Dataverse connector with the Filter rows function. The Dataverse connector's Filter function enables server-side filtering, which is efficient for retrieving only the needed records. Retrieving all accounts and filtering locally is inefficient and may cause delegation issues. The Common Data Service connector is deprecated, and the Office 365 Users connector is unrelated to Dataverse accounts. Therefore, using the Dataverse connector with Filter rows is the correct approach.

Answer

Use the Dataverse connector and retrieve all accounts, then filter in the app

Answer

Use the Office 365 Users connector to get accounts

Answer

Use the Common Data Service connector with a SQL query

Question 4

You are designing a Dataverse solution that includes a custom table named Project. You need to ensure that users can only see Projects that belong to their business unit. Which two features should you configure? (Choose two.)

Accepted Answer

Assign the Project records to the appropriate business unit.. To restrict record visibility to a user's business unit, the table must be business unit-owned or organization-owned, and records must be assigned to the correct business unit. Then a security role with business unit-level read access on the table grants users the ability to see those records. This combination enforces the desired row-level security.

Answer

Enable field-level security on the Project table.

Answer

Configure the Project table's ownership to Organization.

Answer

Set the ownership of the Project table to User or Team.

Question 5

You are configuring a new Dataverse environment for a sales team. You need to set up relationships between the Account and Contact tables. Which two relationship types are supported in Dataverse? (Choose two.)

Accepted Answer

Many-to-Many (N:N). Dataverse natively supports One-to-Many and Many-to-Many relationships. One-to-Many is used when a single record relates to multiple records in another table, and it is implemented via a lookup. Many-to-Many allows multiple records in both tables to relate to each other, using an intersection table. Other relationship types are either not supported or are variations of these two.

Answer

Many-to-One (N:1)

Answer

One-to-One (1:1)

Answer

Self-referential (Hierarchical)

Question 6

A developer is configuring a new custom table in Dataverse. They need to enable features that allow users to track changes to records and to see who created or modified a record. Which two actions should they take? (Choose two.)

Accepted Answer

Enable auditing for the table. To track changes and see who created or modified records, you must enable auditing for the table and then enable auditing for the specific columns you want to monitor. Dataverse automatically includes Created By and Modified By columns, but auditing provides a detailed history of changes. Change tracking is for data synchronization, not audit trails.

Answer

Configure the table to use a custom primary key

Answer

Add a 'Created By' and 'Modified By' column

Answer

Enable change tracking for the table

Question 7

You are designing a data model in Dataverse. You need to establish relationships between tables. Which two relationship types are supported in Dataverse? (Choose two.)

Accepted Answer

Many-to-Many. Dataverse supports two primary relationship types: One-to-Many and Many-to-Many. One-to-Many is used when a single record relates to multiple records in another table, implemented via a lookup. Many-to-Many allows multiple records to be associated with multiple records, using an intersection table. Other relationship types like One-to-One or Hierarchical are not native and must be modeled using these two.

Answer

One-to-One

Answer

Many-to-One

Answer

Hierarchical

Question 8

A developer is building a model-driven app for a help desk. Agents must see only the support cases assigned to their own team, and the filtering must apply automatically whenever the app loads the case list. Which Dataverse mechanism should the developer use to enforce this consistently?

Accepted Answer

Create a system view with a filter on the owning team column.. System views are defined on the table and evaluated by Dataverse, so filters such as records owned by the current user's team are applied consistently across any model-driven app that surfaces the view. Client scripts, business rules, and field-level security each operate at different layers and cannot reliably restrict the set of rows returned to an agent.

Answer

Enable field-level security on the case title column.

Answer

Add a JavaScript web resource that hides rows in the grid after load.

Answer

Configure a business rule on the Case table to set a read-only state.

Question 9

You are managing a Dataverse environment that contains a custom table named Invoice. You need to prevent users from deleting Invoice records that have a status of 'Paid'. Which feature should you configure?

Accepted Answer

A plug-in registered on the Pre-Delete event of the Invoice table.. To prevent deletion of records based on a condition, you must use a plug-in registered on the Pre-Delete event. This server-side code executes before the deletion is finalized and can throw an InvalidPluginExecutionException to cancel the operation. Business rules, column-level security, and workflows do not execute on delete or cannot block the operation, so they are not appropriate for this requirement.

Answer

A business rule on the Invoice table that checks the status and prevents deletion.

Answer

A column-level security profile that marks the status column as read-only.

Answer

A workflow that triggers on the status change and sends an email to the administrator.

Question 10

You are a Power Platform developer. You have a model-driven app that uses a custom table named Order. The Order table has a lookup column to the Account table. You need to ensure that users can only select active accounts when creating or editing an Order record. What should you do?

Accepted Answer

Configure the lookup column to use a custom view that filters accounts to show only active ones.. To restrict the lookup to only active accounts, you configure the lookup column to use a custom view that filters for active accounts. This ensures that users only see and can select active accounts. Other options either do not exist or do not prevent selection of inactive accounts.

Answer

Use a Power Automate flow to update the lookup column to null if the selected account is inactive.

Answer

Create a business rule that checks if the selected account is active and prevents saving if not.

Answer

Set the lookup column to 'Restrict to active records only' in the column properties.

Question 11

You are designing a Dataverse solution for a healthcare provider. The solution includes a custom table named Patient that stores sensitive health information. You need to ensure that only users with a specific security role can view Patient records, and that even users with that role cannot delete records. Which combination of security role settings should you configure?

Accepted Answer

Grant Read privilege at the User level, and set Delete privilege to None.. To restrict viewing to only users with a specific security role, you must ensure that no other roles grant Read access. Within the role, setting Read to User level limits viewing to records the user owns or that are shared with them. Setting Delete to None prevents deletion. This combination satisfies both the view restriction and the deletion prohibition.

Answer

Grant Read privilege at the Business Unit level, and set Delete privilege to None.

Answer

Grant Read and Delete privileges at the Organization level.

Answer

Grant Read and Write privileges on the Patient table, and set Delete privilege to None.

Question 12

A team is configuring a new custom table in Dataverse. They want to ensure the table supports relationships to other tables and that records can be associated with multiple related records. Which TWO configuration choices are required or appropriate to meet these goals? (Choose two.)

Accepted Answer

Create a many-to-many relationship between the custom table and the related table.. Relationships in Dataverse are defined explicitly: a one-to-many relationship places a lookup on the related table, and a many-to-many relationship uses an intersect table for peer associations. Both directly enable linking records and associating one record with multiple related records. Autonumber formatting, a nonexistent multiple-relationship toggle, and ownership hierarchies do not provide these relational capabilities.

Answer

Mark the custom table as a child table in an ownership hierarchy.

Answer

Enable the table option to allow multiple relationships to the same table.

Answer

Set the custom table's primary column to an autonumber format.

Question 13

A maker is troubleshooting an app that queries a Dataverse table containing several million rows. A view returns results quickly when filtered by a custom text column, but a similar query filtered and sorted on a custom whole number column is very slow. The maker confirms both columns are used in the same view definition. What is the most likely explanation?

Accepted Answer

The whole number column is not indexed, so Dataverse cannot use an index for the filter and sort, while the text column benefits from default indexing behavior.. Dataverse keeps indexes on many system columns and on certain column types by default, but custom columns such as whole number are not indexed until an index is explicitly defined. A filter plus sort on an unindexed column over millions of rows forces a scan and a sort, which is slow, whereas the text column benefits from default indexing behavior. Adding an index on the whole number column restores fast server-side execution.

Answer

Sorting on a whole number column forces the query to run client-side, which is inherently slower than server-side text filtering.

Answer

The view is exceeding the Dataverse result limit, causing the platform to discard rows before applying the filter.

Answer

Whole number columns cannot be used in Dataverse view filters and must be converted to decimal before use.

Question 14

Which tool is used to manage Dataverse environments and solutions?

Accepted Answer

Power Platform admin center. The Power Platform admin center is the centralized web portal for managing environments, Dataverse capacity, solutions, security roles, and tenant-wide settings across Power Apps, Power Automate, and Dataverse. Administrators use it to create/manage environments, deploy solutions, and monitor usage. Power Apps Studio and Solution Explorer are maker tools, not admin management surfaces.

Answer

Power Apps Studio

Answer

Dataverse Web API

Answer

Solution Explorer

Question 15

A developer needs to ensure that a custom field value is validated before the record is saved to the database. Where should this logic be placed?

Accepted Answer

Synchronous Plugin. A synchronous plugin executes within the Dataverse pipeline before the record is committed to the database, making it the correct place to enforce server-side validation that must block the save. Because it runs synchronously in the Pre-Operation or Pre-Validation stage, it can throw an InvalidPluginExecutionException to prevent the save if validation fails.

Answer

Power Automate Cloud Flow

Answer

Client-side JavaScript

Answer

Business Rule on the form