nerdexam
Microsoft

PL-400 · Question #457

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might…

The correct answer is A. Yes. This variant DOES meet the requirement (answer is Yes). A server-side Dataverse plugin registered on the Create message of the Account table fires for every account creation event, regardless of whether the record was created through the model-driven app UI or programmatically…

Submitted by viktor_hu· Apr 18, 2026

Question

Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution. After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear on the review screen. You have two tables, account and contact, with a parent-child relationship. Records in the account table can be created in the UI or from an external system integrated with Dataverse by using an Azure Function. When a user creates a record in the account table, a default record in the contact table must be created automatically. You need to implement a process to create the contact records. Solution: Create a cloud flow that runs when the account record is created. Use the Dataverse connector to create the contact record. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(29 responses)
  • A
    72% (21)
  • B
    28% (8)

Explanation

This variant DOES meet the requirement (answer is Yes). A server-side Dataverse plugin registered on the Create message of the Account table fires for every account creation event, regardless of whether the record was created through the model-driven app UI or programmatically via an external Azure Function calling the Dataverse API. Because plugins execute in the Dataverse server pipeline, they intercept all creation paths. The plugin logic can then call IOrganizationService.Create (or use an OrganizationRequest) to create the associated default Contact record, fully satisfying the requirement.

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice