Microsoft AB-410 Building Intelligent Applications Exam Practice Test

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

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

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

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

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

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 custom connector is required to integrate with the third-party AI service because the integration needs a defined authentication scheme and custom request handling. The connector wraps the service’s API as named operations, with host information, paths, methods, headers, parameters, request bodies, and response schemas. Power Automate or Power Apps can then call those operations through governed connections instead of reconstructing raw requests in every solution. Power Fx is an expression language and does not by itself define or secure an external API contract. Microsoft 365 Copilot chat is a user productivity experience, not a Dataverse integration mechanism. An environment variable can store deployment-specific configuration such as a base URL or identifier, but it neither authenticates nor sends the API request. The connector should be packaged in a solution, use the service’s supported API key or OAuth design, and comply with data loss prevention policies. This directly aligns with the Study Guide cloud-flow objective “evaluate and recommend connectors” and Microsoft’s custom connector architecture.

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

Regional contribution — Stacked column chart; Publish chart in app — Select the chart for the table in app designer; Initial dataset — Set the Default View; Prevent chart switching — Clear Display Chart Selection

A stacked column chart is appropriate because each regional column can display the sales-stage segments that compose the region’s total pipeline, making both overall magnitude and stage contribution visible. A standard column chart would compare separate values but would not show composition in the same bar, while a pie chart does not compare multiple regional totals effectively. The chart must be selected for the Opportunities table in the app designer so it becomes part of the model-driven app package available to users. The dashboard component’s Default View should be set to My Open Opportunities so that dataset loads initially. To prevent runtime chart switching, Display Chart Selection must be cleared; otherwise users can choose another available chart. “Default Chart” determines which chart opens first but does not prevent selection of others. The maker should verify that the chosen view and chart are shared through the app and that users have privileges to the underlying opportunity records. The Study Guide explicitly covers “create and configure model-driven app charts and dashboards.” These four settings govern visualization type, app inclusion, initial data context, and runtime choice independently.

Study Guide reference/topic: “Create model-driven apps — Create and configure charts and dashboards.” AB-410 Study Guide | Microsoft Learn technical reference

Deactivating BPFA prevents the process from being available for new use and removes it from the set of active business process flows users can switch to. Removing all privileges for BPFA is the security-based alternative: users without the required process privileges cannot select or run that process, while other business process flows can remain available according to their own privileges and ordering. Moving BPFA to the bottom of the display order only changes the default or presentation order; it does not prevent a user from switching to it. A business rule operates on table or form data and cannot disable a business process flow definition. The choice between deactivation and privilege removal depends on whether BPFA must be unavailable to everyone or retained for a controlled administrative audience. Existing rows should be reviewed before deactivation so active process instances are handled appropriately. The Study Guide includes “configure business process flows” under Implement business and process logic. Both C and D directly control whether the legacy process can be used, whereas ordering and business rules do not enforce the prohibition.

Study Guide reference/topic: “Implement business and process logic — Configure business process flows.” 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

Updating the active mailbox name under Dynamics 365 email configuration does not change the user’s sign-in name. A mailbox row stores email-processing configuration associated with a user or queue; it is not the authority for Microsoft 365 credentials or the Microsoft Entra user principal name. Changing mailbox details would therefore leave Elisabeth.Rice@contoso.com as the actual identity used for authentication and would not satisfy the legal-name sign-in requirement. The existing Microsoft 365 account must be renamed by an identity administrator so the same directory object is preserved. Dataverse can then synchronize the updated identity while retaining row ownership, security associations, and historical activities. Mailbox settings may need review afterward if the primary SMTP address changes, but that is a follow-up configuration rather than the identity change itself. The Study Guide’s audience profile explicitly describes collaboration with environment and security administrators for identity and authentication, and “configure security” remains part of Build data models. Since the proposed mailbox-only change acts on the wrong component, the correct answer is No.

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

A custom connector is not required because SharePoint Online already has a Microsoft-supported connector. The SharePoint connector exposes triggers for list-item creation or modification and actions such as Get item and Get items for retrieving list data. Authentication and connection management are handled through the standard connector, and its operations participate in environment connection references and data policies. A custom connector is appropriate when no suitable prebuilt connector exists or when proprietary API operations, schemas, and authentication must be exposed. Recreating normal SharePoint list operations as a custom connector would add API definition, testing, governance, and maintenance without adding required capability. The flow should select the standard action that matches whether one item or a filtered collection is needed and should use OData filtering or pagination for larger lists. The AB-410 Study Guide places this decision under “evaluate and recommend connectors.” Because a supported SharePoint connector already meets the requirement, the proposed situation does not make a custom connector necessary. The correct response is No.

Study Guide reference/topic: “Create cloud flows — Evaluate and recommend connectors.” 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