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…
Question
Options
- AYes
- BNo
How the community answered
(29 responses)- A72% (21)
- B28% (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.