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…
Question
Options
- AYes
- BNo
How the community answered
(29 responses)- A14% (4)
- B86% (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.