A system API has a guaranteed SLA of 100 ms per request. The system API is deployed to a primary environment as well as to a disaster recovery (DR) environment, with different DNS names in each environment. An upstream process API invokes the system API and the main goal of this process API is to respond to client requests in the least possible time. In what order should the system APIs be invoked, and what changes should be made in order to speed up the response time for requests from the process API?

• A.In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment, and ONLY use the first response
• B.In parallel, invoke the system API deployed to the primary environment and the system API deployed to the DR environment using a scatter-gather configured with a timeout, and then merge the responses
• C.Invoke the system API deployed to the primary environment, and if it fails, invoke the system API deployed to the DR environment
• D.Invoke ONLY the system API deployed to the primary environment, and add timeout and retry logic to avoid intermittent failures

Comment: *

Name: *

Email: *

Verification: *

Version 3.0.1 of a REST API implementation represents time values in PST time using ISO 8601 hh:mm:ss format. The API implementation needs to be changed to instead represent time values in CEST time using ISO 8601 hh:mm:ss format. When following the semver.org semantic versioning specification, what version should be assigned to the updated API implementation?

• A.3.0.2
• B.4.0.0
• C.3.1.0
• D.3.0.1

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.Duplicate the APIs as Mule applications, then deploy them to 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.Redeploy the API implementations to the same servers running the Mule runtimes
• D.Add an additional endpoint to each API for partner-enablement consumption

Comment: *

Name: *

Email: *

Verification: *

What is true about the technology architecture of Anypoint VPCs?

• A.The private IP address range of an Anypoint VPC is automatically chosen by CloudHub
• B.Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network
• C.Each CloudHub environment requires a separate Anypoint VPC
• D.VPC peering can be used to link the underlying AWS VPC to an on-premises (non AWS) private network

Comment: *

Name: *

Email: *

Verification: *

An Anypoint Platform organization has been configured with an external identity provider (IdP) for identity management and client management. What credentials or token must be provided to Anypoint CLI to execute commands against the Anypoint Platform APIs?

• A.The credentials provided by the IdP for identity management
• B.The credentials provided by the IdP for client management
• C.An OAuth 2.0 token generated using the credentials provided by the IdP for client management
• D.An OAuth 2.0 token generated using the credentials provided by the IdP for identity management

Comment: *

Name: *

Email: *

Verification: *