M4 - Data Integration Concepts

Question 1

Mention Integration API choices

Answer 1

Open Data Protocol (OA)
Custom Services
External web services
Microsoft Office Integrations
Recurring integrations
Data Managment package API

Question 2

When are synchronous integrations ideal?

Answer 2

For scenarios requiring immediate feedback, such as validation or real-time updates

Question 3

When are asynchronous integrations ideal?

Answer 3

In exchanges of high-volume data, where performance and reliability are prioritized over immediacy.

Question 4

Mention some data integration scenarios

Answer 4

• Master data synchronization
• Transactional data exchange
• Real-time updates versus scheduled batch processes.

Question 5

Which APIs support file-based integration scenarios and data import and export?

Answer 5

• Recurring integrations API
• Data management framework API

Question 6

What is the Open Data Protocol?

Answer 6

Is a widely used protocol for building and consuming RESTFul APIs.

Question 7

What does the Open Data Protocol (OData) allow developers?

Answer 7

To query and manipulate data using HTTP methods like GET, POST, PUT and DELETE.

Question 8

Key features of Open Data Protocol (OData)

Answer 8

• Real-Time integration: Ideal when requiring real-time data interaction.
• Standard Protocol: Build on open standards, supports URIs.
• Flexible query options: Supports advance querying capabilities such as filtering, sorting, pagination and data projections.
• Built-in Security : Uses OAuth 2.0 for secure access.

Question 9

What does Recurring Integrations API support?

Answer 9

Data import and export

Question 10

Key capabilities of recurring integrations

Answer 10

• Job scheduling
• Multiple data formats: Files and data packages for import and export
• Transformation: If data is in XML formation, Extensible Style Sheet Language Transformation is supported to convert the data.
• Protocols: SOAP and REST
• Service type: Recurring integrations are part of data management APIIs and are available out of the box.
• Availability: Recurring integrations aren’t supported for on-premises implementations.

Question 11

What is the Data Management Framework?

Answer 11

Is a file-based integration scenario that is supported with finance and operations apps.

Question 12

Why would you choose to use the Data Management framework package?

Answer 12

• Scheduling: Is done outside of F&O apps.
• Formats : Data packages only.
• Transformation: Are external to the system.
• Protocols : REST
• Service type: OData is used for authorization and access to the application.
• Availability : Platform 5 and later. Only supported API for on-premises deployments.

Question 13

What are service protection limits for?

Answer 13

To increase system performance and reliability.
Are in place for OData and custom integrations, such that, if a request exceeds the imposed service protection limits, it is throttled. The request also receives a 429 response.

Question 14

Data integrations can be

Answer 14

Synchronous or asynchronous

Question 15

What do synchronous integration patterns use?

Answer 15

The Open Data Protocol (OData) with a continuous flow of data.

Question 16

What patterns do Asynchronous integration use?

Answer 16

Batch data APIs that run through a batch service.

Question 17

One advantage of using batch data APIs is…

Answer 17

Their ability to handler large volumes of data.

Question 18

Best practice when dealing with several hundred records

Answer 18

Use a batch data API integration