AB-410 Dataverse Foundations Practice Test 8 — 15 Questions

Question 1

You are building a model-driven app that uses Dataverse. You need to ensure that users can only view records that they own or that are shared with them. Which security concept should you implement?

Accepted Answer

Record-level security. Record-level security is the correct concept because it controls access to individual records based on ownership and sharing. By configuring security roles with appropriate access levels, you can ensure users only view records they own or that have been explicitly shared with them, meeting the requirement.

Answer

Column-level security

Answer

Hierarchical security

Answer

Field-level security

Question 2

You are a Power Platform developer. You need to create a new custom table in Dataverse to store product information. The table must have a column that can store a monetary value and another column that can store a yes/no choice. Which column data types should you use?

Accepted Answer

Currency for monetary value and Two Options for yes/no choice.. The Currency data type is specifically designed for monetary values, providing currency formatting and precision. The Two Options data type stores a yes/no choice. These are the standard Dataverse data types for these requirements. Other options either use incorrect type names or less appropriate types that do not provide the necessary functionality.

Answer

Floating Point Number for monetary value and Yes/No for yes/no choice.

Answer

Money for monetary value and Boolean for yes/no choice.

Answer

Decimal Number for monetary value and Choice for yes/no choice.

Question 3

A developer is configuring a new custom table in Dataverse. They need to ensure that the table supports auditing and that users can search for records using the Dataverse search. Which two table properties must be enabled? (Choose two.)

Accepted Answer

Enable for Dataverse search. To support auditing, the table must have auditing enabled. To be searchable via Dataverse search, the table must be enabled for search. Change tracking, quick create, and attachments are separate features that do not fulfill the stated requirements. Thus, the two correct properties are Enable auditing and Enable for Dataverse search.

Answer

Enable change tracking

Answer

Enable attachments

Answer

Enable quick create

Question 4

A Dataverse environment contains a custom table 'Invoice' with a column 'TotalAmount' of type Currency. You need to ensure that the 'TotalAmount' is automatically calculated as the sum of line items whenever a related 'InvoiceLine' record is created, updated, or deleted. The calculation must be consistent regardless of how the data is modified (e.g., through the app, API, or import). What should you use?

Accepted Answer

Rollup column on the Invoice table. A rollup column is specifically designed to aggregate values from related records, such as summing child line items into a parent total. It is maintained by the Dataverse platform and recalculates automatically, ensuring consistency regardless of how the data is modified. This makes it the correct choice for automatically calculating TotalAmount from InvoiceLine records.

Answer

JavaScript web resource on the Invoice form

Answer

Power Automate cloud flow triggered on InvoiceLine changes

Answer

Calculated column on the Invoice table

Question 5

You are building a canvas app that connects to Dataverse. You need to store a list of product categories that will be used across multiple apps. The categories should be easy to update without modifying any app. What should you create?

Accepted Answer

A custom table named Category with a primary column for the category name.. A custom table in Dataverse is the appropriate choice for storing shared reference data that multiple apps can consume. It centralizes data management, supports security roles, and allows updates without app modifications. Other options are either app-specific or lack the necessary structure and manageability.

Answer

An Excel file stored in OneDrive and connected via the Excel connector.

Answer

A static collection defined in each app's OnStart property.

Answer

A global choice column in the Product table.

Question 6

A developer needs to create a relationship between two Dataverse tables: 'Project' and 'Task'. A project can have many tasks, but each task belongs to exactly one project. The developer also wants to ensure that when a project is deleted, all related tasks are automatically deleted. Which type of relationship and configuration should they use?

Accepted Answer

One-to-many relationship with cascade delete configured to 'Cascade All'.. The scenario describes a classic one-to-many relationship: one project has many tasks, and each task belongs to one project. To automatically delete tasks when a project is deleted, the cascade delete behavior must be set to 'Cascade All'. This ensures referential integrity and matches the requirement. Other cascade options like 'Remove Link' or 'Restrict' do not delete the child records.

Answer

One-to-many relationship with cascade delete set to 'Remove Link'.

Answer

One-to-many relationship with cascade delete set to 'Restrict'.

Answer

Many-to-many relationship with cascade delete enabled.

Question 7

You are building a model-driven app for a sales team. The app uses a Dataverse table named Opportunity. You need to ensure that when a user opens an Opportunity record, they see a read-only list of related Contacts that are associated with that Opportunity. The list should appear on the main form and allow users to open a Contact record. What should you add to the form?

Accepted Answer

A subgrid.. A subgrid is the correct form component to display a list of related records, such as Contacts associated with an Opportunity. It shows multiple records in a grid, supports read-only mode, and allows users to open individual records. Quick view forms show a single related record, timeline controls show activities, and lookup columns allow selecting a single record, so none of those meet the requirement for a read-only list.

Answer

A quick view form.

Answer

A lookup column.

Answer

A timeline control.

Question 8

A developer is creating a Power Automate cloud flow that must retrieve all active accounts with a specific industry and then update a custom column on each. The flow will run daily. Which Dataverse action should be used to efficiently retrieve the records?

Accepted Answer

List rows. The List rows action is the correct Dataverse connector action to query multiple records with a filter. It supports OData filter expressions and can be set to return all records via pagination. Get a row by ID is for single records, while the other options are not valid action names in Power Automate.

Answer

List records

Answer

RetrieveMultiple

Answer

Get a row by ID

Question 9

You are designing a Dataverse solution for a real estate agency. The agency needs to track properties and the agents who list them. Each property can have only one listing agent, but an agent can list many properties. You create a table named Property and a table named Agent. You need to establish the relationship so that when an agent is deleted, their listed properties remain but the Listing Agent column is cleared. Which relationship type and behavior should you configure?

