A TemperatureSensors API instance is defined in API Manager in the PROD environment of the CAR_FACTORY business group. An AcmelemperatureSensors Mule application implements this API instance and is deployed from Runtime Manager to the PROD environment of the CAR_FACTORY business group. A policy that requires a valid client ID and client secret is applied in API Manager to the API instance.
Where can an API consumer obtain a valid client ID and client secret to call the AcmeTemperatureSensors Mule application?

• A. In secrets manager, request access to the Shared Secret static username/password
• B. In Anypoint Exchange, from an API client application that has been approved for the TemperatureSensors API instance
• C. In access management, from the PROD environment of the CAR_FACTORY business group
• D. In API Manager, from the PROD environment of the CAR_FACTORY business group

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

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. 3.1.0
• C. 4.0.0
• D. 3.0.1

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

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

An API implementation is deployed to CloudHub.
What conditions can be alerted on using the default Anypoint Platform functionality, where the alert conditions depend on the end-to-end request processing of the API implementation?

• A. When the API is invoked by an unrecognized API client
• B. When a particular API client invokes the API too often within a given time period
• C. When the response time of API invocations exceeds a threshold
• D. When the API receives a very high number of API invocations