Microsoft
PL-400 · Question #446
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. Register a service endpoint for an Azure Service Bus queue. Use an Azure Function to process messages from the queue and forward them to the REST API. Redirect failed messages to the dead-letter queue. Azure Service Bus queues are well-suited for handling message-based…
Submitted by weili_xi· 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 an integration that sends created records from a custom Dataverse table to an exposed REST API. When the REST API is unavailable, you must be able to retry if the response status code is 500. You need to select a solution that meets the requirement. Solution: Register a webhook by using the REST API as the endpoint. Wait for the webhook to automatically retry when a failure occurs. Does the solution meet the goal?
Options
- AYes
- BNo
How the community answered
(59 responses)- A29% (17)
- B71% (42)
Explanation
- Register a service endpoint for an Azure Service Bus queue. Use an Azure Function to process messages from the queue and forward them to the REST API. Redirect failed messages to the dead-letter queue. Azure Service Bus queues are well-suited for handling message-based integrations, ensuring reliable delivery even when external systems (like a REST API) are unavailable. Using an Azure Function to process messages and forward them to the REST API adds flexibility and resilience, as it allows for retries and error handling, including the scenario where the API returns a 500 Redirecting failed messages to the dead-letter queue ensures that unprocessed messages are not lost, allowing further investigation or retries. This solution provides the necessary retry mechanism and error handling. * Register an asynchronous plug-in that makes an HTTP request to the REST API. Raise an InvalidPluginExecutionException that is configured to retry when the request fails. * Register a synchronous plug-in that makes an HTTP request to the REST API. Raise an InvalidPluginExecutionException when the request fails. The solution described does not meet the goal. Synchronous plug-ins execute immediately within the context of the transaction and are not ideal for making external HTTP requests, especially if retries are required. If the external REST API is unavailable and you raise an InvalidPluginExecutionException, the entire transaction will fail, and there won’t be any retry mechanism built into this approach. * Register a webhook by using the REST API as the endpoint. Wait for the webhook to automatically retry when a failure occurs. https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-
Community Discussion
No community discussion yet for this question.