Accepted Answer

One-to-many relationship with Referential, Remove Link behavior on the Agent side.. The scenario requires a one-to-many relationship where deleting the parent (Agent) does not delete the child (Property) but clears the lookup. Referential, Remove Link achieves this by setting the referencing column to null. Other behaviors either restrict deletion or cascade delete, neither of which meets the business requirement.

Answer

One-to-many relationship with Referential, Restrict Delete behavior on the Agent side.

Answer

One-to-many relationship with Parental behavior on the Agent side.

Answer

Many-to-many relationship with Referential, Restrict Delete behavior.

Question 10

You are creating a new custom table in Dataverse to store customer feedback. You need to ensure that each feedback record is associated with a specific account. Which type of column should you add to the feedback table to create this association?

Accepted Answer

A lookup column.. A lookup column is used to create a relationship between two tables, specifically a many-to-one relationship. In this scenario, adding a lookup column to the feedback table that targets the account table allows each feedback record to be associated with one account. This is the standard Dataverse mechanism for relating records across tables, and it supports referential integrity and navigation.

Answer

A currency column.

Answer

A choice column.

Answer

A text column.

Question 11

You are designing a Dataverse data model for a field service application. A dispatcher must be able to assign a work order to exactly one technician, but a technician can be assigned many work orders over time. The work order table already exists and the technician table already exists. You need to add the relationship that enforces this business rule with the least administrative effort. What should you create?

Accepted Answer

A one-to-many relationship from the technician table to the work order table, with a lookup column on the work order table.. The business rule describes classic one-to-many cardinality: one technician is associated with many work orders, and each work order carries a single technician reference. Modeling it as a one-to-many relationship anchored on the technician table and adding the lookup on the work order table satisfies the rule directly. Many-to-many and reversed or self-referential designs either permit invalid assignments or cannot span the two tables.

Answer

A self-referential relationship on the work order table that links each work order to its assigned technician record.

Answer

A one-to-many relationship from the work order table to the technician table, with a lookup column on the technician table.

Answer

A many-to-many relationship between the technician table and the work order table using an intersect table.

Question 12

You are designing a Dataverse solution for a hospital. You need to track patient visits and the medications prescribed during each visit. A visit can have multiple medications, and a medication can be prescribed in multiple visits. You also need to store the dosage and frequency for each medication prescribed in a visit. What is the most appropriate way to model this relationship?

Accepted Answer

Create a new table called 'Prescription' with a many-to-one relationship to Visit and a many-to-one relationship to Medication. Add columns for dosage and frequency to the Prescription table.. The correct solution is to create an intersect table (Prescription) with many-to-one relationships to both Visit and Medication, and place the dosage and frequency columns on that intersect table. This captures the many-to-many relationship and allows unique attributes for each association. The other options either misplace the attributes or use an incorrect relationship type.

Answer

Create a many-to-many relationship between Visit and Medication, and add custom columns for dosage and frequency on the Visit table.

Answer

Create a many-to-many relationship between Visit and Medication, and add custom columns for dosage and frequency on the Medication table.

Answer

Create a one-to-many relationship from Visit to Medication, and add columns for dosage and frequency on the Visit table.

Question 13

You need to enforce that a custom table named Project has a unique project code. The project code is entered by users and must be unique across all records. You also want to ensure that the uniqueness check is performed server-side to prevent duplicates from any client. What should you do?

Accepted Answer

Configure an alternate key on the project code column.. Alternate keys are the Dataverse feature designed to enforce uniqueness on columns. They create a unique index on the specified column(s) and are enforced server-side, preventing duplicates from any client. This is a declarative, low-code solution that avoids custom code and ensures data integrity across all entry points.

Answer

Create a calculated column that concatenates the project code with the record ID.

Answer

Write a plug-in that queries for existing project codes and throws an exception if a duplicate is found.

Answer

Create a business rule that checks for duplicate project codes and shows an error message.

Question 14

You are configuring a new custom table in Dataverse to store project tasks. You need to ensure that the table supports attachments, allows users to add notes, and tracks when records are created and modified. Which two actions should you perform? (Choose two.)

Accepted Answer

Enable the 'Attachments' option in the table properties.. To support attachments and notes, you must enable the 'Attachments' and 'Notes' options in the table properties. These are specific table-level settings that control whether users can attach files and add annotations. System columns like 'Created On' and 'Modified By' are automatically included and do not require manual addition.

Answer

Configure the table to use a custom primary key.

Answer

Add a 'Created On' column to the table.

Answer

Add a 'Modified By' column to the table.

Question 15

A company stores customer feedback in a Dataverse table named Feedback. Analysts frequently run reports filtered by the date the feedback was submitted, and they also sort by that date. The column currently stores the value as a single line of text, which forces slow client-side filtering. You need the column to support efficient server-side filtering, sorting, and date range queries. What should you do?

Accepted Answer

Create a new Date and Time column, migrate the feedback dates into it, and update views and forms to use the new column.. Server-side filtering and sorting on dates requires the column to be a native Date and Time type, because only then does Dataverse store and index the value in a queryable temporal format. Since existing column types cannot be converted in place, the practical answer is to introduce a correctly typed date column, migrate the values, and update the consuming views and forms. Calculated and rollup columns do not convert stored text into efficient date storage.

Answer

Change the column data type to Date and Time and keep the existing values.

Answer

Add a calculated column that parses the text value into a date at query time for each report.

Answer

Create a rollup column that aggregates the text dates and exposes them for filtering in reports.