Free MULESOFT-INTEGRATION-ARCHITECT-I Web TestEngine Demo

Q18 Single choice

An organization has decided on a cloud migration strategy to minimize the organization's own IT resources. Currently the organization has all of its new applications running on its own premises and uses an on-premises load balancer that exposes all APIs under the base URL (https://api.rutujar.com).

As part of migration strategy, the organization is planning to migrate all of its new applications and load balancer CloudHub.

What is the most straightforward and cost-effective approach to Mule application deployment and load balancing that preserves the public URL's?

A
Deploy the Mule application to Cloudhub Create a CNAME record for base URL( httpsr://api.rutujar.com) in the Cloudhub shared load balancer that points to the A record of theon-premises load balancer Apply mapping rules in SLB to map URLto
their corresponding Mule applications
B
Deploy the Mule application to Cloudhub Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the Cloudhub dedicated load balancer Apply mapping rules in DLB to map URLto their corresponding Mule applications
C
Deploy the Mule application to Cloudhub
Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the CloudHub shared load balancer Apply mapping rules in SLB to map URLto
their corresponding Mule applications
D
For each migrated Mule application, deploy an API proxy application to Cloudhub with all traffic to the mule applications routed through a Cloud Hub Dedicated load balancer (DLB) Update a CNAME record for base URL ( https://api.rutujar.com) in the organization's DNS server to point to the A record of the CloudHub dedicated load balancer Apply mapping rules in DLB to map each API proxy application who is responding new application

MULESOFT-INTEGRATION-ARCHITECT-I Web TestEngine demo