Microsoft AB-410 - Building Intelligent Applications

A cloud flow added to a canvas app exposes a Run method in Power Fx. Calling FlowName.Run from the Submit button ' s OnSelect property starts the flow as a direct result of the user ' s selection and allows the app to pass any required incident values. SubmitForm submits a form control to its data source; it does not by itself invoke an arbitrary cloud flow. OnVisible runs when a screen becomes visible and could trigger duplicate or unintended notifications unrelated to a successful user submission. Launch opens a URL and is not the function for calling a flow. If the notification must occur only after the incident row is successfully saved, a stronger design is to call SubmitForm in OnSelect and invoke the flow from the form ' s OnSuccess property using Run, but that exact combination is not offered. For the choices given, option A is the required native flow invocation. Microsoft documents adding a flow to a canvas app and calling its Run function from a control formula.

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.

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.

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

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.

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

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 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