nerdexam
Microsoft

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…

Submitted by stefanr· 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 plug-in that runs when the account record is created. Use the Organization service to create the contact record. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(44 responses)
  • A
    20% (9)
  • B
    80% (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.

Full PL-400 Practice