A.Use a Process API to orchestrate calls to multiple System APIs, but NOT to other Process APIs.

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

C.Handle customizations for the end-user application at the Process API level rather than the Experience API level.

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

A.An overall tower usage of resources because each fine-grained API consumes less resources

B.A higher number of discoverable API-related assets in the application network

C.A better response time for the end user as a result of the APIs being smaller in scope and complexity

D.A decrease in the number of connections within the application network supporting the business process

A.The API policy is defined in API Manager, and then applied to ALL API instances in the specified environment

B.The API policy Is defined In Runtime Manager as part of the API deployment to a Mule runtime, and then ONLY applied to the specific API Instance

C.The API policy Is defined in API Manager and then automatically applied to ALL API instances

D.The API policy Is defined In API Manager for a specific API Instance, and then ONLY applied to the specific API instance

A.GET, PUT, OPTIONS

B.GET, OPTIONS, HEAD

C.PUT, POST, DELETE

D.GET, HEAD, POST

A.Document the API using an easily consumable asset like a RAML definition

B.Model all API resources and methods to closely mimic the operations of the backend system

C.Build an Enterprise Data Model (Canonical Data Model) for each backend system and apply it to System APIs

D.Expose to API clients all technical details of the API implementation's interaction with the backend system