AB-410 Building Intelligent Applications Questions and Answers

The Microsoft 365 administrator should change the user’s sign-in name in the Microsoft 365 or Microsoft Entra administration plane. Dataverse user records are synchronized from the tenant identity, so the authoritative user principal name must be updated at its source. The existing identity object remains the same, preserving its directory object identifier and the corresponding Dataverse system-user relationship. Consequently, record ownership, activity history, audit associations, and security-role assignments are not replaced simply because the sign-in name changes. Administrators should allow synchronization to complete and then verify the updated username and mailbox information in the Power Platform environment. Creating a new user would risk separating the historical record from the new identity and would require reassignment work. The scenario asks for a name change without losing application history, which is precisely why the existing directory account must be modified instead of replacing the Dataverse user. This aligns with the Study Guide’s security and identity collaboration expectations and its “configure security” objective for Dataverse-backed applications. The proposed Microsoft 365 administrator action therefore meets the goal.

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

Parental relationship behavior is required because ownership changes on the parent must cascade to all related child rows. In a one-to-many Dataverse relationship, Parental behavior treats the child records as dependent on the parent for supported cascading operations. When the Assign action changes the owner of the parent row, the related child rows are assigned to that new owner as part of the platform operation. Referential behavior preserves the link but does not provide the required assign cascade. Referential, Restrict Delete changes deletion behavior and still does not cause child ownership to follow the parent. “Restrict” by itself is not the relationship behavior option that implements the assignment requirement. Before applying Parental behavior, the designer should confirm that cascading other actions—especially delete, share, unshare, and reparent—matches the business rules, because Parental establishes a broader dependent-record model. If only selected actions should cascade, a configurable cascading relationship is preferable. Under the options supplied, Parental is the only complete answer. The Study Guide specifically measures the ability to “configure table relationships,” which includes selecting cascade behavior based on ownership and lifecycle requirements.

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

The business rule should use Set requirement level to make the target column Business Required when the stated condition is true. In a model-driven form, this prevents the record from being saved until a value is entered, and the requirement can be returned to Optional when the condition no longer applies. Show recommendation presents advisory guidance that a user may ignore, so it cannot enforce completion. Set field visibility only controls whether a control is displayed. Set default value supplies an initial value but does not guarantee that a valid value remains or that the user cannot clear it. The rule should be scoped to the intended table or form and should include both the true and false paths so requirement level does not remain incorrectly set after values change. If the rule must govern updates through APIs as well as forms, the designer must confirm that the selected scope and action provide server-side enforcement for the scenario. The Study Guide explicitly lists “configure business rules.” Option D is the declarative, no-code action that implements conditional mandatory data entry and blocks the form save until the requirement is satisfied.

Study Guide reference/topic: “Implement business and process logic — Configure business rules.” AB-410 Study Guide | Microsoft Learn technical reference

A Copilot Studio agent and an app assistant agent are the two components designed for contextual, in-app conversational interaction. A Copilot Studio agent can be embedded or made available within the business solution and can use configured knowledge, actions, and conversation topics to answer users while they remain in the application. An app assistant agent is intended to assist users in the context of the model-driven app and its current business data. Business rules execute deterministic form or table logic; they cannot provide a conversational response experience. Smart assist surfaces suggested knowledge articles or similar recommendations in supported customer-service scenarios, but it is not the general conversational component described by the requirements. The implementation must also govern grounding sources and security so an agent cannot reveal records the user is not authorized to access. The AB-410 Study Guide asks candidates to “evaluate built-in agents to include in the business solution” and to integrate Copilot capabilities into model-driven experiences. Those objectives support selecting the two agent-based components rather than validation or recommendation-only features.

Study Guide reference/topic: “Design Power Platform solutions — Evaluate built-in agents.” AB-410 Study Guide | Microsoft Learn technical reference

Continue until status is Complete — Do until; Process the fixed retrieved list — Apply to each

Do until is the correct loop when processing must continue until a runtime condition becomes true. The flow can recheck the status and repeat its actions until Status equals Complete, subject to configured count and timeout limits. Because the condition is reevaluated between iterations, it can respond to a status change that occurs while the flow is running. Apply to each is correct for the fixed array of records retrieved at the beginning. It enumerates each item in that array once; records added to the source later are not automatically inserted into the already obtained collection. Scope groups actions for error handling or organization but does not implement either iteration pattern. Concurrency settings affect parallelism and ordering within a loop but do not replace the loop itself. The Do until design should include a delay or appropriate polling interval and explicit termination safeguards to avoid excessive requests. Apply to each concurrency should be chosen according to ordering and connector limits. The Study Guide’s cloud-flow objectives include “implement flow control with conditions and loops.” The verified mapping matches a condition-driven loop and a collection-driven loop to their intended behaviors.

Study Guide reference/topic: “Create cloud flows — Implement flow control with loops.” AB-410 Study Guide | Microsoft Learn technical reference

Revenue changes month over month: Line. Proportion by status: Pie. Progression through sales stages: Funnel.

