PL-400 Practice Questions

Custom pages are essentially canvas apps embedded within a model-driven app. To achieve a pixel-perfect, highly customized layout for displaying a list of records, the standard canvas app Gallery control is the appropriate choice. It provides complete control over the layout, controls, and data displayed for each item in the list, which aligns with the core strengths of canvas apps. Subgrids and PCF grids are used on standard model-driven forms and views, not typically within the custom page canvas designer.

Environment variables are the standard, recommended mechanism for managing configuration data that varies between environments. By creating an environment variable in the solution, the canvas app and flow can reference it. After the solution is deployed to a new environment (like Test or Prod), an administrator can provide the correct URL for that specific environment without modifying the app or flow, which is a core ALM principle.

The Assign message is the specific message that fires when a record's ownership is changed. This is the correct message to trigger the logic.

The requirement specifies the process must execute asynchronously after the transaction is committed. This improves system performance and user experience by not holding up the UI.

An asynchronous plug-in that integrates with an external system should not call the external system directly. The best practice is to post the execution context to a Service Endpoint, which decouples the systems and provides a more robust integration pattern.

The browser's developer tools (F12) are essential for debugging client-side code. The 'Network' tab specifically captures all HTTP requests made by the page, including the Web API calls from your script. It allows you to inspect the full request URL, headers, payload, and the server's response, which is exactly what is needed to debug API interactions. The Monitor tool is more focused on Power Fx and connector calls within canvas apps and custom pages, not traditional model-driven form scripting.

The Power Apps component framework (PCF) is the designated framework for creating code-based, reusable components that can be used across both canvas apps and model-driven apps. It allows developers to use standard web technologies like HTML, CSS, and TypeScript (and by extension, third-party JavaScript libraries) to create rich user experiences that are not possible with out-of-the-box controls. Canvas components are only usable within canvas apps.

The most efficient and correct method is to use a Pre Image. By registering a Pre Image with the required attribute (primarycontactid), the plug-in execution context will contain a snapshot of the record before the update. The Target entity in the InputParameters will contain the new value being set. This avoids an extra API call to the database, making it the most performant and standard approach. Retrieving the record again in a post-operation step or querying the database in a pre-operation step introduces unnecessary overhead and potential race conditions.

This pattern provides the required durability and guarantee. The asynchronous plug-in will execute after the Dataverse transaction is committed. It posts a message to Azure Service Bus, which provides guaranteed delivery. A separate Azure Function can then process messages from the queue, with its own retry logic, to call the external API. This decouples the systems and ensures the audit log is eventually created even if the external API is temporarily unavailable. A synchronous plug-in would lock the UI and fail the Dataverse transaction if the API call fails. A webhook is less durable as it lacks a built-in queue for guaranteed delivery.

The context.webAPI is the standard and supported method for performing data operations against Dataverse from within a PCF component. The retrieveMultipleRecords method, combined with a FetchXML or OData query, allows the component to securely and efficiently fetch related data without needing to manage authentication tokens manually. Using a direct fetch call is not recommended as it bypasses the component's context and security. Binding a subgrid is a configuration for forms, not a data fetching method within the component's code. Passing data via component properties is for static or parent-driven data, not for fetching related records independently.

While Filter and equality checks on option sets (Status = 'Active') are delegable to Dataverse, the StartsWith function on a text column is a common cause of delegation issues. Because StartsWith is not delegable, Power Apps first retrieves the initial 500 records (the non-delegable limit) from Dataverse that match Status = 'Active', and then applies the StartsWith filter locally on that small subset. This leads to incomplete search results. The && operator is delegable. To fix this, the developer should use a delegable search function like the Search function or filter on a different, delegable criterion.

This describes a source-control-first ALM strategy, which is the best practice for team development. Each developer works in isolation. Their unmanaged solutions are unpacked (or 'decomposed') into source files. Git is used to merge the changes from different developers. A CI/CD pipeline (like Azure DevOps with Power Platform Build Tools) then automates the process of packing the merged files back into a solution and deploying it. This approach provides version history, conflict resolution, and automation.