Practice Free AB-410 Building Intelligent Applications Exam Questions Answers With Explanation

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

Each prefix contains five characters: P, O, S, the system digit, and the hyphen. TRIMLEFT(Number, 5) removes those five leading characters and returns the remaining clean order number. For example, POS1-78421 becomes 78421, and POS2-78421 produces the same clean value. Removing four characters would leave the hyphen, while TRIMRIGHT would remove characters from the actual order number rather than the source-system prefix. CONCAT adds text and cannot perform the required cleanup. Because the source integration already guarantees one of the two fixed prefixes, the calculated expression can apply the same length consistently. Production design should still consider null values, unexpected prefixes, and maximum output length so malformed integrations do not produce misleading results. The result is derived rather than manually maintained, which prevents divergence between Number and the clean-number column. The AB-410 Study Guide explicitly includes “configure calculated, rollup, and formula columns.” Option C applies the calculated-text function that matches the exact prefix structure.

Study Guide reference/topic: “Implement business and process logic — Configure calculated, rollup, and formula columns.” AB-410 Study Guide | Microsoft Learn technical reference

This is an appropriate custom connector use case. The internal web service is a proprietary API and its actions must be reused across multiple flows. A custom connector centralizes the service’s host, authentication, paths, parameters, request bodies, and response schemas and exposes each operation as a named Power Automate action. Makers can then use a consistent contract rather than rebuilding raw HTTP requests with different headers or payloads in every flow. The connector can be defined from an OpenAPI document or configured manually and should be packaged in a solution with connection references. If the service is reachable only on a private network, an on-premises data gateway or approved network architecture may also be required. Data loss prevention policies should classify the connector appropriately, and changes to the API should be versioned and regression-tested against dependent flows. The Study Guide explicitly measures the ability to “evaluate and recommend connectors.” The combination of a nonstandard internal service and reusable operations is precisely the situation in which the managed abstraction of a custom connector is justified. The answer is Yes.

Study Guide reference/topic: “Create cloud flows — Evaluate and recommend connectors.” AB-410 Study Guide | Microsoft Learn technical reference

The app should remove avoidable retrieval work from App.OnStart, enable supported preloading, and run independent retrieval calls with Concurrent. App.OnStart executes before the user can interact with the app; large or sequential data operations there directly extend startup time. Moving work to named formulas, screen-level loading, or on-demand execution allows the shell to become usable sooner. Preloading prepares supported app resources and data behavior ahead of use, reducing perceived delay where the setting applies. Concurrent evaluates independent formulas at the same time rather than serially, so total wait time approaches the longest individual call instead of the sum of all calls. Moving transformations from the source into Power Fx can reduce delegation and force more records onto the client, which usually harms performance. ClearCollect can cache a bounded dataset, but loading a large dataset into a collection at startup is precisely the pattern the scenario needs to reduce. The corrected answer is B, C, and D. This aligns with the Study Guide objective to design canvas apps for “performance” and with Microsoft guidance to minimize App.OnStart dependencies and parallelize independent operations.

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

The view should be assigned to the manager security role. The requirement is not to remove access to the underlying table; it is to limit one public view that exposes a sensitive arrangement of columns and filters. Role-based public-view access allows the maker to associate the view with the manager role so it appears for managers but not for users whose roles are excluded. Table privileges are too broad because they govern operations on table rows and would affect every form, view, and app experience that uses the table. Removing the view from navigation does not prevent users from selecting it elsewhere in the model-driven app, and the Quick Find view controls search-result presentation rather than access to a particular public view. The solution should still confirm that sensitive columns have appropriate column-level security if their values must be protected independently of the view. For the stated visibility requirement, however, the targeted control is the view’s role assignment. This maps directly to the AB-410 objective “configure access to forms and views for model-driven apps.”

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

Accounts classification — Choice column; Contacts engagement tier — Choice column; Lookup performance and uniqueness — Alternate key

Both classification requirements should use Choice columns. An account classification and a contact engagement tier are controlled categorical values; Choice columns provide a governed option list, validation, labels, and consistent filtering. If the same option set is needed across tables, the maker should define a reusable global choice and reference it from both columns. A Customer column is a special polymorphic lookup that can reference an Account or Contact row; it represents a customer relationship, not a tier or classification. The lookup-performance and uniqueness requirement should use an alternate key. An alternate key creates a Dataverse key definition over selected columns so integrations can identify a row by business data and Dataverse can enforce uniqueness. The original embedded answer image is intentionally preserved, but the Customer-column selection for engagement tier is technically incorrect; the verified selection is Choice column. The Study Guide covers this under “create and modify columns” and “configure table properties.” The final mapping is therefore Choice column for both categorical attributes and Alternate key for the lookup/uniqueness requirement.

Study Guide reference/topic: “Build data models — Create and modify columns; Configure table properties.” AB-410 Study Guide | Microsoft Learn technical reference

The solution should be updated in the development environment and deployed to production as a managed solution. Development is where makers modify unmanaged components, run validation, and prepare a versioned release. The managed package is then imported through the organization’s controlled deployment process. Managed solutions preserve publisher ownership, support upgrades and patches, and can be removed from production when dependencies and data considerations permit. Running Solution Checker is an important validation step, but option B does not include the required deployment mechanism and therefore is not a complete answer. Importing an unmanaged solution into production merges customizations into the active unmanaged layer and makes controlled removal difficult. Editing a customizations file manually bypasses supported maker and ALM processes and introduces avoidable risk. In practice, the release should also be tested in a separate validation environment before production. The AB-410 Study Guide expressly includes “apply a Microsoft Power Platform solution and ALM strategy.” Option A is the only choice that combines an appropriate source environment with the correct production package type and release-control model.

Study Guide reference/topic: “Design Power Platform solutions — Apply a solution and ALM strategy.” AB-410 Study Guide | Microsoft Learn technical reference

Second Patch is protected by error handling: Yes. Notify runs when the Patch succeeds: No. First Patch can fail without triggering Notify: Yes.

The second Patch call is supplied as the formula argument to IfError, so an error raised by that operation is intercepted and the replacement formula containing Notify is evaluated. Notify therefore runs when the protected Patch fails, not when it succeeds. The first Patch statement appears before IfError as an independent formula separated by a semicolon. Because it is outside the IfError expression, its failure is not handled by the displayed Notify branch. Depending on formula-level error-management settings and chaining behavior, execution may stop or continue, but the stated notification is not attached to that first operation. To provide consistent handling, both writes should be placed inside a deliberate IfError structure or each should have its own error branch, and success notification should be placed in the success path. The app can also inspect Errors for data-source details. Microsoft documents IfError as evaluating a replacement formula when an error occurs and Notify as displaying a user message; merely placing Notify after a Patch does not make it a success handler.

The existing AI Builder classification model should be invoked from the canvas app through Power Fx. The maker adds the model as an app data source or AI capability and calls its prediction operation from the relevant user action, passing the current image. The returned classification and confidence can then be stored in variables, displayed to the user, or written to Dataverse. A static formula cannot reproduce a trained image model’s inference. Refining the model with additional images is a training-lifecycle task and may improve quality later, but it does not consume the existing model during the current interaction. Exporting the containing solution transports components between environments; it does not execute a prediction. The app formula should validate that an image is present, handle service errors, and define what happens when confidence is below the accepted threshold. The Study Guide contains the exact objective “consume an AI model in apps.” Option A is the native runtime integration that classifies each user-submitted image during the active canvas-app session.

Study Guide reference/topic: “Create prompts and models in AI Hub — Consume an AI model in apps.” 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

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.

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

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

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.

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.

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.

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.

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.