What is true about where an API policy is defined in Anypoint Platform and how it is then applied to API instances?

• A.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
• B.The API policy Is defined In API Manager for a specific API Instance, 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, and then applied to ALL API instances in the specified environment

Comment: *

Name: *

Email: *

Verification: *

Mule applications that implement a number of REST APIs are deployed to their own subnet that is inaccessible from outside the organization.
External business-partners need to access these APIs, which are only allowed to be invoked from a separate subnet dedicated to partners - called Partner-subnet. This subnet is accessible from the public internet, which allows these external partners to reach it.
Anypoint Platform and Mule runtimes are already deployed in Partner-subnet. These Mule runtimes can already access the APIs.
What is the most resource-efficient solution to comply with these requirements, while having the least impact on other applications that are currently using the APIs?

• A.Redeploy the API implementations to the same servers running the Mule runtimes
• B.Implement (or generate) an API proxy Mule application for each of the APIs, then deploy the API proxies to the Mule runtimes
• C.Add an additional endpoint to each API for partner-enablement consumption
• D.Duplicate the APIs as Mule applications, then deploy them to the Mule runtimes

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 B
• B.Option D
• C.Option A
• D.Option C

Comment: *

Name: *

Email: *

Verification: *

What is a best practice when building System APIs?

• 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

Comment: *

Name: *

Email: *

Verification: *

What Mule application deployment scenario requires using Anypoint Platform Private Cloud Edition or Anypoint Platform for Pivotal Cloud Foundry?

• A.When it Is required to make ALL applications highly available across multiple data centers
• B.When it is required that ALL APIs are private and NOT exposed to the public cloud
• C.When regulatory requirements mandate on-premises processing of EVERY data item, including meta-data
• D.When ALL backend systems in the application network are deployed in the organization's intranet

Comment: *

Name: *

Email: *

Verification: *