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

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

Security-role-based view access and view filters address different parts of the record-display problem. A view filter constrains the rows returned—for example, Status equals Active and Owner equals Current User—so inactive or unrelated accounts do not appear. Security roles can restrict which public views are available to particular audiences, preventing users from selecting a broader view that was not designed for them. Defining view columns only changes which fields are shown; it does not reduce the number of records. App settings do not provide the row-specific query criteria. Configuring a status column supplies data that a filter can test but does not itself filter the view. Dataverse row-level privileges remain the security boundary: a filtered view improves relevance but should not be treated as protection against access through another query or API. The role should therefore also implement the intended record access depth. The AB-410 Study Guide covers “create and configure views,” “configure access to forms and views,” and “configure security.” Options C and E combine audience-appropriate view availability with the query criteria needed to show the relevant records.

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

401 errors — Reauthenticate connection; Duplicate executions — Enable concurrency control

A 401 response indicates that the connector call is unauthorized, commonly because a connection token expired, credentials changed, consent was revoked, or the connection reference points to an invalid connection. Reauthenticating the connection renews the credential context and is the direct corrective action. Increasing timeout or changing retry policy cannot convert an unauthorized request into an authorized one. Duplicate executions require control over simultaneous flow runs. Enabling trigger concurrency control and setting an appropriate degree of parallelism prevents overlapping instances from processing the same event at the same time. The maker should also examine trigger conditions, polling behavior, and idempotency keys, because concurrency control alone cannot correct every duplicate-trigger design. Adding a delay merely shifts execution time, and retry policy addresses transient action failures rather than independent duplicate runs. After correcting both issues, failed runs should be resubmitted only where the actions are safe to repeat. The Study Guide includes “test and troubleshoot cloud flows.” The mappings target the actual failure classes: restore authentication for 401 errors and govern parallel runs for duplicate execution.

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