An organization currently uses a multi-node Mule runtime deployment model within their datacenter, so each Mule runtime hosts several Mule applications. The organization is planning to transition to a deployment model based on Docker containers in a Kubernetes cluster. The organization has already created a standard Docker image containing a Mule runtime and all required dependencies (including a JVM), but excluding the Mule application itself.
What is an expected outcome of this transition to container-based Mule application deployments?

• A.Required redesign of Mule applications to follow microservice architecture principles
• B.Required change to the URL endpoints used by clients to send requests to the Mule applications
• C.Required migration to the Docker and Kubernetes-based Anypoint Platform - Private Cloud Edition
• D.Guaranteed consistency of execution environments across all deployments of a Mule application

Comment: *

Name: *

Email: *

Verification: *

A Mule application currently writes to two separate SQL Server database instances across the internet using a single XA transaction. It is proposed to split this one transaction into two separate non-XA transactions with no other changes to the Mule application.
What non-functional requirement can be expected to be negatively affected when implementing this change?

• A.Availability
• B.Response time
• C.Consistency
• D.Throughput

Comment: *

Name: *

Email: *

Verification: *

A popular retailer is designing a public API for its numerous business partners. Each business partner will invoke the API at the URL https://api.acme.com/partners/v1. The API implementation is estimated to require deployment to 5 CloudHub workers.
The retailer has obtained a public X.509 certificate for the name api.acme.com, signed by a reputable CA, to be used as the server certificate.
Where and how should the X.509 certificate and Mule applications be used to configure load balancing among the 5 CloudHub workers, and what DNS entries should be configured in order for the retailer to support its numerous business partners?

• A.Add the X.509 certificate to the Mule application's deployable archive, then configure a CloudHub Dedicated Load Balancer (DLB) for each of the Mule application's CloudHub workers Create a CNAME for api.acme.com pointing to the DLB's A record
• B.Add the X.509 certificate to a CloudHub Dedicated Load Balancer (DLB), not to the Mule application Create a CNAME for api.acme.com pointing to the DLB's A record
• C.Add the X.509 certificate to the Mule application's deployable archive, then configure the CloudHub Shared Load Balancer (SLB) for each of the Mule application's CloudHub workers Create a CNAME for api.acme.com pointing to the SLB's A record
• D.Add the X.509 certificate to the CloudHub Shared Load Balancer (SLB), not to the Mule application Create a CNAME for api.acme.com pointing to the SLB's A record

Comment: *

Name: *

Email: *

Verification: *

An organization has decided on a cloud migration strategy that aims to minimize the organization's own IT resources. Currently, the organization has all of its Mule applications running on its own premises and uses an on-premises load balancer that exposes all APIs under the base URL https://api.acme.com.
As part of the migration strategy, the organization plans to migrate all of its Mule applications and load balancer to CloudHub.
What is the most straight-forward and cost-effective approach to Mule application deployment and load balancing that preserves the public URLs?

• A.Deploy the Mule applications to CloudHub
  Update the CNAME record for api.acme.com in the organization's DNS server pointing to the A record of the CloudHub Shared Load Balancer (SLB) Apply mapping rules in the SLB to map URLs to their corresponding Mule applications
• B.For each migrated Mule application, deploy an API Proxy Mule application to CloudHub, with all applications under the control of a CloudHub dedicated load balancer (DLB) Update the CNAME record for api.acme.com in the organization's DNS server pointing to the A record of a CloudHub dedicated load balancer (DLB) Apply mapping rules in the DLB to map each API Proxy application to its corresponding Mule application
• C.Deploy the Mule applications to CloudHub
  Update the CNAME record for api.acme.com in the organization's DNS server pointing to the A record of a CloudHub dedicated load balancer (DLB) Apply mapping rules in the DLB to map URLs to their corresponding Mule applications
• D.Deploy the Mule applications to CloudHub
  Create a CNAME record for api.acme.com in the CloudHub Shared Load Balancer (SLB) pointing to the A record of the on-premises load balancer Apply mapping rules in the SLB to map URLs to their corresponding Mule applications

Comment: *

Name: *

Email: *

Verification: *

An organization is designing the following two Mule applications that must share data via a common persistent object store instance:
- Mule application P will be deployed within their on-premises datacenter.
- Mule application C will run on CloudHub in an Anypoint VPC.
The object store implementation used by CloudHub is the Anypoint Object Store v2 (OSv2).
what type of object store(s) should be used, and what design gives both Mule applications access to the same object store instance?

• A.Application C uses the Object Store connector to access a persistent object Application P accesses the persistent object store via the Object Store REST API
• B.Application C and P both use the Object Store connector to access the Anypoint Object Store v2
• C.Application C and P both use the Object Store connector to access a persistent object store
• D.Application P uses the Object Store connector to access a persistent object store Application C accesses this persistent object store via the Object Store REST API through an IPsec tunnel

Comment: *

Name: *

Email: *

Verification: *