What is a typical result of using a fine-grained rather than a coarse-grained API deployment model to implement a given business process?

• A.A decrease in the number of connections within the application network supporting the business process
• 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.An overall tower usage of resources because each fine-grained API consumes less resources

Comment: *

Name: *

Email: *

Verification: *

An API implementation is updated. When must the RAML definition of the API also be updated?

• A.When the API implementation changes from interacting with a legacy backend system deployed on-premises to a modern, cloud-based (SaaS) system
• B.When the API implementation changes the structure of the request or response messages
• C.When the API implementation is migrated from an older to a newer version of the Mule runtime
• D.When the API implementation is optimized to improve its average response time

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

Three business processes need to be implemented, and the implementations need to communicate with several different SaaS applications.
These processes are owned by separate (siloed) LOBs and are mainly independent of each other, but do share a few business entities. Each LOB has one development team and their own budget In this organizational context, what is the most effective approach to choose the API data models for the APIs that will implement these business processes with minimal redundancy of the data models?
A) Build several Bounded Context Data Models that align with coherent parts of the business processes and the definitions of associated business entities

B) Build distinct data models for each API to follow established micro-services and Agile API-centric practices

C) Build all API data models using XML schema to drive consistency and reuse across the organization

D) Build one centralized Canonical Data Model (Enterprise Data Model) that unifies all the data types from all three business processes, ensuring the data model is consistent and non-redundant

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

Comment: *

Name: *

Email: *

Verification: *

When using CloudHub with the Shared Load Balancer, what is managed EXCLUSIVELY by the API implementation (the Mule application) and NOT by Anypoint Platform?

• A.The number of DNS entries allocated to the API implementation
• B.The assignment of each HTTP request to a particular CloudHub worker
• C.The SSL certificates used by the API implementation to expose HTTPS endpoints
• D.The logging configuration that enables log entries to be visible in Runtime Manager

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

Comment: *

Name: *

Email: *

Verification: *