Microsoft AB-410 Building Intelligent Applications Exam Practice Test

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

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.

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

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

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.

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.

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.

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

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

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

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

A user-defined function and a component library solve different forms of duplication in the canvas-app estate. A user-defined function centralizes reusable Power Fx logic behind a named, parameterized function, so formulas do not need to be copied and maintained independently. A component library stores reusable canvas components that can be consumed by multiple apps and updated through a controlled component lifecycle. That directly supports the requirement for reusable UI elements across applications. A collection is an in-memory table used during an app session, not a cross-application logic package. A context variable is screen scoped and cannot standardize behavior across apps. A named formula can centralize a reusable calculation within an app, but the question’s paired requirements emphasize reusable logic and reusable UI across multiple applications; the function and component library provide the complete combination. The components should be packaged in solutions and governed through ALM so dependent apps receive tested versions. The Study Guide names “user-defined functions” and “component libraries” within its exact objective to “create reuseable components,” making B and D the aligned selections.

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

Country/region population — Power Automate flow; Passport expiration visibility — Business rule

The Country/region population should use a Power Automate flow, while passport-expiration visibility should use a business rule. A flow triggered by the row change can inspect the selected language values, set US when English is present, and leave Country/region blank when Other is selected. The passport requirement is ordinary form behavior: when Passport ownership equals Yes, a business rule can show the expiration-date control; otherwise it can hide it. That gives immediate client-side feedback with minimal code. The original embedded answer image assigns both requirements to business rules; it is preserved unchanged, but the verified first mapping is Power Automate flow. The flow must avoid a trigger loop by filtering changed columns or checking whether an update is necessary. The Study Guide covers business rules, cloud-flow triggers, and business-logic use-case evaluation. The corrected mapping respects both feature support and execution timing.

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

A Lookup column is designed to reference one row in another Dataverse table. The selected related row’s identifier is stored as part of the relationship, and Dataverse maintains the association so forms, views, queries, and security behaviors can work with it consistently. The requirement explicitly excludes aggregation, which rules out a Rollup column; rollups calculate values such as sum, count, minimum, maximum, or average over related rows. A Calculated column evaluates an expression from other values, while a Formula column uses Power Fx to derive a result. Neither is the correct structural mechanism for selecting and maintaining a single related account or transaction row. The lookup’s relationship should be configured with the appropriate required level, cascade behavior, and delete rule so it matches the record lifecycle. This is not merely a display field: it is a schema-level relationship component. The AB-410 Study Guide lists “create and modify columns” and “configure table relationships” under Build data models. A Lookup column is therefore the only option that natively represents the required one-record association.

Study Guide reference/topic: “Build data models — Create and modify columns.” 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