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

Business Type rule — Table scope; Account rating re-evaluation rule — Specific form scope

The Business Type rule should use Table scope because it must apply to the data regardless of which form or app is used, including the canvas app. Table-scoped business rules execute at the table level for supported operations and are not tied to one model-driven form. The account-rating recommendation is explicitly limited to one model-driven app form, so Specific form scope is the correct choice. This prevents the recommendation from appearing on other account forms that serve different processes. All forms would be broader than necessary because it applies the client-side rule to every main form for the table. The maker should confirm that the selected actions are supported at the chosen scope; not every form action is available at table scope. The original requirement to set Business Type based on customer size is data logic, whereas the rating recommendation is presentation guidance in a particular experience. The Study Guide explicitly lists “configure business rules.” The verified mapping applies the narrowest effective scope: Table for reusable cross-app data behavior and Specific form for the app-limited recommendation.

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

Security-role-based view access and view filters address different parts of the record-display problem. A view filter constrains the rows returned—for example, Status equals Active and Owner equals Current User—so inactive or unrelated accounts do not appear. Security roles can restrict which public views are available to particular audiences, preventing users from selecting a broader view that was not designed for them. Defining view columns only changes which fields are shown; it does not reduce the number of records. App settings do not provide the row-specific query criteria. Configuring a status column supplies data that a filter can test but does not itself filter the view. Dataverse row-level privileges remain the security boundary: a filtered view improves relevance but should not be treated as protection against access through another query or API. The role should therefore also implement the intended record access depth. The AB-410 Study Guide covers “create and configure views,” “configure access to forms and views,” and “configure security.” Options C and E combine audience-appropriate view availability with the query criteria needed to show the relevant records.

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