A company has started to create an application network and is now planning to implement a Center for Enablement (C4E) organizational model. What key factor would lead the company to decide upon a federated rather than a centralized C4E?

• A.When there are a large number of existing common assets shared by development teams
• B.When various teams responsible for creating APIs are new to integration and hence need extensive training
• C.When development is already organized into several independent initiatives or groups
• D.When the majority of the applications in the application network are cloud based

Comment: *

Name: *

Email: *

Verification: *

Which layer in the API-led connectivity focuses on unlocking key systems, legacy systems, data sources etc and exposes the functionality?

• A.Experience Layer
• B.Process Layer
• C.System Layer

Correct Answer: C

Correct answer: System Layer

The APIs used in an API-led approach to connectivity fall into three categories:
System APIs - these usually access the core systems of record and provide a means of insulating the user from the complexity or any changes to the underlying systems. Once built, many users, can access data without any need to learn the underlying systems and can reuse these APIs in multiple projects.
Process APIs - These APIs interact with and shape data within a single system or across systems (breaking down data silos) and are created here without a dependence on the source systems from which that data originates, as well as the target channels through which that data is delivered.
Experience APIs - Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source, rather than setting up separate point-to-point integrations for each channel. An Experience API is usually created with API-first design principles where the API is designed for the specific user experience in mind.

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

What is the best way to decompose one end-to-end business process into a collaboration of Experience, Process, and System APIs?
A) Handle customizations for the end-user application at the Process API level rather than the Experience API level

B) Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs

C) Always use a tiered approach by creating exactly one API for each of the 3 layers (Experience, Process and System APIs)

D) Use a Process API to orchestrate calls to multiple System APIs, but NOT to other Process APIs

• A.Option A
• B.Option B
• C.Option C
• D.Option D

Correct Answer: B

Correct answer: Allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs.
*****************************************
>> All customizations for the end-user application should be handled in "Experience API" only. Not in Process API
>> We should use tiered approach but NOT always by creating exactly one API for each of the 3 layers. Experience APIs might be one but Process APIs and System APIs are often more than one. System APIs for sure will be more than one all the time as they are the smallest modular APIs built in front of end systems.
>> Process APIs can call System APIs as well as other Process APIs. There is no such anti-design pattern in API-Led connectivity saying Process APIs should not call other Process APIs.
So, the right answer in the given set of options that makes sense as per API-Led connectivity principles is to allow System APIs to return data that is NOT currently required by the identified Process or Experience APIs. This way, some future Process APIs can make use of that data from System APIs and we need NOT touch the System layer APIs again and again.

Comment: *

Name: *

Email: *

Verification: *

The responses to some HTTP requests can be cached depending on the HTTP verb used in the request.
According to the HTTP specification, for what HTTP verbs is this safe to do?

• A.PUT, POST, DELETE
• B.GET, HEAD, POST
• C.GET, PUT, OPTIONS
• D.GET, OPTIONS, HEAD

Comment: *

Name: *

Email: *

Verification: *

What Anypoint Connectors support transactions?

• A.Database, VM, File
• B.Database, JMS, VM, SFTP
• C.Database, 3MS, HTTP
• D.Database, JMS, VM

Comment: *

Name: *

Email: *

Verification: *