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.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
• C.Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
• D.Implement required changes to the Process API implementation so that whenever possible, the Process API's RAML definition remains unchanged

Comment: *

Name: *

Email: *

Verification: *

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

Comment: *

Name: *

Email: *

Verification: *

What is a typical result of using a fine-grained rather than a coarse-grained API deployment model to implement a given business process?

• A.A decrease in the number of connections within the application network supporting the business process
• B.An overall tower usage of resources because each fine-grained API consumes less resources
• C.A better response time for the end user as a result of the APIs being smaller in scope and complexity
• D.A higher number of discoverable API-related assets in the application network

Comment: *

Name: *

Email: *

Verification: *

Which layer in the API-led connectivity focuses on unlocking key systems, legacy systems, data sources etc and exposes the functionality?

• A.Experience Layer
• B.Process Layer
• C.System Layer

Correct Answer: C

System Layer

The APIs used in an API-led approach to connectivity fall into three categories:
System APIs - these usually access the core systems of record and provide a means of insulating the user from the complexity or any changes to the underlying systems. Once built, many users, can access data without any need to learn the underlying systems and can reuse these APIs in multiple projects.
Process APIs - These APIs interact with and shape data within a single system or across systems (breaking down data silos) and are created here without a dependence on the source systems from which that data originates, as well as the target channels through which that data is delivered.
Experience APIs - Experience APIs are the means by which data can be reconfigured so that it is most easily consumed by its intended audience, all from a common data source, rather than setting up separate point-to- point integrations for each channel. An Experience API is usually created with API-first design principles where the API is designed for the specific user experience in mind.

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: *