MB-500 · Question #254
Drag and Drop Question You need to integrate Dynamics 365 Finance with the following applications. Which integration patterns should you use? To answer, drag the appropriate patterns to the correct…
The correct answer is dual-write; custom service; batch data integration. Dynamics 365 Finance Integration Patterns > Note: The question appears to be missing the application names for positions 1–3. The explanation below covers the technical reasoning for each pattern, which maps to the most common exam version of this question (typically…
Question
Exhibit
Answer Area
Drag items
Correct arrangement
- dual-write
- custom service
- batch data integration
Explanation
Dynamics 365 Finance Integration Patterns
Note: The question appears to be missing the application names for positions 1–3. The explanation below covers the technical reasoning for each pattern, which maps to the most common exam version of this question (typically: Dataverse/CE apps, third-party/external apps, legacy/large-volume systems).
Integration Pattern Overview
| Position | Pattern | Typical Application Type |
|---|---|---|
| 1 | dual-write | Dataverse-based apps (e.g., D365 Sales, Customer Service) |
| 2 | custom service | External/third-party systems needing real-time sync |
| 3 | batch data integration | Legacy systems or high-volume periodic data transfers |
Position 1 - dual-write
Technical reason: Dual-write is a Microsoft-native, out-of-the-box framework that creates bidirectional, near-real-time synchronization between Dynamics 365 Finance & Operations apps and Dataverse-based apps (D365 Sales, Customer Service, Marketing, etc.). It uses pre-built entity maps and runs synchronously on data changes.
- Works only between F&O and Dataverse - not for arbitrary third-party systems
- Requires no custom code for standard entities
- Maintains referential integrity across both platforms
Common mistake: Thinking dual-write works with any external app. It is exclusively for Microsoft Dataverse ecosystems.
Position 2 - custom service
Technical reason: Custom services expose D365 Finance functionality via OData endpoints or custom X++ service classes, enabling synchronous, real-time request/response integration with third-party or external applications that need immediate feedback (e.g., trigger a business process and get a result back).
- Used when dual-write is unavailable (non-Dataverse target)
- Suitable for transactional operations: create a sales order, validate a record, query data
- Requires API development effort on both sides
Common mistake: Using batch integration when the third-party system requires a real-time response. Custom service is the right choice when latency matters.
Position 3 - batch data integration
Technical reason: The Data Management Framework (DIXF) handles large-volume, scheduled, or one-time data imports/exports using flat files (CSV, XML, Excel) or packages. It is designed for scenarios where real-time sync is not required - migrations, nightly feeds, bulk record creation.
- Asynchronous by nature - no immediate feedback
- Best for: legacy system migration, HR feeds, external reporting extracts
- Lowest implementation complexity for bulk data
Common mistake: Applying batch integration to systems that need real-time responses. Batch jobs introduce inherent delay and are inappropriate for time-sensitive transactions.
Key Differentiator Summary
- Dataverse app? → dual-write (built-in, real-time, bidirectional)
- Third-party needing real-time? → custom service (synchronous API)
- High volume or scheduled? → batch data integration (async, file-based)
Topics
Community Discussion
No community discussion yet for this question.