Free PL-400 Exam Flashcards

Confirm whether supported out-of-the-box features already meet the requirement. Custom code adds lifecycle, security, testing, and support obligations.

Use server-side Dataverse logic, such as a plug-in, so the rule also applies to API calls and other clients that bypass a specific app form.

Choose it when external data must appear as Dataverse rows without copying that data into Dataverse. Validate feature limitations before selecting it.

Very large or rapidly growing data with high read/write throughput and low-latency needs. Elastic tables scale horizontally, and performance depends on a consistent partitioning strategy.

It controls which connectors can be used together and which are blocked, reducing unintended movement of organizational data between services.

Authorization determines what an authenticated identity may access or do. In Dataverse, roles, teams, business units, and row sharing contribute to that decision.

Grant only the table privileges, access depths, and other permissions the component or user actually needs. Avoid broad roles as a shortcut.

They let the same solution use different configuration values after deployment without editing the solution's logic for each environment.

It lets solution components refer to a connection indirectly, so a suitable connection can be supplied when the solution moves to another environment.

It shows that one solution component requires another component. Resolve required dependencies before deleting components or deploying the solution.

The active top layer normally controls it. Forms, model-driven apps, and site maps can use merge behavior instead of simple top-wins behavior.

They provide a governed, in-product process for deploying solutions through configured environments with validation and deployment controls.

They add Power Platform-specific tasks for source synchronization, solution artifacts, checks, environment operations, and downstream deployment automation.

It provides centrally managed reusable components across apps and notifies app makers when published component updates are available.

It sends supported filtering or sorting work to the data source, allowing the query to evaluate the full data set instead of a limited local subset.

A nondelegable query is evaluated locally against only the configured row limit—500 by default and at most 2,000—so matching rows beyond that subset can be missed.

It records app events and data operations, including requests, responses, timing, and errors, so a maker can trace observed behavior to its source.

It detects an error and evaluates a corresponding replacement or recovery formula, allowing the app to handle failure deliberately.

Add a Power Automate cloud flow to the app and invoke it from Power Fx, passing only the inputs the flow requires.

Call executionContext.getFormContext(). The global Xrm.Page form context is deprecated for new client scripting.

It identifies the event and supplies the relevant form or grid context, so the handler does not depend on a global form reference.

It provides supported client methods for Dataverse data operations, including creating, retrieving, updating, and deleting rows.

Modern command buttons can use Power Fx, while JavaScript remains available when the command requires supported client-side code.

Use Xrm.Navigation.navigateTo with a page input that identifies the custom page and navigation options for the target presentation.

The framework calls it when values in the control's property bag or relevant context change, so the control can render the current state.

Call the notifyOutputChanged callback received during init. The framework can then call getOutputs to collect the new bound value.

For the initial operation, it can reject an invalid request before the main operation and before the database transaction begins.

PreOperation runs inside the transaction before the main write, so changing Target values there can affect the row being saved without issuing another update.

It runs after the originating transaction and avoids delaying the save, but it cannot roll back that completed transaction.

A pre-image captures selected row values before the operation; a post-image captures selected values after the operation where that image is supported.

They make the step run only when one of those columns is included in the update payload. Inclusion triggers the step even if the supplied value is unchanged.

It describes the current Dataverse event, including message, stage, depth, caller, parameters, and other execution data available to the plug-in.

It records diagnostic trace messages that help reconstruct plug-in execution and troubleshoot failures without relying on interactive debugging.

It provides supported Dataverse operations for working with rows and executing organization requests under an appropriate service context.

It defines a solution-aware Dataverse message with typed request and response values that callers can invoke through supported Dataverse APIs.

A bound API is associated with a table row or table collection. An unbound API is a global operation with no table binding.

It describes the REST API's operations, parameters, and schemas so Power Apps and Power Automate can expose those operations as connector actions or triggers.

It must define how the connector obtains and sends credentials accepted by the target API, such as OAuth 2.0 or an API key.

They alter connector behavior at runtime, such as routing a request or setting values, without changing the underlying API implementation.

Pause for the duration in the Retry-After response header, then retry according to a bounded retry strategy instead of immediately resending the request.

It avoids storing an application secret in code or configuration. The identity still needs an authorized Dataverse application user and appropriate privileges.

They prevent selected trigger or action data from being displayed in run history, reducing exposure of secrets and other sensitive values.

Use it to centralize a reusable sequence called by parent flows. Create the parent and child directly in the same solution for supported linking and deployment.

It defines the Azure messaging destination that a registered Dataverse event step can notify with execution context data.

An Azure-aware plug-in uses it to request that Dataverse post the current event execution context to a configured Azure service endpoint.

Use it when Dataverse should send event context to an HTTPS endpoint that can authenticate the request and respond within the configured execution model.

Choose Event Hubs when Dataverse events feed a high-throughput stream that multiple consumers can process for telemetry or event analytics.

Request tracked changes, store the opaque delta link returned by Dataverse, and use that link later to retrieve changes since the previous completed synchronization round.

It lets integration code address a Dataverse row by a unique external value when the external system does not store the Dataverse GUID.

It updates a matching row or creates one when no match exists. Integrations commonly pair it with an alternate key when the Dataverse GUID is unknown.