Pass the Microsoft Microsoft Certified: Dynamics 365 Sales AI Consultant Associate AB-410 Questions and answers with CertsForce

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

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

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

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

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.

Feature: Audit changes to its data. Table: Resident.

Food type and amount are columns on the Resident table, so Dataverse auditing must be enabled for that table and for the two relevant columns. The Audit changes to its data setting records create, update, and delete events and captures the user and time associated with audited changes. This directly supports the requirement to identify who changed the values during the preceding three months. The audit-retention policy should therefore retain records for at least that period. The Feeding table is not the correct target because the scenario explicitly states that food type and amount are stored on each Resident row. A timeline displays activities and notes but does not automatically provide field-level before-and-after history. Audit user access records access events and is not a substitute for auditing data changes. Environment-level auditing must also be enabled before table and column auditing produces history. Microsoft documents that audited changes can be retrieved with Changed By and Created On information, allowing authorized staff to determine who made each modification and when it occurred.

The Adoption Fee column is Currency, while Dataverse formula columns do not produce the Currency data type and do not support direct use of a currency column without conversion. Microsoft requires the Decimal function to convert a currency value into a supported decimal value before it participates in the formula. The correct expression is therefore `Decimal( ' Adoption Fee ' ) * 0.20`, which returns 20 percent of the current fee as a decimal result. Option C applies Decimal after multiplying the currency column, so it still attempts unsupported direct arithmetic on Currency before conversion. Option D omits the required conversion entirely. Option B is not valid Power Fx syntax for multiplying a column by a percentage. The supplied answer C has therefore been corrected to A. The Deposit formula column should use a Decimal Number result with suitable precision, and because formula columns are calculated from current row values, the deposit automatically reflects later changes to Adoption Fee. Microsoft Learn explicitly documents direct currency-column usage through `Decimal(currency column)` and notes that Currency is not a supported formula-column output type.