PL-400 · Question #456
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 variant also does NOT meet the requirement (answer is No). A common incorrect approach is a Power Automate flow or solution that is not configured to trigger on all account creation paths. For example, a flow triggered on a model-driven app form save would miss external…
Question
Options
- AYes
- BNo
How the community answered
(49 responses)- A22% (11)
- B78% (38)
Explanation
This variant also does NOT meet the requirement (answer is No). A common incorrect approach is a Power Automate flow or solution that is not configured to trigger on all account creation paths. For example, a flow triggered on a model-driven app form save would miss external Azure Function calls. Similarly, a workflow or business rule that operates only within the Dataverse UI context fails the external-system creation scenario. The contact record must be created for every account creation event regardless of origin, which requires a server-side plugin registered on the Create step of the Account table.
Community Discussion
No community discussion yet for this question.