AB-410 Building Intelligent Applications Questions and Answers

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

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

The runtime instructions should be stored in an AI Builder custom prompt. A custom prompt is the managed component that holds the company’s directions for tone, structure, required fields, inputs, and expected output. The same prompt can be invoked by Prompt controls on forms for different tables, provided the inputs are designed generically or mapped appropriately. A Power Platform AI model represents a model capability, but it is not the artifact used to store these scenario-specific natural-language instructions. A Dataverse prompt column applies generation to a table column; the question requires reusable instructions for controls across multiple tables, not a separate generated column definition. A business rule is deterministic logic and cannot store or execute generative instructions. The prompt should be solution aware, versioned through ALM, tested with representative records, and restricted to approved grounding data. The Study Guide explicitly measures the ability to “build prompts,” “add inputs to a prompt,” and consume prompts in apps. An AI Builder custom prompt is therefore the reusable instruction asset that the Prompt controls should call at runtime.

Study Guide reference/topic: “Create prompts and models in AI Hub — Build prompts.” 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 Microsoft Dataverse trigger “When a row is added, modified or deleted” is the correct trigger because the flow must run automatically whenever the Account Number field changes. The trigger can be configured for the Modified change type, the Account table, and an appropriate scope. Its Select columns or filtering-attributes setting should identify the account-number column so unrelated row updates do not start the validation flow. A trigger condition can further prevent work when the value is blank or already normalized. “When a row is selected” is an instant, user-initiated trigger and does not run automatically. A business-process-flow step only runs when that step is explicitly invoked. “When an action is performed” responds to a defined Dataverse action rather than a standard column modification. The correction logic should also avoid recursively retriggering itself when it updates the formatted value, for example by comparing the existing and normalized values before writing. The Study Guide explicitly lists “recommend cloud flow triggers.” Option D is the only event trigger that directly observes Dataverse row modification and can be narrowed to the required field.

Study Guide reference/topic: “Create cloud flows — Recommend cloud flow triggers.” AB-410 Study Guide | Microsoft Learn technical reference

JavaScript is the correct solution because model-driven app client scripting can respond to form and column events and change control properties while the form is open. An OnChange handler can evaluate the current value and call supported client API methods to set a control visible or hidden, enabled or disabled, or otherwise update the form experience without waiting for a server process. The script should be packaged as a JavaScript web resource, added to the form library, and registered against the appropriate event with the execution context passed to the handler. It should use formContext rather than deprecated global APIs and include null and error handling. This meets the real-time requirement directly. The answer does not imply that code should always be preferred: a business rule is better for supported declarative actions, but the series specifically identifies JavaScript as the complete dynamic show/hide implementation. Power Automate remains unsuitable for immediate UI manipulation. The Study Guide objective “evaluate use cases for business logic” requires choosing between declarative rules, client scripting, and automation based on where and when the logic must run.

Study Guide reference/topic: “Implement business and process logic — Evaluate use cases for business logic.” AB-410 Study Guide | Microsoft Learn technical reference

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

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

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

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