AB-410 Practice Test 2 — 10 Questions

Question 1

A Power Platform administrator needs to allow users in a specific department to create and edit records in a custom table, but they should not be able to delete any records. The department users already have a security role with Read and Write privileges on the table. Which security role privilege should you modify?

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

Accepted Answer

Delete. Deletion of records is controlled by the Delete privilege in a security role. To prevent deletion while allowing create and edit, you must ensure the role lacks Delete permission on that table. The other privileges affect reading, updating, or associating records, not removal.

Answer

Append To

Answer

Read

Answer

Write

Question 2

What is the primary role of a 'Security Role' in Dataverse?

Accepted Answer

To define data access privileges. A Security Role in Dataverse defines the privileges a user or team has on tables, records, and other resources — essentially, it controls data access. Security roles specify Create, Read, Write, Delete, Append, Append To, Assign, and Share privileges at the table level, and the scope (User, Business Unit, Parent: Child Business Unit, Organization) determines which records the user can access. This is the primary role of a security role.

Answer

To route work items

Answer

To manage app branding

Answer

To define user authentication

Question 3

You are creating a Dataverse table for a real estate application. You need to store a list of property features for each listing, such as 'Pool', 'Garage', and 'Fireplace'. Each listing can have multiple features, and you want to easily filter listings by a specific feature. The features are chosen from a predefined list of 20 options. Which column type should you use?

Accepted Answer

Multi-select Choice. The need is to store multiple predefined features per record and filter by them. A Multi-select Choice column is purpose-built for this: it allows selecting multiple options from a single global or local choice list, and it supports querying with the contains operator. Other column types either cannot store multiple values, lack validation, or introduce unnecessary complexity.

Answer

Lookup

Answer

Choice

Answer

Text

Question 4

A team is building an app on Dataverse. They need to record the moment a support ticket is escalated so that downstream automations can trigger on that event, and they want the value captured automatically without the user entering it. They also want the value to remain unchanged if the ticket is later edited. Which column type best fits this requirement?

Accepted Answer

A Date and Time column named Escalated On that is set by a business rule or Power Automate flow when the escalation status changes.. The requirement is to capture the escalation moment automatically and then freeze that value. A Date and Time column populated by a business rule or Power Automate flow at the moment the escalation status changes does exactly that. A creation-time default captures the wrong event, a calculated column cannot reference the clock at an arbitrary time and recalculates on edits, and storing ticks in a number column loses native date behavior.

Answer

A calculated column that returns the current date and time whenever the escalated flag is true.

Answer

A whole number column that stores a timestamp value converted to ticks by the client application.

Answer

A Date and Time column with a default value of the current date and time.

Question 5

You have a business rule that runs on a form. It sets a field to mandatory. Can this be bypassed?

Accepted Answer

Yes, because it is client-side logic. Business rules that run on a form execute as client-side JavaScript in the browser (or model-driven app client), so they can be bypassed by editing the record through other means — such as the Web API, an import, a plugin, or a different form where the rule is not applied. The rule only enforces the mandatory field at the form UI layer, not at the Dataverse platform layer. This is why the correct answer is that it can be bypassed because it is client-side logic.

Answer

Yes, if the user is an admin

Answer

No, it is enforced at the database level

Answer

No, it is enforced by the app

Question 6

You are designing a Power Automate flow that uses AI Builder to process a batch of documents. You need to handle potential errors when the AI Builder action fails due to unsupported file formats. Which TWO actions or configurations should you implement to ensure robust error handling? (Choose two.)

Accepted Answer

Use a Scope action to group the AI Builder action and configure its run after to handle failures.. To handle errors from unsupported file formats, you should prevent them from reaching the AI Builder action by adding a Condition to check file extensions. Additionally, using a Scope action around the AI Builder action allows you to catch any failures and respond appropriately, such as notifying an admin. These two approaches together provide both proactive and reactive error handling.

Answer

Set the AI Builder action's retry policy to retry on failure.

Answer

Configure the AI Builder action's run after settings to run only on failure and send a notification.

Answer

Enable 'Secure Inputs' on the AI Builder action to prevent errors.

Question 7

You are building a model-driven app for a customer support team. The app uses a custom table called Support Request. You need to configure the app so that users can quickly find requests by priority and see only requests assigned to their team. Which two actions should you perform? (Choose two.)

Accepted Answer

Create a view on the Support Request table that filters by the team and add it to the app.. To let users see only their team's requests, create a filtered view and add it to the app. To let them quickly find requests by priority, enable quick find and include the Priority column in its search configuration. Together these provide both the visibility scope and the search capability required.

Answer

Add a dashboard that shows all Support Request records.

Answer

Create a business rule that sets the Priority field to High when a request is created.

Answer

Add a chart on the Support Request table to display priority distribution.

Question 8

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 9

You have a business requirement to categorize 'Project' records by a 'Status' field. You need to ensure users can only select from a predefined list. Which field type is most appropriate?

Accepted Answer

Choice column. A Choice column stores a predefined set of options (an option set) and restricts user input to those values, which is exactly what is needed to categorize Project records by a Status field with a fixed list. Choice columns can be local (defined per table) or global (shared across tables), and they support single or multi-select.

Answer

Whole Number column

Answer

Text column

Answer

Lookup column

Question 10

You need to group fields together on a form for better readability. What should you use?

Accepted Answer

Section. A Section is a container component on a form that groups related fields under a common heading, improving readability by visually clustering information. It allows you to organize fields into logical blocks, often with a title and collapsible behavior. This is the standard way to group fields on a form in Dynamics 365 and Power Apps model-driven apps. Tabs, columns, and Quick Views serve different purposes and do not provide the same grouping functionality.

Answer

Tab

Answer

Column

Answer

Quick View