support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  1. Home
  2. Exams
  3. Microsoft
  4. AB-410

Microsoft AB-410 Exam Prep
Building Intelligent Applications (Page 2 )

Updated On: 20-Aug-2026
Page 2 of 10
PDF with 69 Questions
View Related Case Study

You need to add the Priority column to the Maintenance Request table.
Which column type should you use?

  1. local choice
  2. global choice
  3. status reason
  4. formula

Answer(s): B

Explanation:

The most appropriate column type for storing priorities with these specific values is a global choice (or a local choice if the priority list is completely unique to this table). Between the two choice options, a global choice is generally preferred in Dataverse for standard attributes like priority so that the same definition can be reused consistently across multiple tables (e.g., Tasks, Cases, and Projects).
Scenario: A new column named Priority must be added to multiple tables. Users must be able to select only one option from the following set per row: Low, Medium, High, Critical.


Reference:

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/formula-columns?tabs=type-or-paste



View Related Case Study

DRAG DROP (Drag and Drop is not supported)
You need to configure the Maintenance Request relationships to the other tables.
Which type of relationship behavior should you set? To answer, move the appropriate behavior types to the correct tables. You may use each behavior type 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:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Referential, Restrict Delete If forced to choose the closest standard behavior that ensures the primary safety rule (preventing deletion if a technician is assigned) is met before any deletion happens, Referential, Restrict Delete
Box 2: Referential, Restrict Delete The correct relationship type to use is Referential, Restrict Delete.'
One-to-Many Structure: A technician can have multiple requests, but each request only links to one technician. This requires a standard lookup field on the Maintenance Request table.
Data Integrity: Restrict Delete prevents a technician record from being deleted if they are still assigned to active maintenance requests. This stops your data from becoming orphaned or broken.
Independent Lifecycles: A maintenance request should not be deleted just because a technician leaves the company (which rules out Parental). Historical Tracking: You want to keep the maintenance history intact rather than clearing the technician link blank (which rules out Remove link).
Scenario: Relationship requirements A maintenance request can have only zero or one maintenance report. Only one Technician can be related to a Maintenance Request at a time.
When a Maintenance Request is deleted, any Maintenance Reports associated with it must also be deleted, but this action should be prevented if there is value in the Technician lookup.
When a Maintenance Request is assigned to a different owner, the Maintenance Report associated with it must be reassigned to the new owner as well, but the associated Technician should stay with the current owner.


Reference:

https://learn.microsoft.com/en-us/power-apps/maker/data-platform/data-platform-entity-lookup



View Related Case Study

DRAG DROP (Drag and Drop is not supported)
You need to configure the access requirements to the views.
Which configurations should you use? To answer, move the appropriate configurations to the correct views. You may use each configuration 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:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Security roles To restrict a public view to a specific set of users within the table list view selector, you should use Security roles.
Microsoft Dataverse includes a native feature called role-based system views. This capability allows system administrators and makers to manage public view access directly within the view settings.
Scenario: The Technicians table contains the following public views:
-Senior Technicians
-Junior Technicians
The Senior Technician view must be available through the table list view selector to a set of specific users only.
Box 2: Sharing Sharing is the correct view access configuration to use.
Personal Views: These belong to individual users and cannot be assigned to security roles or business units.
Direct Control: Sharing allows the owner to grant specific permissions to other users or teams without changing record ownership.
Scenario: A tester creates a personal view named Hot Assets on the Assets table. The tester recognizes that the view is useful for the entire testing team. The view must be made accessible to the team.


Reference:

https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/manage-view-access



View Related Case Study

You need to define the alternate key for the Technicians table by using the TechCheck ref column.
Which setting should you apply to the TechCheck ref column?

  1. Required
  2. Searchable
  3. Column security
  4. Auditing

Answer(s): A

Explanation:

This column is required.
Scenario: Contoso Ltd. requires the following table logic: If a user tries to save changes to a Technician row where the TechCheck ref column is empty, the action must be prevented and a message explaining the action must be displayed.



A company uses a model-driven app across multiple departments.
A public view intended only for managers currently exposes sensitive columns and filters to all users.
The view must meet the following requirements:
-Restrict access to the specific public view to managers.
-Display only context-relevant views for other users.
You need to configure view access.
What should you do?

  1. Restrict the view by assigning it to the manager security role.
  2. Configure table-level permissions for managers only.
  3. Remove the view from the app navigation.
  4. Set up the quick find view.

Answer(s): A

Explanation:

To achieve this goal, you should restrict the view by assigning it to the manager security role.
Incorrect: [Not B] Table-level permissions (Security Roles) control access to the data rows themselves, not the user interface components like views.


Reference:

https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/manage-view-access



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?

  1. Referential, Restrict Delete
  2. Referential
  3. Restrict
  4. Parental

Answer(s): D

Explanation:

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.


Reference:

https://learn.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/create-and-edit-1n-relationships



A company tracks order processing duration using a model-driven app.
The company requires a system that provides the following functionality:
-The age of the order, based on the created date, must be displayed on forms and views.
-The value must update dynamically when viewed without storing the result.
-The value must NOT be stored in the database.
You need to configure the column types.
Which two column types should you use? Each correct answer presents part of the solution.
Note: Each correct selection is worth one point.

  1. Formula
  2. Calculated
  3. BigInt
  4. Prompt

Answer(s): A,B

Explanation:

To meet the requirements, you should use Calculated columns or Formula columns.
Formula Columns: This is the modern, recommended approach in Microsoft Power Apps. They use Power Fx to calculate values in real-time when a record is retrieved. They do not store data in the database and work perfectly in both forms and views.
Calculated Columns: This is the legacy feature that performs real-time calculations. Like formula columns, they do not store values in the database for time-dependent calculations (like using NOW() or UTCNOW()) and are supported across views and forms.



DRAG DROP (Drag and Drop is not supported)
You are designing a data model for a company. The model uses only standard Microsoft Dataverse tables.
You must extend the existing Accounts and Contacts tables to support the following business requirements:
-Store an additional classification value on the Accounts table.
-Add a field that indicates a customer’s engagement tier on the Contacts table.
-Create a mechanism to improve lookup performance and ensure uniqueness across selected fields.
You need to modify the tables to support the business requirements.
Which components should you use? To answer, move the appropriate components to the correct requirements. You may use each component 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:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Choice column You should use a Choice column (formerly known as an Option Set). This column type allows you to define a static list of predefined classification values (e.g., "Tier 1", "Tier 2", or "VIP") that users can select from a drop-down menu on the Account table/entity reference (Microsoft Dataverse).
Predefined List: A classification value implies choosing from a fixed, standard set of options (e.g., Gold/Silver/ Bronze or VIP/Standard).
Native Feature: Choice columns allow users to select one or more values from a dropdown menu.
Low Overhead: They do not require creating or maintaining separate tables.
Box 2: Customer column
Box 3: Alternate key You should use an Alternate key.
An alternate key in Microsoft Dataverse allows you to define a unique business key made of one or more columns.
When you create an alternate key, the platform automatically generates a database index to enforce uniqueness and significantly optimize lookup performance.


Reference:

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/define-alternate-keys-entity



  PDF
Viewing page 2 of 10
Viewing questions 9 - 16 out of 69 questions


Post your Comments and Discuss Microsoft AB-410 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!