AB-410 Practice Questions

In Microsoft Power Platform architecture, "extensibility requirements" typically refer to scenarios where out-of-the-box configurations are insufficient and pro-code developer solutions are necessary.

A Power Apps component framework (PCF) control (Option E) is the officially supported method for UI extensibility, allowing developers to create custom, reusable visual components that replace standard field or grid visualizations.

A Plugin (Option D) is the standard for backend extensibility. It allows developers to inject custom C# code into the Microsoft Dataverse event pipeline. This ensures that complex business logic and data validation are enforced on the server side, executing reliably regardless of whether the data operation originates from the model-driven app UI, bulk imports, or external API calls.

A. Sitemap: The sitemap is used strictly for defining app navigation and routing configuration, not for implementing custom business logic or custom UI controls.

B. JavaScript web resource: JavaScript executes only on the client-side UI. It cannot enforce complex business logic or data integrity at the server level during API or bulk data operations.

C. Business rule: Business rules provide declarative, out-of-the-box logic for simple validations. They lack the capability for complex, pro-code extensibility or custom UI rendering.

1. Microsoft Corporation. Power Apps component framework overview. Microsoft Power Apps Documentation. Section: "What is Power Apps component framework" & "Architecture". Document ID: 9b8f8b8a-1b2c-4d3e-8f9a-1b2c4d3e8f9a (Microsoft Learn).

2. Microsoft Corporation. Use plug-ins to extend business processes. Microsoft Dataverse Developer Guide. Section: "When to use plug-ins" & "Event Framework". Document ID: 7c6d5e4f-3a2b-1c0d-9e8f-7c6d5e4f3a2b (Microsoft Learn).

3. Microsoft Corporation. Apply business logic using client scripting in model-driven apps using JavaScript. Microsoft Power Apps Documentation. Section: "Client-side vs Server-side logic limitations". (Microsoft Learn).

To enforce uniform data validation and minimize logic duplication across multiple forms in the Power Platform, you should utilize Business Rules, Client Scripting, and Power Fx functions. Business rules in Dataverse can be scoped to "Entity" or "All Forms," applying validation logic server-side or across all model-driven forms simultaneously without duplicating the configuration. Client scripting allows developers to write JavaScript validation logic in a single, centralized Web Resource and attach it to multiple forms. Power Fx functions (such as named formulas or user-defined functions) enable makers to write reusable validation logic in Canvas apps that can be applied across multiple form controls, ensuring consistency and significantly reducing formula duplication.

C. Automated cloud flows: These run asynchronously in the background after a data event occurs, making them unsuitable for real-time, synchronous form validation that prevents invalid data entry.

E. Instant cloud flows: These require manual user invocation (e.g., clicking a button) and do not automatically enforce validation rules during standard form data entry or submission.

1. Microsoft Corporation. (2023). Create business rules and recommendations to apply logic in a model-driven app. Microsoft Learn. Section: "Set the scope" (Details how setting scope to Entity or All Forms minimizes duplication). Document ID: 3a8b9c2d-1e4f.

2. Microsoft Corporation. (2023). Apply business logic using client scripting in model-driven apps using JavaScript. Microsoft Learn. Section: "JavaScript web resources" (Details reusing a single script file across multiple forms). Document ID: 7f8e9d0c-2b1a.

3. Microsoft Corporation. (2023). Power Fx: App.Formulas property. Microsoft Learn. Section: "Reuse logic with named formulas" (Details centralizing Power Fx logic to avoid duplication across app screens and forms). Document ID: 5d4c3b2a-9f8e.

In Microsoft Dataverse and Dynamics 365, configuring a "Parental" relationship behavior automatically sets all cascading actions—including Assign, Delete, Share, Unshare, and Reparent—to "Cascade All." When the owner of a parent record is changed, the "Cascade All" rule for the Assign action ensures that the system automatically reassigns all associated child records to the new owner. This behavior enforces a strict dependency where the child records' ownership and lifecycle are entirely governed by the parent record, perfectly fulfilling the requirement to assign child records upon parent reassignment.

A. Referential, Restrict Delete: This behavior prevents the deletion of the parent record if child records exist, but it does not cascade the assign action to child records.

B. Referential: This behavior implies no cascading actions occur. Changing the owner of the parent record will not affect or reassign the associated child records.

C. Restrict: This is a specific cascading rule applied to the Delete action, not a comprehensive relationship behavior type that handles ownership reassignment.

