Examice

Question 6 of 58

What is true about the technology architecture of Anypoint VPCs?

The private IP address range of an Anypoint VPC is automatically chosen by CloudHub.

Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can stay within a private network.

Each CloudHub environment requires a separate Anypoint VPC.

VPC peering can be used to link the underlying AWS VPC to an on-premises (non AWS) private network.

Correct Answer: B

Traffic between Mule applications deployed to an Anypoint VPC and on-premises systems can indeed stay within a private network. This is achieved through secure connectivity options such as IPsec tunnels or AWS Direct Connect. By using these methods, data can traverse privately and securely, ensuring that the traffic remains within a secured network without exposing it to the public internet.

Question 7 of 58

An API implementation is deployed on a single worker on CloudHub and invoked by external API clients (outside of CloudHub).

How can an alert be set up that is guaranteed to trigger AS SOON AS that API implementation stops responding to API invocations?

Implement a heartbeat/health check within the API and invoke it from outside the Anypoint Platform and alert when the heartbeat does not respond.

Configure a ג€worker not respondingג€ alert in Anypoint Runtime Manager.

Handle API invocation exceptions within the calling API client and raise an alert from that API client when the API is unavailable.

Create an alert for when the API receives no requests within a specified time period.

Correct Answer: B

To set up an alert that is guaranteed to trigger as soon as the API implementation stops responding to API invocations, the best option is to configure a 'worker not responding' alert in Anypoint Runtime Manager. This solution provides immediate monitoring and alerting of the worker's status, ensuring timely detection of any unresponsiveness. Other options either require additional implementation effort, like external health checks, or may not be as reliable or immediate in detecting the issue.

Question 8 of 58

The implementation of a Process API must change.

What is a valid approach that minimizes the impact of this change on API clients?

Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition.

Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version.

Implement required changes to the Process API implementation so that, whenever possible, the Process API's RAML definition remains unchanged.

Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 - Moved Permanently to inform API clients they should be calling the new API implementation.

Correct Answer: C

The best approach to minimize the impact of changes on API clients is to implement the required changes to the Process API implementation in such a way that the RAML definition remains unchanged whenever possible. This ensures that clients relying on the existing API definition do not experience disruptions or need to make modifications to their integrations.

Question 9 of 58

Refer to the exhibit.

An organization needs to enable access to their customer data from both a mobile app and a web application, which each need access to common fields as well as certain unique fields.

The data is available partially in a database and partially in a 3rd-party CRM system.

What APIs should be created to best fit these design requirements?

A Process API that contains the data required by both the web and mobile apps, allowing these applications to invoke it directly and access the data they need thereby providing the flexibility to add more fields in the future without needing API changes.

One set of APIs (Experience API, Process API, and System API) for the web app, and another set for the mobile app.

Separate Experience APIs for the mobile and web app, but a common Process API that invokes separate System APIs created for the database and CRM system

A common Experience API used by both the web and mobile apps, but separate Process APIs for the web and mobile apps that interact with the database and the CRM System.

Correct Answer: C

To meet the design requirements of enabling access to customer data from both a mobile app and a web application, it's essential to have separate Experience APIs for the mobile and web apps. This allows each app to have tailored experiences and access specific fields as needed. However, a common Process API is practical for handling the integration and business logic, ensuring consistency and reusability. This Process API can then invoke separate System APIs that interact with the database and the CRM system to retrieve the necessary data. This setup ensures modularity and flexibility, enabling future scalability without significant changes to the API structure.

Question 10 of 58

Refer to the exhibit.

A developer is building a client application to invoke an API deployed to the STAGING environment that is governed by a client ID enforcement policy.

What is required to successfully invoke the API?

The client ID and secret for the Anypoint Platform account owning the API in the STAGING environment

The client ID and secret for the Anypoint Platform account's STAGING environment

The client ID and secret obtained from Anypoint Exchange for the API instance in the STAGING environment

A valid OAuth token obtained from Anypoint Platform and its associated client ID and secret

Correct Answer: C

To successfully invoke an API governed by a client ID enforcement policy in the STAGING environment, the client application must provide the client ID and secret specific to the API instance in that environment. These credentials are typically obtained directly from Anypoint Exchange for the API instance in the STAGING environment. This is because client ID and secret are used to uniquely identify and authenticate the client application interacting with a specific API instance, ensuring proper access control.