Free Microsoft AB-410 Practice Exam with Questions & Answers | Set: 2

Maintain history of changes: Enable auditing at the table level. Detect updates externally: Enable change tracking at the table level.

Dataverse auditing records changes so authorized administrators can review the history of operations and changed values. Auditing must be enabled at the environment and table levels, and relevant columns must also participate where detailed column changes are required. Audit retention controls how long those audit records remain but does not enable the history itself. Change tracking serves the integration requirement: it lets an external client retrieve only rows that changed since a prior synchronization token, supporting efficient incremental synchronization instead of repeatedly reading the entire table. Long-term data retention archives operational data and is unrelated to the audit trail. A generic synchronization interval also does not expose Dataverse change tokens. The two properties may be enabled together because they solve different problems—governance history versus integration delta detection. Administrators should plan audit capacity and protect synchronization tokens appropriately. Microsoft documents Dataverse auditing for data-change history and change tracking for synchronizing data with external systems.

Support case to customer — One-to-many; Customer children — One-to-many; Agent assignment history — Connections

Each support case should reference one customer through a many-to-one lookup, which is configured from the customer perspective as a one-to-many relationship: one customer can have many cases. Customer children also require a self-referencing one-to-many relationship, allowing one customer row to be the parent of multiple child customer rows. Historical agent assignments are different. A conventional lookup retains only the current related row unless a separate history table is introduced. Dataverse Connections provide a flexible, role-based association between records and can retain multiple agent-to-customer links over time without redesigning the standard tables. A one-to-one relationship would prevent a customer from having multiple cases or children, and a many-to-many relationship is unnecessary where each case or child has one parent. The designer should define relationship roles and views so users can interpret the connection history consistently. The AB-410 Study Guide includes the exact objective “configure table relationships.” The correct mapping uses one-to-many relationships for structured parent/child data and Connections for the flexible assignment-history requirement.

Study Guide reference/topic: “Build data models — Configure table relationships.” AB-410 Study Guide | Microsoft Learn technical reference

OrderTotal exceeds 1,000: greater(triggerOutputs()?[ ' body/OrderTotal ' ], 1000). CustomerName contains VIP: contains(triggerOutputs()?[ ' body/CustomerName ' ], ' VIP ' ).

The greater expression returns true only when the OrderTotal value is larger than 1,000, which precisely implements the word exceeds. An equals comparison would match only 1,000, and less would reverse the requirement. The contains expression searches the CustomerName string for VIP anywhere within the value, so it can identify names such as VIP Customer or Contoso VIP Account. startsWith would be narrower because it would match only when VIP appears at the beginning. The null-safe question-mark operator in the trigger-output path helps avoid an immediate navigation error when a parent object is missing, although the flow should still consider blank and incorrectly typed values. If customer-name matching must be case-insensitive, normalize both strings with toLower before applying contains. The condition branches can then route the order to approval and flag the record independently. Microsoft documents greater and contains as workflow expression functions used in Power Automate conditions.

The solution requires an AI Builder prompt, a cloud flow, and a Dataverse table. The prompt performs the autonomous semantic analysis of each feedback item, including sentiment or other instructed classifications. The cloud flow supplies the event-driven orchestration: it retrieves new feedback, calls the prompt, interprets the result, writes the output, and branches to an escalation action when sentiment is negative. Dataverse provides persistent, queryable storage for the original feedback, model result, status, and reporting fields. A canvas app may be useful for reviewing results but is not required for autonomous execution. A business rule can validate or adjust Dataverse data but cannot independently call the generative model and orchestrate external escalation. The flow should include explicit failure handling, confidence or result validation, and an idempotent design so retries do not create duplicate escalations. Approved data policies must also permit the connectors used by the flow. The Study Guide covers “consume a prompt in cloud flows,” “configure cloud flow actions,” and the creation of Dataverse-backed business solutions. A, B, and E form the complete analysis, automation, and persistence architecture.

Study Guide reference/topic: “Create cloud flows; Create prompts and models in AI Hub.” AB-410 Study Guide | Microsoft Learn technical reference

LoanApplicant lookup to Contact: N:1. LoanApplicant to LoanApplication: 1:N. Loan or application to one Property: N:1.

A lookup column on LoanApplicant that points to Contact means many LoanApplicant rows can reference one Contact row, so the relationship from LoanApplicant to Contact is many-to-one (N:1). If one applicant can submit more than one application while each application belongs to one applicant, the correct relationship is one-to-many (1:N) from LoanApplicant to LoanApplication. A many-to-many relationship would incorrectly allow one application to belong to multiple applicants unless that is an explicit business requirement. Finally, when each loan or application is associated with one property and a property can be referenced by multiple loan records over time, the loan-side relationship to Property is N:1. Microsoft documents Dataverse 1:N and N:1 relationships as two perspectives of the same lookup relationship.