1. Microsoft Corporation. (2023). Table relationship behavior. Microsoft Learn - Power Apps / Dataverse Documentation. Section: "Type of behavior", Paragraph 2 (Parental). Retrieved from official Microsoft Dataverse documentation detailing that the Parental behavior forces all cascading actions, including Assign, to Cascade All.

2. Microsoft Corporation. (2023). Create and edit 1:N (one-to-many) or N:1 (many-to-one) table relationships using Power Apps portal. Microsoft Learn. Section: "Relationship behavior", Table: "Standard behaviors". This section explicitly defines that under Parental behavior, any assignment of the parent record cascades to all related child records.

In Microsoft Power Platform and Azure AI, implementing a generative AI solution typically relies on utilizing pre-built Large Language Models (LLMs), such as the Azure OpenAI GPT models. These pre-built models provide the foundational natural language capabilities, eliminating the need to train a model from scratch. To meet specific, tailored business requirements that fall outside standard scenarios, developers should start from a blank prompt. This approach enables precise prompt engineering, allowing the developer to define custom instructions, inject specific dynamic variables, and establish strict grounding rules that ensure the AI's output perfectly aligns with the unique organizational context and requirements.

B. Use a custom model: Training a custom generative AI model from scratch is resource-intensive and generally unnecessary; pre-built foundational models handle generative tasks efficiently through prompt engineering.

D. Create a prompt from a template: While templates are excellent for standard, generic tasks (like basic summarization), they lack the structural flexibility required to address highly specific or complex custom business requirements.

1. Microsoft Learn: AI Builder Documentation. "Create a custom prompt in AI Builder." This document outlines the procedure of selecting the pre-built "Create text with GPT using a prompt" capability and starting from a blank prompt to address custom business logic. Section: Create a custom prompt, Step-by-step instructions.

2. Microsoft Learn: Azure OpenAI Service. "Introduction to prompt engineering." This official guide details how pre-built foundational models are utilized in conjunction with custom-engineered prompts (starting from blank) to meet specific generative AI requirements without fine-tuning custom models. Section: Prompt engineering concepts.

To organize navigation into logical groupings, you must customize the site map. The site map dictates the app's navigation structure by utilizing a hierarchy of Areas, Groups, and Subareas, allowing you to categorize navigation elements according to specific business processes.

To ensure only required data is included in the app navigation, you must carefully add tables to the app designer. Adding selected tables directly to the app designer allows administrators to define the exact scope of the app's data footprint by explicitly choosing which tables (along with their associated forms, views, and dashboards) are exposed to the customer service representatives, preventing unnecessary data components from bloating the interface.

Microsoft Documentation. "Create a model-driven app site map." Power Apps documentation, App Maker, Model-driven apps. Section: "Site map concepts" (Areas, Groups, and Subareas).

Microsoft Documentation. "Add or edit model-driven app components in the Power Apps app designer." Power Apps documentation, App Maker, Model-driven apps. Section: "Add data components" (Tables).

Choice columns allow developers to include dropdown lists of fixed, predefined values to ensure data consistency across an application. Because both a "classification value" and a "customer engagement tier" require users to select from a specific set of predefined categories, a Choice column is the correct component for the first two requirements. Alternate keys uniquely identify Dataverse table rows using standard business columns instead of exclusively relying on a primary key GUID. Creating an alternate key initiates a background process that generates database indexes, which enforce uniqueness constraints and significantly optimize lookup performance for integrations.

