PL-400 Sample Questions & Answers

The API Key authentication type is specifically designed for this scenario. Configuring it with the correct parameter name (x-api-key) and location (Header) will automatically create a field on the connection creation screen, securely store the user's input, and add it as the specified header to every outbound request from the connector. This is the simplest and most secure method for handling API keys.

Azure Durable Functions are designed for stateful, long-running orchestrations. They can maintain their state across system restarts and handle complex, multi-day processes reliably.

To call the Azure Durable Function from a canvas app or Power Automate, a custom connector is the standard mechanism. It provides the bridge between the Power Platform and the custom Azure-hosted logic.

The OnSave event is the correct place to perform final validation before a record is committed to the database. The executionContext.getEventArgs().preventDefault() method is used specifically within the OnSave event to cancel the save operation. After preventing the save, formContext.ui.setFormNotification should be used to display a clear error message to the user, explaining why the save was blocked. Placing this logic in OnLoad or OnChange would be either too early or would not prevent saving if the invalid date was already present when the form loaded.

This statement is true. The 'Pre-validation' stage is the first stage in the pipeline and occurs before the main database transaction begins. It is intended for initial validation logic. If the plug-in throws an exception here, the entire operation is aborted without initiating a transaction that would need to be rolled back. The 'Pre-operation' and 'Post-operation' stages execute within the database transaction.

Elastic tables are specifically designed for high-volume, append-heavy workloads like IoT data, logs, and telemetry. They are built on Azure Cosmos DB and offer horizontal scaling and performance benefits for handling massive datasets that standard Dataverse tables (built on Azure SQL) are not optimized for. Virtual tables are for data that resides in external systems, and standard tables are for typical business application data.

ExecuteMultipleRequest is specifically designed for bulk data operations. It allows you to package multiple message requests (like UpdateRequest, CreateRequest, etc.) into a single call to the server. This significantly reduces the number of network round trips and is the most performant way to handle bulk operations. The server processes the requests in a more optimized fashion, often in parallel. ExecuteTransactionRequest groups operations into a single transaction but is not optimized for high throughput like ExecuteMultipleRequest. A simple parallel loop of UpdateRequest would quickly hit API throttling limits.

Using a Trigger Condition is the most efficient method. It filters events on the server side before the flow is initiated, which prevents unnecessary flow runs and saves API calls. Adding a Condition control as the first action means the flow still runs for every file, consumes a run, and then terminates, which is inefficient. A Filter Query is not available on this specific SharePoint trigger for file content properties. A Switch control would also require the flow to run first.

With modern Dataverse relationships in canvas apps, you can directly access related record data using dot notation. By setting the Items property simply to Accounts, you can then set the Text property of labels inside the gallery to ThisItem.Name for the account name, ThisItem.'Primary Contact'.'Full Name' for the contact's name, and ThisItem.'Primary Contact'.Email for the email. Power Apps automatically handles the join in the background, which is highly efficient. Using AddColumns with LookUp would result in the N+1 query problem, making a separate API call for every account in the gallery, which is extremely inefficient.

Managed Identity is the most secure method for Azure resources to authenticate to services that support Microsoft Entra ID (formerly Azure AD) authentication, like Dataverse. By enabling a Managed Identity for the Azure Function, Azure manages the credential lifecycle automatically. You create an Application User in Dataverse that represents this identity and assign it a security role. The function can then acquire an access token without any secrets stored in its configuration, fulfilling the primary requirement.

The on-premises data gateway application itself provides the most direct and detailed troubleshooting tools. It allows you to enable additional logging, view performance counters (CPU, memory), test network ports, and view logs that capture detailed information about requests, responses, and errors that occur at the gateway level. This is essential for diagnosing issues related to network connectivity, server performance, or gateway service problems that would not be visible in the Power Automate run history.