AB-410 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 approval must use Custom Responses — Wait for one response because the possible outcomes are Approved, Rejected, or Escalated. The standard Approve/Reject type cannot represent the required escalation response. Multiple approvers should be entered in a single approval action so the request is distributed consistently while the action completes after the first response, as required. After the approval returns, a Condition evaluates the selected response and sends the correct confirmation email or escalation path. Creating separate approval actions in parallel would complicate cancellation and could allow several independent outcomes after the business decision has already been reached. The flow should record the responder and outcome and ensure the condition accounts for the exact custom response labels. The AB-410 Study Guide explicitly covers “manage approvals by using cloud flows,” “configure cloud flow actions,” and conditions. These three settings implement the response model, multi-approver distribution, and post-decision processing without waiting for remaining approvers.

Study Guide reference/topic: “Create cloud flows — Manage approvals.” 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 maker should define a prompt that references the support-case fields and create the destination column with the Prompt data type. The prompt contains the instructions for producing the case summary and declares the record inputs needed to ground that output. The prompt column then makes the generated summary available in the Dataverse/model-driven app context for the current row. A formula column performs deterministic Power Fx computation and cannot generate a natural-language summary from multiple fields. A business rule can set or validate values, but it does not invoke a generative model. The prompt should limit inputs to the approved columns, specify the required structure, and handle empty or contradictory case data so the generated content remains useful. Security on the source fields must still be respected, because an AI-generated summary must not become a route around restricted data. The AB-410 Study Guide lists “configure prompt columns” under Build data models and “add inputs to a prompt” under AI Hub. Options A and D supply the instruction definition and the Dataverse column behavior required for record-context generation.

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

The solution requires an AI Builder prompt, a cloud flow, and a Dataverse table. The prompt performs the autonomous semantic analysis of each feedback item, including sentiment or other instructed classifications. The cloud flow supplies the event-driven orchestration: it retrieves new feedback, calls the prompt, interprets the result, writes the output, and branches to an escalation action when sentiment is negative. Dataverse provides persistent, queryable storage for the original feedback, model result, status, and reporting fields. A canvas app may be useful for reviewing results but is not required for autonomous execution. A business rule can validate or adjust Dataverse data but cannot independently call the generative model and orchestrate external escalation. The flow should include explicit failure handling, confidence or result validation, and an idempotent design so retries do not create duplicate escalations. Approved data policies must also permit the connectors used by the flow. The Study Guide covers “consume a prompt in cloud flows,” “configure cloud flow actions,” and the creation of Dataverse-backed business solutions. A, B, and E form the complete analysis, automation, and persistence architecture.

Study Guide reference/topic: “Create cloud flows; Create prompts and models in AI Hub.” 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

Changing the username directly in the app’s Dataverse user record does not meet the goal. The application user entry is synchronized from Microsoft Entra ID and is not the authoritative place to change a person’s sign-in identity. A direct modification may be blocked, overwritten by synchronization, or leave the tenant sign-in name unchanged. The correct operation is to update the existing user account in Microsoft 365 or Microsoft Entra administration so the same directory object is retained and its new user principal name flows into the Power Platform environment. Retaining the object identity is what protects ownership and application history. The spelling difference in the proposed “Elizabeth” record also creates an additional risk of modifying the wrong identity. After the tenant update, administrators should verify synchronization and mailbox approval without creating a replacement user. The AB-410 profile expects collaboration with identity administrators for “roles, identity, and authentication,” and the data-model objective includes “configure security.” Because the proposed app-record edit bypasses the identity source, the answer is No.

Study Guide reference/topic: “Build data models — Configure security.” 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