Q:
You are training a new Dynamics 365 Finance developer.
You need to recommend where asynchronous integrations should be used instead of synchronous integrations.
For which scenario should you recommend asynchronous integration?

A A retailer requires all new customer data captured at point of sale (POS) terminals through the day sent back to the system.
B A retailer wants to ensure gift card balances are communicated back to the system from point of sale (POS) terminals in near real-time.
C A manufacturer wants to move production data from an on-premises deployment Dynamics 365 Finance in near real-time.
D A warehouse wants to track movement of all inventory from scanners to the system.

Share this MCQ

Answer: A

Explanation:

An asynchronous pattern is a non-blocking pattern, where the caller submits the request and then continues without waiting for a response.
Typical scenarios and patterns that use batch data integrations (asynchronous pattern)
Here is a typical scenario that uses batch data APIs.
Import large volumes of sales orders
A company receives a large volume of sales orders from a front-end system that runs on-premises. These orders must periodically be sent to the application for processing and management.
Incorrect:
Not B, Not C, Not D: A synchronous pattern is a blocking request and response pattern, where the caller is blocked until the callee has finished running and gives a response.

Reference:
https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/data-entities/integration-overview

Q: You are training a new Dynamics 365 Finance developer.You need to recommend where asynchronous integrations should be used instead of synchronous integrations.For which scenario should you recommend asynchronous integration?

Report Question

Q:
You are training a new Dynamics 365 Finance developer.
You need to recommend where asynchronous integrations should be used instead of synchronous integrations.
For which scenario should you recommend asynchronous integration?