Continue until status is Complete — Do until; Process the fixed retrieved list — Apply to each

Do until is the correct loop when processing must continue until a runtime condition becomes true. The flow can recheck the status and repeat its actions until Status equals Complete, subject to configured count and timeout limits. Because the condition is reevaluated between iterations, it can respond to a status change that occurs while the flow is running. Apply to each is correct for the fixed array of records retrieved at the beginning. It enumerates each item in that array once; records added to the source later are not automatically inserted into the already obtained collection. Scope groups actions for error handling or organization but does not implement either iteration pattern. Concurrency settings affect parallelism and ordering within a loop but do not replace the loop itself. The Do until design should include a delay or appropriate polling interval and explicit termination safeguards to avoid excessive requests. Apply to each concurrency should be chosen according to ordering and connector limits. The Study Guide’s cloud-flow objectives include “implement flow control with conditions and loops.” The verified mapping matches a condition-driven loop and a collection-driven loop to their intended behaviors.

Study Guide reference/topic: “Create cloud flows — Implement flow control with loops.” AB-410 Study Guide | Microsoft Learn technical reference

A system chart is the native model-driven app visualization for aggregated Dataverse data and can be displayed alongside the rows in a selected view. The chart can group, count, sum, or otherwise aggregate supported columns and updates as the view or filters change. This directly meets the requirement for managers to compare a visual representation with the corresponding list of records inside the app. A Power BI semantic model can support richer analytics, but it adds an external analytical layer and is not necessary for the stated in-app chart requirement. App navigation determines where pages and tables appear, while general app settings do not create a visualization. The maker should create the chart for the appropriate table, choose the category and series fields, add the chart to the app, publish, and verify that managers have access to the underlying rows and columns. Microsoft Learn lists model-driven app charts and dashboards within the AB-410 create-intelligent-applications domain.

Revenue changes month over month: Line. Proportion by status: Pie. Progression through sales stages: Funnel.

A line chart is designed to show a measure across an ordered time axis, so monthly total opportunity revenue should be plotted as a line to reveal direction, increases, decreases, and trend continuity. A pie chart shows each status category as a share of the selected whole, making it suitable for the proportion of opportunities by status in the current view. A funnel chart represents progressive stages in a process and makes drop-off between sales stages visible. Charts should use an appropriate aggregate, such as Sum of Estimated Revenue for the time series and Count of Opportunities for the status and stage views. The maker must also confirm that the chart is added to the model-driven app and that users have access to the underlying data. Microsoft documents line, pie, and funnel chart types for model-driven app visualizations.

The view should be assigned to the manager security role. The requirement is not to remove access to the underlying table; it is to limit one public view that exposes a sensitive arrangement of columns and filters. Role-based public-view access allows the maker to associate the view with the manager role so it appears for managers but not for users whose roles are excluded. Table privileges are too broad because they govern operations on table rows and would affect every form, view, and app experience that uses the table. Removing the view from navigation does not prevent users from selecting it elsewhere in the model-driven app, and the Quick Find view controls search-result presentation rather than access to a particular public view. The solution should still confirm that sensitive columns have appropriate column-level security if their values must be protected independently of the view. For the stated visibility requirement, however, the targeted control is the view’s role assignment. This maps directly to the AB-410 objective “configure access to forms and views for model-driven apps.”

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

Each prefix contains five characters: P, O, S, the system digit, and the hyphen. TRIMLEFT(Number, 5) removes those five leading characters and returns the remaining clean order number. For example, POS1-78421 becomes 78421, and POS2-78421 produces the same clean value. Removing four characters would leave the hyphen, while TRIMRIGHT would remove characters from the actual order number rather than the source-system prefix. CONCAT adds text and cannot perform the required cleanup. Because the source integration already guarantees one of the two fixed prefixes, the calculated expression can apply the same length consistently. Production design should still consider null values, unexpected prefixes, and maximum output length so malformed integrations do not produce misleading results. The result is derived rather than manually maintained, which prevents divergence between Number and the clean-number column. The AB-410 Study Guide explicitly includes “configure calculated, rollup, and formula columns.” Option C applies the calculated-text function that matches the exact prefix structure.

Study Guide reference/topic: “Implement business and process logic — Configure calculated, rollup, and formula columns.” AB-410 Study Guide | Microsoft Learn technical reference

Logical navigation groupings — Customize the site map; Required tables in navigation — Add tables to app designer

The site map organizes a model-driven app’s navigation into areas, groups, and subareas, so customizing it is the action that creates logical business-process groupings. Tables and other pages are exposed through those subareas. To ensure that only required table data is included, the maker adds the selected tables to the app in the app designer and omits unrelated tables. Configuring app settings changes runtime features and behavior but does not define the navigation hierarchy. App properties hold metadata such as name, description, or icon and likewise do not select the operational data components. The final app should be validated for dependencies because adding a table can also require forms, views, charts, and security-role privileges. Navigation visibility does not itself grant data access; users still need the relevant Dataverse permissions. The Study Guide’s model-driven app objectives include “compose a model-driven app” and configure its forms, views, and access. The correct mapping therefore uses the site map for information architecture and the app designer’s table selection for component inclusion.

Study Guide reference/topic: “Create model-driven apps — Compose a model-driven app.” AB-410 Study Guide | Microsoft Learn technical reference

Assigning the appropriate security roles is the complete action because model-driven app access and Dataverse data access are both role driven. The app must be shared with the role, and the role must grant the accounting team the table privileges required to read and create or update the financial records. Configuring app visibility privileges alone may make the app tile appear, but it does not establish the underlying table rights. Setting an app as default affects navigation or launch preference and does not grant access. Granting table-level permissions is only one part of the required configuration and, in Dataverse, those privileges are normally delivered through a security role; option C represents the combined mechanism expected by the question. The administrator should use least privilege, choose the correct access depth, and include privileges for dependent tables and processes used by the app. Existing visibility in the launcher is not proof of effective authorization. The AB-410 Study Guide includes both “configure access to model-driven apps” and “configure security.” Appropriate role assignment aligns the user, the shared app, and the table operations in one enforceable access model.

Study Guide reference/topic: “Create model-driven apps — Configure access to model-driven apps.” AB-410 Study Guide | Microsoft Learn technical reference

Get a row by ID (Dataverse) → Initialize the variable → Set the variable → Send an email

The flow first retrieves the customer with Get a row by ID so the email value is available as dynamic content. It then initializes a string variable, sets that variable to the retrieved email address, and uses the variable in the Send an email action. Initialization must occur before Set, while retrieval may occur before or after initialization; the question acknowledges that more than one valid order exists. The displayed sequence is therefore valid: Get row, Initialize, Set, Send. Append to a string variable is unnecessary because only one email value is stored, and appending can unintentionally retain or concatenate content in a loop. The variable should use a clear name and the email action should handle an empty address before attempting delivery. If the value is used only once, direct dynamic content could be simpler, but the requirement explicitly asks to store it for later use. The Study Guide covers “configure cloud flow actions.” This sequence establishes the source value, creates the storage container, assigns the value, and consumes it in dependency order.

Study Guide reference/topic: “Create cloud flows — Configure cloud flow actions.” 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

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.