Microsoft AB-410 Building Intelligent Applications Exam Practice Test

The requirement does not make a custom connector necessary. A one-time, non-reusable REST request can be implemented with an appropriate HTTP action by supplying the endpoint, method, authentication, headers, query parameters, and request body. The response can then be parsed or referenced in that same flow. A custom connector is most valuable when an API must be exposed as reusable, named operations across several flows or apps, when makers need a shared schema and authentication definition, or when governance requires a managed API abstraction. The scenario explicitly states that reuse is not required, so building and maintaining that abstraction would be unnecessary. The designer must still confirm that the HTTP action supports the service’s authentication method, that licensing is available, and that environment data policies allow the endpoint. Those implementation constraints do not change the connector decision given. The Study Guide objective is “evaluate and recommend connectors,” which requires distinguishing a direct HTTP call from a reusable custom connector. Since the proposed one-off call can be made natively, the answer is No.

Study Guide reference/topic: “Create cloud flows — Evaluate and recommend connectors.” 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

Deactivating BPFA prevents the process from being available for new use and removes it from the set of active business process flows users can switch to. Removing all privileges for BPFA is the security-based alternative: users without the required process privileges cannot select or run that process, while other business process flows can remain available according to their own privileges and ordering. Moving BPFA to the bottom of the display order only changes the default or presentation order; it does not prevent a user from switching to it. A business rule operates on table or form data and cannot disable a business process flow definition. The choice between deactivation and privilege removal depends on whether BPFA must be unavailable to everyone or retained for a controlled administrative audience. Existing rows should be reviewed before deactivation so active process instances are handled appropriately. The Study Guide includes “configure business process flows” under Implement business and process logic. Both C and D directly control whether the legacy process can be used, whereas ordering and business rules do not enforce the prohibition.

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

A calculated column is the correct option because it can evaluate a mathematical expression over numerical columns in the same Dataverse row without custom code. Dataverse stores the calculation definition and derives the exposed read-only value from the underlying columns rather than requiring the application to maintain an ordinary stored result. This satisfies the requirement for a dynamic, non-manually persisted value. A business rule would typically set a column value during a create or update event, resulting in stored data that can become stale if the rule does not run for every path. JavaScript operates only in supported client experiences and would not provide a consistent table-level value to all consumers. A dataflow transforms and loads data on a schedule or run; it materializes data rather than evaluating the field whenever accessed. The expression should account for blanks, numeric precision, and supported functions. The Study Guide explicitly lists “configure calculated, rollup, and formula columns.” Under the choices provided, D is the native declarative behavior that matches the calculation, access, storage, and low-code requirements.

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

OrderTotal — greater(triggerOutputs()?['body/OrderTotal'], 1000); CustomerName — contains(triggerOutputs()?['body/CustomerName'] , 'VIP')

The approval condition must use greater(triggerOutputs()?['body/OrderTotal'], 1000) because the requirement is strictly “exceeds 1,000.” equals would match only 1,000, and less would reverse the decision. The VIP test must use contains(triggerOutputs()?['body/CustomerName'] , 'VIP') because the requirement says the name identifies the string anywhere in the value. startsWith would miss names where VIP occurs later, and equals would match only a value consisting entirely of VIP. In production, the maker should confirm the trigger schema and ensure OrderTotal is numeric rather than text; conversion may be required when the source supplies a string. Case sensitivity and null handling should also be tested for customer names. These expressions can be used in Condition actions or trigger conditions depending on whether unwanted runs should be prevented entirely. The Study Guide explicitly includes “implement flow control with conditions and loops.” The two selected functions translate the comparison language precisely: greater for the numeric threshold and contains for substring identification.

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

JavaScript is the correct solution because model-driven app client scripting can respond to form and column events and change control properties while the form is open. An OnChange handler can evaluate the current value and call supported client API methods to set a control visible or hidden, enabled or disabled, or otherwise update the form experience without waiting for a server process. The script should be packaged as a JavaScript web resource, added to the form library, and registered against the appropriate event with the execution context passed to the handler. It should use formContext rather than deprecated global APIs and include null and error handling. This meets the real-time requirement directly. The answer does not imply that code should always be preferred: a business rule is better for supported declarative actions, but the series specifically identifies JavaScript as the complete dynamic show/hide implementation. Power Automate remains unsuitable for immediate UI manipulation. The Study Guide objective “evaluate use cases for business logic” requires choosing between declarative rules, client scripting, and automation based on where and when the logic must run.

