When designing an upstream API and its implementation, the development team has been advised to NOT set timeouts when invoking a downstream API, because that downstream API has no SLA that can be relied upon.
This is the only downstream API dependency of that upstream API.
Assume the downstream API runs uninterrupted without crashing. What is the impact of this advice?

• A.A toad-dependent timeout of less than 1000 ms will be applied by the Mule runtime in which the downstream API implementation executes
• B.A default timeout of 500 ms will automatically be applied by the Mule runtime in which the upstream API implementation executes
• C.An SLA for the upstream API CANNOT be provided
• D.The invocation of the downstream API will run to completion without timing out

Comment: *

Name: *

Email: *

Verification: *

What API policy would be LEAST LIKELY used when designing an Experience API that is intended to work with a consumer mobile phone or tablet application?

• A.IP whitelist
• B.OAuth 2.0 access token enforcement
• C.Client ID enforcement
• D.JSON threat protection

Comment: *

Name: *

Email: *

Verification: *

An organization has created an API-led architecture that uses various API layers to integrate mobile clients with a backend system. The backend system consists of a number of specialized components and can be accessed via a REST API. The process and experience APIs share the same bounded-context model that is different from the backend data model. What additional canonical models, bounded-context models, or anti-corruption layers are best added to this architecture to help process data consumed from the backend system?

• A.Create a bounded-context model for every layer and overlap them when the boundary contexts overlap, letting API developers know about the differences between upstream and downstream data models
• B.Create a canonical model that combines the backend and API-led models to simplify and unify data models, and minimize data transformations.
• C.Create a bounded-context model for the system layer to closely match the backend data model, and add an anti-corruption layer to let the different bounded contexts cooperate across the system and process layers
• D.Create an anti-corruption layer for every API to perform transformation for every data model to match each other, and let data simply travel between APIs to avoid the complexity and overhead of building canonical models

Comment: *

Name: *

Email: *

Verification: *

Refer to the exhibit.

An organization uses one specific CloudHub (AWS) region for all CloudHub deployments.
How are CloudHub workers assigned to availability zones (AZs) when the organization's Mule applications are deployed to CloudHub in that region?

• A.Workers are randomly distributed across available AZs within that region
• B.AZs are selected as part of the Mule application's deployment configuration
• C.An AZ is randomly selected for a Mule application, and all the Mule application's CloudHub workers are assigned to that one AZ
• D.Workers belonging to a given environment are assigned to the same AZ within that region

Comment: *

Name: *

Email: *

Verification: *

The implementation of a Process API must change.
What is a valid approach that minimizes the impact of this change on API clients?

• A.Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
• B.Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
• C.Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged
• D.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

Comment: *

Name: *

Email: *

Verification: *