Module Assessment

1.

A plug-in registered synchronously on the creation of a request table record consistently takes close to two seconds to run, and no other logic in the pipeline needs its result before the transaction completes. Which change most directly improves the caller's perceived responsiveness without introducing new risk to the pipeline?

Wrap the plug-in's data operations in an ExecuteMultipleRequest to reduce round trips.

Register the plug-in step for asynchronous execution instead of synchronous.

Register the same validation logic on the Retrieve message so it runs before the record is returned.

2.

A developer is designing a new custom API that reserves a device against a single, already-existing request record, and wants Dataverse to automatically pass that record to the plug-in without defining a custom parameter for it. Which binding type configuration achieves this?

EntityCollection binding, bound to the request table.

Global binding with a custom EntityReference request parameter.

Entity binding, bound to the request table.

3.

A developer writes the plug-in that implements the main operation of a custom API and wants to pass a secure string to it at run time, the same way they would pass secure configuration data to a conventional registered plug-in step. What should the developer expect?

They set the secure value as a response property so the plug-in reads it from OutputParameters.

The plug-in registration tool doesn't let them register a step for a custom API's main-operation plug-in, so there's no secure configuration data to set.

They add the value as a required request parameter so every caller must supply it.

4.

A procurement system outside Dataverse confirms a purchase order, and that confirmation needs to reach Dataverse as an event that other flows can react to, with no possibility that a Dataverse-side plug-in could block or alter the already-completed confirmation. How should this custom API be configured?

Set Allowed Custom Processing Step Type to Async Only, specify no plug-in for the main operation, and include only request parameters.

Set Allowed Custom Processing Step Type to Sync and Async so subscribers can validate the confirmation before it's accepted.

Set Allowed Custom Processing Step Type to None and rely on a main-operation plug-in to validate the confirmation before accepting it.

5.

A plug-in configured with Power Platform managed identity successfully acquires a token at run time, but its call to Azure Key Vault still fails with an access-denied error. What's the most likely cause, given that authentication already succeeded?

The federated identity credential's subject identifier doesn't match the plug-in's signing certificate.

The plug-in assembly was signed with a self-signed certificate instead of one from a trusted issuer.

The identity hasn't been granted a role assignment or access policy on the Key Vault.

Check your knowledge

Feedback