Study Guide reference/topic: “Implement business and process logic — Evaluate use cases for business logic.” AB-410 Study Guide | Microsoft Learn technical reference

Disabling the Searchable property for the unwanted address columns removes them from maker-facing query and view design experiences where searchable columns are offered for views, charts, and Advanced Find-style filtering. That directly addresses the requirement that users should not be able to select those columns while creating views and filters. Column-level security is not a metadata-hiding feature: removing Read access protects values at runtime but does not reliably remove the column definition from customization or query interfaces. A business rule can change controls on forms, but it does not govern which columns are available to a view designer. Deleting standard address columns is destructive, can break dependencies, and is unnecessary. The original answer A therefore over-applies data security to what is fundamentally a discoverability/configuration requirement; D is the verified answer. If the values themselves are sensitive, column security may be implemented in addition, but that is a separate requirement. This decision aligns with the AB-410 objectives “create and modify columns” and “configure public views,” particularly the use of column metadata to shape view and filter authoring.

Study Guide reference/topic: “Build data models — Create and modify columns; Configure public views.” AB-410 Study Guide | Microsoft Learn technical reference

Maintenance Report — Parental; Technician — Referential, Restrict Delete

The Maintenance Report relationship must use Parental behavior. A report is operationally dependent on its Maintenance Request: deleting the request must delete the related report, and assigning the request to a new owner must also assign the report. Parental behavior supplies cascading behavior for operations such as Assign and Delete, which matches both requirements. The Technician relationship must use Referential, Restrict Delete. The technician is an independent master record and must not be reassigned merely because a maintenance request changes owner. Restrict Delete also protects the related record arrangement where deletion would violate an existing reference. Referential, Remove Link would clear the lookup instead of blocking the relevant deletion, so it does not meet the stated protection requirement. This decision aligns with the AB-410 Study Guide objective “configure table relationships,” including selection of relationship behavior according to ownership and cascade requirements.

Study Guide reference/topic: “Build data models — Configure table relationships.” AB-410 Study Guide | Microsoft Learn technical reference

Senior Technicians — Security roles; Hot Assets — Sharing

The Senior Technicians public view should be restricted by security roles. Public views are solution components and can be included in a model-driven app, but role-based view access is the correct mechanism when only a defined class of users should see the view in the view selector. The relevant manager or senior-technician role is granted access while other roles are excluded, allowing each audience to see context-relevant views without changing table-level data privileges. Hot Assets is a personal view created by an individual tester. Personal views are user-owned artifacts and are made available to colleagues by sharing them with users or teams. Sharing the view with the Testers team is therefore the direct way to make it usable by the whole testing group. Owner teams and business units concern record ownership or security scope; they do not convert a personal view into a shared view by themselves. The AB-410 Study Guide lists “configure access to forms and views for model-driven apps.” These two configurations apply the platform’s distinct access models: role assignment for a public system view and explicit sharing for a user-owned personal view.

Study Guide reference/topic: “Create model-driven apps — Configure access to forms and views.” 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.

The App access checker requires the individual user as its input, so the new QA tester’s email address is the appropriate value. The checker evaluates why that user can or cannot open a model-driven app by examining app sharing, assigned security roles, licenses, and relevant environment access. A Microsoft Entra security-group name or a Dataverse group-team name is not the subject of the diagnostic; those objects can influence access, but the tool performs its analysis for a specific user identity. The manager’s username is unrelated to the tester’s failure. In this case, group-team membership may be synchronized or evaluated indirectly, and the checker can reveal the effective access result even when the user is not visibly listed as a conventional team member. Administrators should also verify that the environment security group, license assignment, app sharing, and table privileges are aligned. Its content maps to the Study Guide objective “configure access to model-driven apps,” including use of the App access checker for targeted diagnosis.

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

TechCheck ref must be configured as Required before it is used as an alternate key. An alternate key is intended to identify a Dataverse row by a stable business value supplied by an external system. Allowing the key column to be empty would defeat the onboarding integration’s requirement that every technician be addressable by the external reference. The case also states that the same TechCheck reference cannot be used on more than one Technician row; the alternate key enforces uniqueness through its Dataverse index after the key is activated. Searchable controls whether the column is available in search experiences, but it does not guarantee that a value is supplied. Column security governs who can read or update a value, and auditing records changes; neither property establishes the required identity. A sound implementation also validates existing data for nulls and duplicates before activating the key, because key creation can fail while invalid rows remain. This is covered by the Study Guide objectives “configure table properties” and “create and modify columns.” Required is therefore the setting that supports a complete, consistently populated external business key.

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

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