A line chart is designed to show a measure across an ordered time axis, so monthly total opportunity revenue should be plotted as a line to reveal direction, increases, decreases, and trend continuity. A pie chart shows each status category as a share of the selected whole, making it suitable for the proportion of opportunities by status in the current view. A funnel chart represents progressive stages in a process and makes drop-off between sales stages visible. Charts should use an appropriate aggregate, such as Sum of Estimated Revenue for the time series and Count of Opportunities for the status and stage views. The maker must also confirm that the chart is added to the model-driven app and that users have access to the underlying data. Microsoft documents line, pie, and funnel chart types for model-driven app visualizations.

1. Edit the Resident form. 2. Add a form component. 3. Select the Dog lookup.

The weight column belongs to the related Dog row, but care staff work from the Resident form. A form component control is designed for this exact model-driven app requirement: it embeds a related table ' s main form and permits users with sufficient privileges to edit that related row without leaving the current record. First edit the Resident main form, because that is where the related Dog information must appear. Next add the Form component from the form designer. Finally bind the component to the Dog lookup on Resident and select the appropriate Dog main form containing the Weight column. Editing the Dog form alone would not place editable Dog fields on the Resident form. A custom code component is unnecessary and would violate the scenario ' s preference for out-of-the-box low-code functionality. The Dog lookup must contain a value before the embedded form can display a record. Care staff also require Read and Write privileges for the Dog table; the form component does not bypass Dataverse security. Microsoft documents this control as allowing direct editing of a related table row from another table ' s main form.

The Adoption Fee column is Currency, while Dataverse formula columns do not produce the Currency data type and do not support direct use of a currency column without conversion. Microsoft requires the Decimal function to convert a currency value into a supported decimal value before it participates in the formula. The correct expression is therefore `Decimal( ' Adoption Fee ' ) * 0.20`, which returns 20 percent of the current fee as a decimal result. Option C applies Decimal after multiplying the currency column, so it still attempts unsupported direct arithmetic on Currency before conversion. Option D omits the required conversion entirely. Option B is not valid Power Fx syntax for multiplying a column by a percentage. The supplied answer C has therefore been corrected to A. The Deposit formula column should use a Decimal Number result with suitable precision, and because formula columns are calculated from current row values, the deposit automatically reflects later changes to Adoption Fee. Microsoft Learn explicitly documents direct currency-column usage through `Decimal(currency column)` and notes that Currency is not a supported formula-column output type.

Feature: Audit changes to its data. Table: Resident.

Food type and amount are columns on the Resident table, so Dataverse auditing must be enabled for that table and for the two relevant columns. The Audit changes to its data setting records create, update, and delete events and captures the user and time associated with audited changes. This directly supports the requirement to identify who changed the values during the preceding three months. The audit-retention policy should therefore retain records for at least that period. The Feeding table is not the correct target because the scenario explicitly states that food type and amount are stored on each Resident row. A timeline displays activities and notes but does not automatically provide field-level before-and-after history. Audit user access records access events and is not a substitute for auditing data changes. Environment-level auditing must also be enabled before table and column auditing produces history. Microsoft documents that audited changes can be retrieved with Changed By and Created On information, allowing authorized staff to determine who made each modification and when it occurred.

Component: Business rule. Condition: Pickup date is more than [Spay or neuter date + 2]. Configure the Show Error Message action on the condition ' s false branch.

A business rule is the correct no-code component because the requirement is synchronous form validation with a visible error that prevents an invalid row from being saved. Configure the rule condition by comparing the Pickup date with the Spay or neuter date plus two days. When the condition is false, use Show Error Message on the Pickup date field to tell the user that pickup is too early. The answer screenshot pairs Business rule with an `If(DateDiff(...))` Power Fx expression, but business-rule conditions are assembled with field, operator, and date-offset operands; they are not authored as a formula-column Power Fx expression. A flow would run after a data event and is unsuitable for immediate form validation. A formula column can calculate a value but cannot itself display the required blocking pop-up. The condition must also handle blank dates and the exact policy boundary: ' no sooner than two days ' means a pickup exactly two days later is permitted. Microsoft documents business rules as supporting conditions, date arithmetic, and Show Error Message actions that prevent saving invalid model-driven app data.

Adopters: None - Organization - None. Dogs: None - Organization - Organization. Residents: None - Organization - Organization.

Care staff must be able to identify adopters for upcoming meetings but must not add or modify adopter information. The Contact or Adopter table therefore requires organization-level Read with no Create or Write. Dogs are organization owned, and staff must view dog information and update the Weight column through the Dog form embedded in Resident. They consequently require organization-level Read and Write but no Create, because only administrative staff may add dogs. Residents are created automatically when a Dog is created, so care staff do not require Create. They do require organization-level Read and Write to view and maintain residency details such as food type and amount.

