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

Comment: *

Name: *

Email: *

Verification: *

What Mule application can have API policies applied by
Anypoint Platform to the endpoint exposed by that Mule application?
A) A Mule application that accepts requests over HTTP/1.x

B) A Mule application that accepts JSON requests over TCP but is NOT required to provide a response

C) A Mute application that accepts JSON requests over WebSocket

D) A Mule application that accepts gRPC requests over HTTP/2

• A.Option A
• B.Option B
• C.Option C
• D.Option D

Comment: *

Name: *

Email: *

Verification: *

An API experiences a high rate of client requests (TPS) vwth small message paytoads. How can usage limits be imposed on the API based on the type of client application?

• A.Use an SLA-based rate limiting policy and assign a client application to a matching SLA tier based on its type
• B.Use a spike control policy that limits the number of requests for each client application type
• C.Use a cross-origin resource sharing (CORS) policy to limit resource sharing between client applications, configured by the client application type
• D.Use a rate limiting policy and a client ID enforcement policy, each configured by the client application type

Comment: *

Name: *

Email: *

Verification: *

An Anypoint Platform organization has been configured with an external identity provider (IdP) for identity management and client management. What credentials or token must be provided to Anypoint CLI to execute commands against the Anypoint Platform APIs?

• A.The credentials provided by the IdP for identity management
• B.The credentials provided by the IdP for client management
• C.An OAuth 2.0 token generated using the credentials provided by the IdP for client management
• D.An OAuth 2.0 token generated using the credentials provided by the IdP for identity management

Comment: *

Name: *

Email: *

Verification: *

What is true about automating interactions with Anypoint Platform using tools such as Anypoint Platform REST APIs, Anypoint CU, or the Mule Maven plugin?

• A.Access to Anypoint Platform APIs and Anypoint CU can be controlled separately through the roles and permissions in Anypoint Platform, so that specific users can get access to Anypoint CLI white others get access to the platform APIs
• B.Anypoint Platform APIs can ONLY automate interactions with CloudHub, while the Mule Maven plugin is required for deployment to customer-hosted Mule runtimes
• C.By default, the Anypoint CLI and Mule Maven plugin are NOT included in the Mule runtime, so are NOT available to be used by deployed Mule applications
• D.API policies can be applied to the Anypoint Platform APIs so that ONLY certain LOBs have access to specific functions

Comment: *

Name: *

Email: *

Verification: *