nerdexam
Microsoft

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…

Submitted by carter_n· 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 JavaScript function that runs when the account record form is saved. Use the Web API in the JavaScript function to create the contact record. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(49 responses)
  • A
    22% (11)
  • B
    78% (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.

Full PL-400 Practice