A business process flow is designed to present a visible sequence of stages and steps on a model-driven app record. The adoption duties naturally form the ordered stages Commitment, Pre-pickup, and Pickup, with the individual signature, deposit, surgery, date, payment, and handoff tasks configured as data steps within those stages. This guides administrative staff through the required order and clearly shows current progress. A business rule performs conditional form logic such as setting values, changing visibility, making fields required, or displaying errors; it does not provide the requested multi-stage duty list and process bar. A business unit is an organizational security boundary and has no role in representing procedural steps. The supplied answer A is therefore incorrect and has been changed to B. The separate date-validation requirement can still be implemented with a business rule while the overall adoption workflow is implemented as the business process flow. Microsoft documents business process flows as a way to ensure users enter data consistently and follow the same stages when completing organizational processes.

Calling the prompt from a Power Automate cloud flow provides a reusable service-level entry point that can be invoked by different Power Platform experiences. The flow can accept parameters from each caller, pass those values into the prompt, and then route the generated result to an app, Dataverse, email, or another process. This addresses reuse more effectively than binding the prompt directly to one canvas app. An input variable is necessary for dynamic data, but by itself it does not establish cross-service orchestration; the flow exposes and manages those inputs for multiple callers. Returning JSON can standardize output handling but does not make the prompt reusable by itself. Direct canvas-app invocation is valid for an app-only requirement, not for the stated need to span Power Platform services. The flow should define explicit input types and validate required values so the case’s inconsistent-input problem is not repeated. The AB-410 Study Guide lists both “add inputs to a prompt” and “consume a prompt in cloud flows.” Option B provides the reusable execution layer while allowing dynamic values to be supplied at runtime.

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

A custom prompt is the native low-code mechanism for generating an inspection report from current app data while following the company’s existing template instructions. The maker can define inputs for the inspection fields, specify required sections, tone, order, and formatting, and invoke the prompt from the new app. This keeps the report-generation experience within Power Platform and minimizes custom AI development. A paginated report is well suited to deterministic, pixel-precise reporting, but it does not perform the requested generative composition and generally presents a separate reporting artifact. A Word template performs deterministic field substitution and is useful when no generative rewriting is required; it does not supply the AI-driven custom narrative described in the case. The prompt should be grounded only with approved inspection data, tested for missing inputs, and reviewed for output consistency before production use. The Study Guide covers “build prompts,” “add inputs to a prompt,” and “consume a prompt in apps.” Option C is therefore the component that directly implements native generative inspection-report creation.

Study Guide reference/topic: “Create prompts and models in AI Hub — Consume a prompt in apps.” AB-410 Study Guide | Microsoft Learn technical reference

The solution should use a prebuilt AI capability where it satisfies the complaint-processing requirement and create the generative prompt from blank for the organization-specific inspection report. Using a prebuilt model minimizes custom model development and training effort, which directly reflects the stated constraint. A blank custom prompt gives the maker control over the inspection template, instructions, inputs, tone, and output format required by the business. Starting from a prompt template can accelerate common scenarios, but the case requires alignment to an existing custom inspection format; a blank prompt avoids carrying irrelevant template assumptions and permits deliberate grounding. Building a custom trained model would add data preparation, training, validation, and lifecycle overhead that the requirement seeks to minimize. The prompt should define required inputs explicitly and be tested with representative data to prevent the inconsistent output problem identified in the case. The Study Guide covers “build prompts from templates or from blank,” “add inputs to a prompt,” and consumption of AI capabilities in apps and flows. Options A and C provide the lowest-custom-development design that still supports the specific generative output.

Study Guide reference/topic: “Create prompts and models in AI Hub — Build prompts and consume AI capabilities.” AB-410 Study Guide | Microsoft Learn technical reference

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

The App access checker requires the individual user as its input, so the new QA tester’s email address is the appropriate value. The checker evaluates why that user can or cannot open a model-driven app by examining app sharing, assigned security roles, licenses, and relevant environment access. A Microsoft Entra security-group name or a Dataverse group-team name is not the subject of the diagnostic; those objects can influence access, but the tool performs its analysis for a specific user identity. The manager’s username is unrelated to the tester’s failure. In this case, group-team membership may be synchronized or evaluated indirectly, and the checker can reveal the effective access result even when the user is not visibly listed as a conventional team member. Administrators should also verify that the environment security group, license assignment, app sharing, and table privileges are aligned. Its content maps to the Study Guide objective “configure access to model-driven apps,” including use of the App access checker for targeted diagnosis.

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

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

TechCheck ref must be configured as Required before it is used as an alternate key. An alternate key is intended to identify a Dataverse row by a stable business value supplied by an external system. Allowing the key column to be empty would defeat the onboarding integration’s requirement that every technician be addressable by the external reference. The case also states that the same TechCheck reference cannot be used on more than one Technician row; the alternate key enforces uniqueness through its Dataverse index after the key is activated. Searchable controls whether the column is available in search experiences, but it does not guarantee that a value is supplied. Column security governs who can read or update a value, and auditing records changes; neither property establishes the required identity. A sound implementation also validates existing data for nulls and duplicates before activating the key, because key creation can fail while invalid rows remain. This is covered by the Study Guide objectives “configure table properties” and “create and modify columns.” Required is therefore the setting that supports a complete, consistently populated external business key.

Study Guide reference/topic: “Build data models — Configure table properties.” 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.