nerdexam
Microsoft

PL-400 · Question #34

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 another variant of the same integration scenario requiring durability against component unavailability. The proposed solution in this variant (likely using Azure Event Grid or a direct trigger without queuing) also does not meet the data-loss requirement. Event Grid has…

Submitted by ricky.ec· 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: Configure the Azure Function with a timer trigger that runs every five minutes. The function will query the Common Data Service and process records created in the last five minutes. Does the solution meet the goal?

Options

  • AYes
  • BNo

How the community answered

(33 responses)
  • A
    21% (7)
  • B
    79% (26)

Explanation

This is another variant of the same integration scenario requiring durability against component unavailability. The proposed solution in this variant (likely using Azure Event Grid or a direct trigger without queuing) also does not meet the data-loss requirement. Event Grid has a limited retry window and is not designed for guaranteed delivery over extended outages. Azure Service Bus is the correct solution because it provides persistent message storage, dead-letter queuing, and long-term retry capabilities - all necessary when a component can be unavailable for more than a few seconds. Since this proposed solution does not implement a durable queue mechanism, it fails the stated requirement and the answer is No.

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice