nerdexam
Microsoft

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…

Submitted by jian89· 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 custom API bound to the account table that uses a plug-in. Use the Organization service to create the contact record. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(26 responses)
  • A
    19% (5)
  • B
    81% (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.

Full PL-400 Practice