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…
Question
Options
- AYes
- BNo
How the community answered
(33 responses)- A21% (7)
- B79% (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.