For which scenario should you recommend asynchronous integration?

You are training a new Dynamics 365 Finance and Operations 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 service company needs workers to be able to access just-in-time inventory data from the field by using a third-party Software as a Service (SaaS) application to ensure they have parts to complete a service.
C . A retailer wants to ensure gift card balances are communicated back to the system from point of sale (POS) terminals in near real-time.
D . A company uses workflow for purchasing approvals, which then sends just-in-time approval information to a third-party application for approvers to review.

View Answer

Answer: A

Explanation:

Classic data integration: Asynchronous, Classic data integration provides asynchronous and uni-directional data synchronization experience between model-driven applications in Dynamics 365 and Dynamics 365 Finance and Operations applications. It’s an IT-administrator led experience and you must schedule the data sync jobs to run on a specific cadence. Classic data integration is suitable for business scenarios that involves bulk ingress/egress of data across Dynamics 365 applications.

Incorrect Answers:

B: Just-in-time inventory data required.

C: Real-time required.

Not D: Bi-directional.

Note: Dual-write: Synchronous, Bi-directional.

Dual-write provides synchronous, bi-directional, near-real time experience between model-driven applications in Dynamics 365 and Finance and Operations applications. Data synchronization happens with little or no intervention and is triggered by create, update and delete actions on an entity. Dual-write is suitable for interactive business scenarios that span across Dynamics 365 applications.