Drag and Drop Question A company uses Dynamics 365 Finance and Dynamics 365 Supply Chain Management. The company plans to integrate Dynamics 365 Sales customer data with Finance and Supply Chain…

The correct answer is Open Data Protocol (OData); Dual-write; Custom service. Dynamics 365 Data Integration - Exam Explanation Context: The question presents 3 scenarios for integrating Dynamics 365 Sales data with Finance & SCM. Azure Data Lake is a distractor (not used). --- Placement 1: Open Data Protocol (OData) Typical scenario: Perform a one-time…

Implement data and application integration

Question

Drag and Drop Question A company uses Dynamics 365 Finance and Dynamics 365 Supply Chain Management. The company plans to integrate Dynamics 365 Sales customer data with Finance and Supply Chain Management. You need to integrate the data. Which data integration option should you select for each scenario? To answer, drag the appropriate data integration options to the correct scenarios. Each data integration option may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content. NOTE: Each correct selection is worth one point. Answer:

Exhibit

Answer Area

Drag items

Open Data Protocol (OData)Dual-writeCustom serviceAzure Data Lake integration

Correct arrangement

Open Data Protocol (OData)
Dual-write
Custom service

Explanation

Dynamics 365 Data Integration - Exam Explanation

Context: The question presents 3 scenarios for integrating Dynamics 365 Sales data with Finance & SCM. Azure Data Lake is a distractor (not used).

Placement 1: Open Data Protocol (OData)

Typical scenario: Perform a one-time or periodic/scheduled data migration/synchronization, or read/write individual records via REST.

Why OData: OData exposes Finance & SCM data entities as standard REST endpoints. It is ideal for ad-hoc, periodic, or one-directional data operations (e.g., importing a batch of customers on a schedule). It is not real-time and not bidirectional by design - it's a synchronous request/response model.

Placement 2: Dual-write

Typical scenario: Synchronize customer data in near-real time between Dynamics 365 Sales (Dataverse) and Finance & SCM, bidirectionally and automatically.

Why Dual-write: Dual-write is Microsoft's purpose-built framework for live, bidirectional sync between Dataverse apps (Sales, Customer Service) and Finance & SCM. A record updated in Sales instantly reflects in Finance, and vice versa. This is the primary answer for any scenario involving ongoing, real-time Sales ↔ Finance/SCM integration.

Placement 3: Custom service

Typical scenario: Expose or consume a custom business logic operation not covered by standard data entities, or integrate with a third-party system requiring specific processing.

Why Custom service: Custom services (X++ classes exposed as SOAP/REST services) are used when standard data entities don't meet the need - for example, triggering a workflow, applying business rules during import, or handling a non-standard integration shape.

Why Azure Data Lake is NOT used

Azure Data Lake integration is an analytics/reporting tool - it exports Finance & SCM data to a lake for BI consumption. It has no role in transactional synchronization with Sales and should not be selected for any of these scenarios. It is a classic distractor on this exam.

Common Mistakes

Mistake	Correction
Choosing Dual-write for one-time migrations	Dual-write is for continuous real-time sync, not one-off imports
Choosing OData for real-time Sales ↔ Finance sync	OData is pull-based; Dual-write handles live bidirectional sync
Choosing Azure Data Lake for any transactional scenario	It is analytics-only
Overlooking Custom service	It is the right answer when business logic or non-standard data shape is required

Topics

#OData#Dual-write#custom service#data integration patterns

Community Discussion

No community discussion yet for this question.

Full MB-500 Practice