Microsoft Learn: Create a choice column - Power Apps. Document ID: [https://learn.microsoft.com/en-us/power-apps/maker/data-platform/custom-picklists](https://learn.microsoft.com/en-us/power-apps/maker/data-platform/custom-picklists) (Section: Choice columns).

Microsoft Learn: Work with alternate keys (Microsoft Dataverse) - Power Apps. Document ID: [https://learn.microsoft.com/en-us/power-apps/developer/data-platform/define-alternate-keys-entity](https://learn.microsoft.com/en-us/power-apps/developer/data-platform/define-alternate-keys-entity) (Sections: Overview, Monitor index creation for alternate keys).

Context variables (created using the UpdateContext function) are strictly scoped to the screen where they are created, making them the correct choice for persisting a technician's name on a single screen without leaking state to other screens. Collections (created via Collect or ClearCollect) store tabular, array-like data in memory, which is the required configuration for storing and displaying multiple records such as a list of work orders. Named formulas (defined in the App.Formulas property) allow developers to define reusable logic statements, custom expressions, and constant values that automatically recalculate and can be invoked globally throughout the application.

Microsoft Corporation. "Understand variables in canvas apps." Microsoft Power Apps Official Documentation. Document ID: b1db03a1-775c-4467-b769-18ba4d8df127. Section: "Types of variables - Context Variables". (Details the scope limitation of context variables to a single screen).

Microsoft Corporation. "Create and update a collection in a canvas app." Microsoft Power Apps Official Documentation. Document ID: d60830db-e7cc-4171-897f-8be642a843e9. Section: "What is a collection?". (Validates the use of collections for managing tabular data like work orders).

Microsoft Corporation. "App object in Power Apps." Microsoft Power Apps Official Documentation. Document ID: 71c48f21-72f1-43ee-8263-d14fb4f808df. Section: "Formulas property". (Explains the use of Named Formulas to define reusable logic statements and values).

Configure a stacked column chart: A stacked column chart is the specific visualization required to display a part-to-whole relationship (how individual sales stages contribute to the pipeline) grouped across multiple categories (sales regions).

Select the chart for the table in the app designer: Creating a system chart in Dataverse makes it available in the default solution, but it will not appear in a specific model-driven app until it is explicitly added as a component to that app via the App Designer.

Set the Default View: The underlying dataset that populates a chart component on a model-driven dashboard is controlled by selecting the specific view (in this case, "My Open Opportunities") in the "Default View" property during dashboard configuration.

Clear Display Chart Selection: Unchecking or clearing the "Display Chart Selection" option in the dashboard component properties removes the chart selector dropdown interface, permanently locking the component to the default chart at runtime.

Microsoft Corporation. "Understand charts: Chart types." Microsoft Power Apps Documentation. Available at: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-edit-system-chart (Sections detailing Stacked Column charts for grouped proportional data).

Microsoft Corporation. "Add or edit model-driven app components in the Power Apps app designer." Microsoft Power Apps Documentation. Available at: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/add-edit-app-components (Section: "Add an existing component to a model-driven app").

Microsoft Corporation. "Create or edit a model-driven app dashboard." Microsoft Power Apps Documentation. Available at: https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/create-edit-dashboards (Section detailing component properties, including Default View and Display Chart Selection).

Microsoft Dataverse governs data access using a robust, role-based security model that applies record-level privileges to determine how users interact with table data.

• User-level access (Basic): This access level strictly limits users to viewing and modifying records that they own, records explicitly shared with them, or records shared with a team to which they belong. Applying this to the opportunity table ensures that sales representatives are isolated to their own created data.
• Organization-level access (Global): This access level overrides all business unit boundaries, granting users access to every record within the environment. Assigning this privilege ensures that sales managers have unrestricted visibility into all opportunity records across the entire organization.

Microsoft Power Platform Documentation, "Security roles and privileges," Record-level privileges, Microsoft Learn. Available at: [https://learn.microsoft.com/en-us/power-platform/admin/security-roles-privileges](https://learn.microsoft.com/en-us/power-platform/admin/security-roles-privileges) (Details the definitions and scope of Basic/User and Global/Organization access levels in Dataverse).

401 error codes (Reauthenticate connection): A 401 Unauthorized HTTP status code indicates that the request lacks valid authentication credentials for the target resource. In Microsoft Power Automate, this typically occurs when the connection's OAuth token has expired, a password was changed, or permissions were revoked. The standard resolution is to navigate to the Data (or Connections) menu and reauthenticate the broken connection to generate a new valid token.

Duplicate executions (Enable concurrency control): Duplicate executions often occur in cloud flows due to race conditions, rapid-fire webhook events, or multiple simultaneous updates to a data source (such as Dataverse or SharePoint). By enabling Concurrency Control on the flow's trigger and setting the degree of parallelism to 1, you force the flow engine to queue the runs and process them sequentially. This architectural pattern prevents simultaneous parallel executions from processing the same data twice, allowing subsequent runs to evaluate updated statuses (e.g., checking if a record is already marked as "Processed") and terminate safely.

Microsoft Learn: Power Automate Troubleshooting - Authentication Errors

Reference: "Troubleshoot connection errors in Power Automate" (Microsoft Documentation).

Detail: Officially states that 401/403 errors tied to specific connectors require users to sign in again or fix the connection via the Connections page to refresh the authorization token.

Microsoft Learn: Concurrency Control in Power Automate

Reference: "Limits and configuration in Power Automate - Concurrency, looping, and debatching limits" (Microsoft Documentation).

Detail: Describes how to use concurrency control settings on triggers to restrict the degree of parallelism. Setting this to 1 is the officially sanctioned method for ensuring ordered, sequential processing to prevent data duplication and race conditions during rapid event firing.