PL-400 · Question #455
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 B. No. Like Question 7, the proposed solution in this variant does NOT meet the requirement (answer is No). The scenario explicitly states that accounts can be created from both the UI and an external Azure Function. A solution that relies on a UI-triggered mechanism-such as a…
Question
Options
- AYes
- BNo
How the community answered
(44 responses)- A20% (9)
- B80% (35)
Explanation
Like Question 7, the proposed solution in this variant does NOT meet the requirement (answer is No). The scenario explicitly states that accounts can be created from both the UI and an external Azure Function. A solution that relies on a UI-triggered mechanism-such as a business rule, form script, or a flow triggered only by manual user action-will not fire when the Azure Function creates the account via the Dataverse API. Only a server-side mechanism that intercepts all Account Create events regardless of origin (such as a registered Dataverse plugin on the Create message) guarantees the contact is always created.
Community Discussion
No community discussion yet for this question.