A rale limiting policy has been applied to a soap VI.2 API published in Clondhub. The API implementation catches errors in a global error handler on error propagate in the main flow for HTTP: RETRY_EXHAUSTED with HTTP status set to 429 and any with the HTTP status set to 500.
What is the expected H1TP status when the client exceeds the quota of the API calls?

• A.HTTP status 429 as defined in the HTTP:RETRY EXHAUSTED error handler in the API B. HTTP status 500 as defined in the ANY error handler in the API since an API:RETRY_EXHAUSTED will be generated
• B.HTTP status 400 from the rate-limiting policy violation since the call does not reach the back-end
• C.HTTP status 401 unauthorized for policy violation

Comment: *

Name: *

Email: *

Verification: *

What comparison is true about a CloudHub Dedicated Load Balancer (DLB) vs. the CloudHub Shared Load Balancer (SLB)?

• A.Only a DLB allows the configuration of a custom TLS server certificate
• B.Only the SLB can forward HTTP traffic to the VPC-internal ports of the CloudHub workers
• C.Both a DLB and the SLB allow the configuration of access control via IP whitelists
• D.Both a DLB and the SLB implement load balancing by sending HTTP requests to workers with the lowest workloads

Correct Answer: A

* Shared load balancers don't allow you to configure custom SSL certificates or proxy rules
* Dedicated Load Balancer are optional but you need to purchase them additionally if needed.
* TLS is a cryptographic protocol that provides communications security for your Mule app. TLS offers many different ways of exchanging keys for authentication, encrypting data, and guaranteeing message integrity.
* The CloudHub Shared Load Balancer terminates TLS connections and uses its own server-side certificate.
* Only a DLB allows the configuration of a custom TLS server certificate
* DLB enables you to define SSL configurations to provide custom certificates and optionally enforce two-way SSL client authentication.
* To use a DLB in your environment, you must first create an Anypoint VPC. Because you can associate multiple environments with the same Anypoint VPC, you can use the same dedicated load balancer for your different environments.
* MuleSoft Reference: https://docs.mulesoft.com/runtime-manager/dedicated-load-balancer-tutorial Additional Info on SLB Vs DLB:

Comment: *

Name: *

Email: *

Verification: *

Which type of communication is managed by a service mesh in a microservices architecture?

• A.Communication between microservices
• B.Communication between microservices developers
• C.Communication between microservices runtime administrators
• D.Communication between trading partner services

Comment: *

Name: *

Email: *

Verification: *

An integration team uses Anypoint Platform and follows MuleSoft's recommended approach to full lifecycle API development.
Which step should the team's API designer take before the API developers implement the AP! Specification?

• A.Generate test cases using MUnit so the API developers can observe the results of running the API
• B.Use the scaffolding capability of Anypoint Studio to create an API portal based on the API specification
• C.Publish the API specification to Exchange and solicit feedback from the API's consumers
• D.Use API Manager to version the API specification

Comment: *

Name: *

Email: *

Verification: *

An organization is migrating all its Mule applications to Runtime Fabric (RTF). None of the Mule applications use Mule domain projects.
Currently, all the Mule applications have been manually deployed to a server group among several customer hosted Mule runtimes.
Port conflicts between these Mule application deployments are currently managed by the DevOps team who carefully manage Mule application properties files.
When the Mule applications are migrated from the current customer-hosted server group to Runtime Fabric (RTF), fo the Mule applications need to be rewritten and what DevOps port configuration responsibilities change or stay the same?

• A.Yes, the Mule applications Must be rewritten
  DevOps No Longer needs to manage port conflicts between the Mule applications
• B.Yes, the Mule applications Must be rewritten
  DevOps Must Still Manage port conflicts.
• C.NO, The Mule applications do NOT need to be rewritten
  DevOps MUST STILL manage port conflicts
• D.NO, the Mule applications do NO need to be rewritten
  DevOps NO LONGER needs to manage port conflicts between the Mule applications.

Comment: *

Name: *

Email: *

Verification: *