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

Comment: *

Name: *

Email: *

Verification: *

A Mule application exposes an HTTPS endpoint and is deployed to the CloudHub Shared Worker Cloud. All traffic to that Mule application must stay inside the AWS VPC.
To what TCP port do API invocations to that Mule application need to be sent?

• A.443
• B.8081
• C.8091
• D.8082

Comment: *

Name: *

Email: *

Verification: *

A company requires Mule applications deployed to CloudHub to be isolated between non-production and production environments. This is so Mule applications deployed to non-production environments can only access backend systems running in their customer-hosted non-production environment, and so Mule applications deployed to production environments can only access backend systems running in their customer-hosted production environment. How does MuleSoft recommend modifying Mule applications, configuring environments, or changing infrastructure to support this type of per-environment isolation between Mule applications and backend systems?

• A.Modify properties of Mule applications deployed to the production Anypoint Platform environments to prevent access from non-production Mule applications
• B.Configure firewall rules in the infrastructure inside each customer-hosted environment so that only IP addresses from the corresponding Anypoint Platform environments are allowed to communicate with corresponding backend systems
• C.Create non-production and production environments in different Anypoint Platform business groups
• D.Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments

Correct Answer: D

Correct answer: Create separate Anypoint VPCs for non-production and production environments, then configure connections to the backend systems in the corresponding customer-hosted environments.
*****************************************
>> Creating different Business Groups does NOT make any difference w.r.t accessing the non-prod and prod customer-hosted environments. Still they will be accessing from both Business Groups unless process network restrictions are put in place.
>> We need to modify or couple the Mule Application Implementations with the environment. In fact, we should never implements application coupled with environments by binding them in the properties. Only basic things like endpoint URL etc should be bundled in properties but not environment level access restrictions.
>> IP addresses on CloudHub are dynamic until unless a special static addresses are assigned. So it is not possible to setup firewall rules in customer-hosted infrastrcture. More over, even if static IP addresses are assigned, there could be 100s of applications running on cloudhub and setting up rules for all of them would be a hectic task, non-maintainable and definitely got a good practice.
>> The best practice recommended by Mulesoft (In fact any cloud provider), is to have your Anypoint VPCs seperated for Prod and Non-Prod and perform the VPC peering or VPN tunneling for these Anypoint VPCs to respective Prod and Non-Prod customer-hosted environment networks.
Reference:

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 modern API has its own software development lifecycle, which reduces the need for documentation and automation
• B.Each modem API must be treated like a product and designed for a particular target audience (for instance, mobile app developers)
• 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

Correct Answer: B

Correct Answers:
1. Each modern API must be treated like a product and designed for a particular target audience (for instance mobile app developers)
*****************************************

Comment: *

Name: *

Email: *

Verification: *

How are an API implementation, API client, and API consumer combined to invoke and process an API?

• A.The API consumer creates an API implementation, which receives API invocations from an API such that they are processed for an API client
• B.The API client creates an API consumer, which receives API invocations from an API such that they are processed for an API implementation
• C.The ApI consumer creates an API client, which sends API invocations to an API such that they are processed by an API implementation
• D.The ApI client creates an API consumer, which sends API invocations to an API such that they are processed by an API implementation

Comment: *

Name: *

Email: *

Verification: *