PL-400 practice question 4 of 35

You are designing a one-way integration from Microsoft Dataverse to another system. You must use an Azure Function to update the other system. The…

Choose your answer, then check it against the explanation.

Domain Extend the platform

You are designing a one-way integration from Microsoft Dataverse 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 service endpoint in the Dataverse instance that connects to an Azure Service Bus queue. Register a step at the endpoint which runs asynchronously on the record's Create message and in the post-operation stage. Configure the Azure Function to process records as they are added to the queue. Does the solution meet the goal?

Answer options

Correct Answer:

Explanation

The proposed solution correctly implements a durable and reliable integration pattern. Registering an asynchronous step on a service endpoint connected to an Azure Service Bus queue effectively decouples Dataverse from the target system. If the Azure Function or the target system is unavailable, messages are safely stored in the queue until they can be processed, thus preventing data loss. The asynchronous post-operation execution ensures that the main Dataverse transaction is not blocked and that only successfully created records are sent, fulfilling all the stated requirements for a resilient integration.

Why Incorrect

B. No: This option is incorrect. The solution uses a standard, recommended architecture for one-way, asynchronous integration from Dataverse. The use of an Azure Service Bus queue is specifically designed to handle temporary unavailability of downstream components, which directly addresses the core requirement of the scenario.

References

1. Microsoft Dataverse Developer Guide, "Azure integration with Microsoft Dataverse": This document outlines the use of Azure Service Bus for creating a secure and reliable communication channel between Dataverse and external applications. It states, "This capability is especially useful in keeping disparate Dataverse systems or other Dataverse servers synchronized with business data changes."

Source: Microsoft. (n.d.). Azure integration with Microsoft Dataverse. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/power-apps/developer/data-platform/azure-integration

2. Microsoft Dataverse Developer Guide, "Event Framework": The documentation on the asynchronous service explains its resilience. It states, "Asynchronous plug-ins are queued... If an asynchronous plug-in fails, the platform will try to run it again." This built-in retry mechanism in Dataverse handles transient connectivity issues to the Service Bus.

Source: Microsoft. (n.d.). Event Framework. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/power-apps/developer/data-platform/event-framework#asynchronous-service

3. Azure Service Bus Documentation, "Service Bus queues, topics, and subscriptions": This documentation describes queues as a durable messaging solution. Messages sent to a queue are held until a consuming application is ready to receive and process them, which is the fundamental principle that prevents data loss when a component is unavailable.

Source: Microsoft. (n.d.). What are Service Bus queues, topics, and subscriptions?. Microsoft Learn. Retrieved from https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#queues

Question 4 of 35

Keep practicing

Take the free PL-400 practice test

Ten exam-style questions with answers and explanations, plus the exam facts and study guides.

Start the free practice test