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

Both Formula and Calculated columns can expose a value derived from other Dataverse data without requiring users to store and maintain the result manually. A formula column uses Power Fx and is evaluated from its referenced columns when the value is retrieved. This is suitable for calculating order age from Created On and the current date, subject to the supported Power Fx functions and data types. A classic calculated column also derives its read-only value from a defined expression and can use date-difference functions for an age calculation. BigInt is a stored numeric data type; it would require another process to keep the value current. A Prompt column generates AI content and is unrelated to a deterministic elapsed-time calculation. The important design distinction is that a dynamic age should not be written as ordinary row data, because it becomes stale as time passes. Formula or calculated behavior keeps the displayed result tied to the source expression. The AB-410 Study Guide expressly lists “configure calculated, rollup, and formula columns,” making A and B the two relevant low-code column types.

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

A global variable is appropriate for a selected scalar value that must remain available while the user moves between screens. It is created with Set and can be referenced anywhere in the canvas app for the remainder of the session unless changed. A collection is an in-memory table, so it is the correct component for holding multiple rows and columns of tabular data that controls such as galleries can consume. Context variables are scoped to a screen and would not reliably satisfy the cross-screen requirement. A data source is an external system or table rather than an application-state container; connecting to one does not itself preserve a temporary selection or session table. The maker should avoid duplicating authoritative data in a collection unless offline or transformation behavior requires it, and should clear sensitive session state when appropriate. For large datasets, delegable source queries are preferable to indiscriminate collection loading. The Study Guide’s exact canvas-app objective is “manage variables and collections.” Options A and D match the required tabular and application-wide scalar state types.

Study Guide reference/topic: “Create canvas apps — Manage variables and collections.” AB-410 Study Guide | Microsoft Learn technical reference

Parental relationship behavior is required because ownership changes on the parent must cascade to all related child rows. In a one-to-many Dataverse relationship, Parental behavior treats the child records as dependent on the parent for supported cascading operations. When the Assign action changes the owner of the parent row, the related child rows are assigned to that new owner as part of the platform operation. Referential behavior preserves the link but does not provide the required assign cascade. Referential, Restrict Delete changes deletion behavior and still does not cause child ownership to follow the parent. “Restrict” by itself is not the relationship behavior option that implements the assignment requirement. Before applying Parental behavior, the designer should confirm that cascading other actions—especially delete, share, unshare, and reparent—matches the business rules, because Parental establishes a broader dependent-record model. If only selected actions should cascade, a configurable cascading relationship is preferable. Under the options supplied, Parental is the only complete answer. The Study Guide specifically measures the ability to “configure table relationships,” which includes selecting cascade behavior based on ownership and lifecycle requirements.

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

Country/region population — Power Automate flow; Passport expiration visibility — Business rule

The Country/region population should use a Power Automate flow, while passport-expiration visibility should use a business rule. A flow triggered by the row change can inspect the selected language values, set US when English is present, and leave Country/region blank when Other is selected. The passport requirement is ordinary form behavior: when Passport ownership equals Yes, a business rule can show the expiration-date control; otherwise it can hide it. That gives immediate client-side feedback with minimal code. The original embedded answer image assigns both requirements to business rules; it is preserved unchanged, but the verified first mapping is Power Automate flow. The flow must avoid a trigger loop by filtering changed columns or checking whether an update is necessary. The Study Guide covers business rules, cloud-flow triggers, and business-logic use-case evaluation. The corrected mapping respects both feature support and execution timing.

Study Guide reference/topic: “Implement business and process logic — Configure business rules and flows.” AB-410 Study Guide | Microsoft Learn technical reference

Build and validate new features — Sandbox; Host stable workloads — Production

A Sandbox environment is appropriate for building and validating new features. It supports development and testing activities while isolating unfinished work from operational users and production data. It can be reset, copied, placed in administration mode, or otherwise managed for lifecycle work without treating it as the stable system of record. A Production environment is intended to host the approved business workload, with controlled access, monitoring, backup, and managed solution deployment. The Default environment is automatically available to users in a tenant and is not the recommended controlled development or enterprise-production boundary. A Developer environment is designed for an individual maker rather than the shared development team described in the scenario. Security groups can restrict membership, but the environment type still needs to reflect its lifecycle purpose. The team should also use solutions and deployment pipelines so validation occurs before production import. The AB-410 Study Guide explicitly asks candidates to “recommend environment types” and “apply a Microsoft Power Platform solution and ALM strategy.” Sandbox for build/validation and Production for stable workloads is the aligned environment architecture.

Study Guide reference/topic: “Design Power Platform solutions — Recommend environment types.” 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

A global choice provides one centrally maintained option set that multiple Dataverse columns can reference. This directly satisfies the requirement that Priority must be added to several tables and that a newly added option must become available automatically wherever the shared choice is used. Microsoft’s Dataverse documentation states that columns can refer to a “common set of global options.” Maintaining the values centrally prevents separate Priority columns from drifting out of synchronization.

A local choice is defined specifically for one column. Adding a value to one local choice would not update corresponding columns on other tables. Status reason is tied to a row’s active or inactive state and is unsuitable for general priority classification. A formula column calculates a value; it does not provide a centrally managed, user-selectable list.

Because users must select one value, the column should be a single-select Choice referencing the global Priority choice, not a multi-select Choices column.