PL-400 · Question #454
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. This is a Yes/No series question where the proposed solution does NOT meet the requirement (answer is No). The scenario requires automatic contact creation whenever an account is created, whether via the UI or via an external Azure Function. The solution presented in this…
Question
Options
- AYes
- BNo
How the community answered
(26 responses)- A19% (5)
- B81% (21)
Explanation
This is a Yes/No series question where the proposed solution does NOT meet the requirement (answer is No). The scenario requires automatic contact creation whenever an account is created, whether via the UI or via an external Azure Function. The solution presented in this variant (likely a client-side JavaScript or form event approach) only fires for UI-initiated record creation. Records created programmatically by the Azure Function bypass the browser and UI event pipeline entirely, so the contact would never be created for that path. A valid solution must be server-side (e.g., a Dataverse plugin on the Account Create message) to cover both creation sources.
Community Discussion
No community discussion yet for this question.