Maintenance Report — Parental; Technician — Referential, Restrict Delete

The Maintenance Report relationship must use Parental behavior. A report is operationally dependent on its Maintenance Request: deleting the request must delete the related report, and assigning the request to a new owner must also assign the report. Parental behavior supplies cascading behavior for operations such as Assign and Delete, which matches both requirements. The Technician relationship must use Referential, Restrict Delete. The technician is an independent master record and must not be reassigned merely because a maintenance request changes owner. Restrict Delete also protects the related record arrangement where deletion would violate an existing reference. Referential, Remove Link would clear the lookup instead of blocking the relevant deletion, so it does not meet the stated protection requirement. This decision aligns with the AB-410 Study Guide objective “configure table relationships,” including selection of relationship behavior according to ownership and cascade requirements.

Study Guide reference/topic: “Build data models — Configure table relationships.” AB-410 Study Guide | Microsoft Learn technical reference

A global choice provides one centrally maintained option set that multiple Dataverse columns can reference. This directly satisfies the requirement that Priority must be added to several tables and that a newly added option must become available automatically wherever the shared choice is used. Microsoft’s Dataverse documentation states that columns can refer to a “common set of global options.” Maintaining the values centrally prevents separate Priority columns from drifting out of synchronization.

A local choice is defined specifically for one column. Adding a value to one local choice would not update corresponding columns on other tables. Status reason is tied to a row’s active or inactive state and is unsuitable for general priority classification. A formula column calculates a value; it does not provide a centrally managed, user-selectable list.

Because users must select one value, the column should be a single-select Choice referencing the global Priority choice, not a multi-select Choices column.

Senior Technicians — Security roles; Hot Assets — Sharing

The Senior Technicians public view should be restricted by security roles. Public views are solution components and can be included in a model-driven app, but role-based view access is the correct mechanism when only a defined class of users should see the view in the view selector. The relevant manager or senior-technician role is granted access while other roles are excluded, allowing each audience to see context-relevant views without changing table-level data privileges. Hot Assets is a personal view created by an individual tester. Personal views are user-owned artifacts and are made available to colleagues by sharing them with users or teams. Sharing the view with the Testers team is therefore the direct way to make it usable by the whole testing group. Owner teams and business units concern record ownership or security scope; they do not convert a personal view into a shared view by themselves. The AB-410 Study Guide lists “configure access to forms and views for model-driven apps.” These two configurations apply the platform’s distinct access models: role assignment for a public system view and explicit sharing for a user-owned personal view.

Study Guide reference/topic: “Create model-driven apps — Configure access to forms and views.” AB-410 Study Guide | Microsoft Learn technical reference

Business rules and Power Apps component framework controls address the two extensibility requirements while minimizing unnecessary server-side code. A business rule implements supported validation or form/table logic declaratively, making it preferable to a plug-in when the requirement can be satisfied without custom server execution. A Power Apps component framework control packages a reusable custom user-interface component that can be deployed in a solution and used across supported applications. A JavaScript web resource can customize form behavior but is not the preferred reusable control framework for a component with its own rendering and lifecycle. A sitemap controls model-driven app navigation and does not implement either reusable UI or business logic. A plug-in is valid for transactions that require server-side execution, but the case explicitly says to minimize that approach. The AB-410 Study Guide explicitly includes “recommend extensibility options.” Selecting a declarative rule and a PCF control applies that objective to the distinct logic and UI requirements.

Study Guide reference/topic: “Design Power Platform solutions — Recommend extensibility options.” AB-410 Study Guide | Microsoft Learn technical reference

Technician name on one screen — Context variable; Work orders — Collection; Logic statements — Named formula

A context variable should hold the technician’s name because the value is required only on the home screen. Context variables are screen scoped, which limits the state to the place where it is needed and avoids creating wider application dependencies. A collection is the correct structure for work orders because it stores a table of records that a gallery can enumerate, filter, and display. A named formula is appropriate for reusable logic statements that should be calculated consistently without imperatively setting a variable. The original answer image selects a global variable for the technician name, but that scope is broader than required; the image is retained unchanged while the verified mapping uses Context variable. A global variable is appropriate when a scalar value must be available across screens, not when the requirement explicitly limits persistence to one screen. The app should also avoid loading an unnecessarily large work-order collection and should delegate filtering to the data source where possible. The Study Guide directly lists “manage variables and collections” and “named formulas” under Create canvas apps. The verified mapping applies each state mechanism at its intended scope and data shape.

Study Guide reference/topic: “Create canvas apps — Manage variables and collections; Create reusable components.” AB-410 Study Guide | Microsoft Learn technical reference