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: Register a service endpoint in the Common Data Service 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 port-operation stage.
Configure the Azure Function to process records as they are added to the queue.
Does the solution meet the goal?
A . Yes
B . No
Answer: A
Explanation:
Microsoft Dataverse supports integration with Azure.
For the Dataverse and Azure connection to work, there must be at least one solution in an Azure Service Bus solution account, where the solution contains one or more service endpoints. For a queue endpoint contract, a listener doesn’t have to be actively listening.
Reference: https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/azure-integration