An API implementation is being designed that must invoke an Order API, which is known to repeatedly experience downtime.
For this reason, a fallback API is to be called when the Order API is unavailable.
What approach to designing the invocation of the fallback API provides the best resilience?

• A.Search Anypoint Exchange for a suitable existing fallback API, and then implement invocations to this fallback API in addition to the Order API
• B.Create a separate entry for the Order API in API Manager, and then invoke this API as a fallback API if the primary Order API is unavailable
• C.Redirect client requests through an HTTP 307 Temporary Redirect status code to the fallback API whenever the Order API is unavailable
• D.Set an option in the HTTP Requester component that invokes the Order API to instead invoke a fallback API whenever an HTTP 4xx or 5xx response status code is returned from the Order API

Comment: *

Name: *

Email: *

Verification: *

What condition requires using a CloudHub Dedicated Load Balancer?

• A.When cross-region load balancing is required between separate deployments of the same Mule application
• B.When custom DNS names are required for API implementations deployed to customer-hosted Mule runtimes
• C.When API invocations across multiple CloudHub workers must be load balanced
• D.When server-side load-balanced TLS mutual authentication is required between API implementations and API clients

Comment: *

Name: *

Email: *

Verification: *

An enterprise is embarking on the API-led digital transformation journey, and the central IT team has started to define System APIs. Currently there is no Enterprise Data Model being defined within the enterprise, and the definition of a clean Bounded Context Data Model requires too much effort.
According to MuleSoft's recommended guidelines, how should the System API data model be defined?

• A.If there are misspellings of the data fields in the back-end system, Systerm APIs should not correct it, and expose it as-is to mirror the back-end systems
• B.The data model of the System APIs should make use of data types that approximately mirror those from the back-end systems
• C.The data model should define its own naming convention, and not follow the same naming as the back-end systems
• D.The System APIs should expose all back-end system fields

Comment: *

Name: *

Email: *

Verification: *

A company has created a successful enterprise data model (EDM). The company is committed to building an application network by adopting modern APIs as a core enabler of the company's IT operating model. At what API tiers (experience, process, system) should the company require reusing the EDM when designing modern API data models?

• A.At the experience and process tiers
• B.At the experience and system tiers
• C.At the process and system tiers
• D.At the experience, process, and system tiers

Comment: *

Name: *

Email: *

Verification: *

Which statement is true about Spike Control policy and Rate Limiting policy?

• A.All requests are rejected after the limit is reached in Rate Limiting policy, whereas the requests are queued in Spike Control policy after the limit is reached
• B.In a clustered environment, the Rate Limiting.and Spike Control policies are applied to each node in the cluster
• C.To protect Experience APIs by limiting resource consumption, Rate Limiting policy must be applied
• D.In order to apply Rate Limiting and Spike Control policies, a contract to bind client application and API is needed for both

Comment: *

Name: *

Email: *

Verification: *