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

• A.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
• 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.Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition

Comment: *

Name: *

Email: *

Verification: *

An organization makes a strategic decision to move towards an IT operating model that emphasizes consumption of reusable IT assets using modern APIs (as defined by MuleSoft).
What best describes each modern API in relation to this new IT operating model?

• A.Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)
• B.Each modern API has its own software development lifecycle, which reduces the need for documentation and automation
• C.Each modern API must be easy to consume, so should avoid complex authentication mechanisms such as SAML or JWT D
• D.Each modern API must be REST and HTTP based

Comment: *

Name: *

Email: *

Verification: *

True or False. We should always make sure that the APIs being designed and developed are self-servable even if it needs more man-day effort and resources.

• A.FALSE
• B.TRUE

Comment: *

Name: *

Email: *

Verification: *

In which layer of API-led connectivity, does the business logic orchestration reside?

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

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