nerdexam
Microsoft

PL-400 · Question #32

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. The integration requirement specifies that the solution must support scenarios where a component is unavailable for more than a few seconds without data loss. This requires a durable, queue-based messaging architecture. The proposed solution in this variant (likely using a…

Submitted by kim_seoul· 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 once 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 in the review screen. You are designing a one-way integration from the Common Data Service to another system. You must use an Azure Function to update the other system. The integration must send only newly created records to the other system. The solution must support scenarios where a component of the integration is unavailable for more than a few seconds to avoid data loss. You need to design the integration solution. Solution: Register a webhook in the Common Data Service that connects to the Azure Function. Register a step on the webhook which runs synchronously on the record's Create message and in the post-operation stage. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(29 responses)
  • A
    14% (4)
  • B
    86% (25)

Explanation

The integration requirement specifies that the solution must support scenarios where a component is unavailable for more than a few seconds without data loss. This requires a durable, queue-based messaging architecture. The proposed solution in this variant (likely using a synchronous plugin or direct webhook to Azure Function) does not satisfy this requirement because if the Azure Function or any component is temporarily unavailable, records created during that window will be lost with no retry mechanism. The correct approach is to use Azure Service Bus: CDS sends messages to a Service Bus queue, and the Azure Function reads from the queue when it becomes available. Service Bus persists messages durably, ensuring no data loss during outages. Because this variant does not use a durable queue, the answer is No.

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice