QuestionQ9
MuleSoft application network conceptsAn organization has chosen a cloud-migration strategy that minimizes its own IT resources. At present, all its Mule applications run on premises, and an on-premises load balancer exposes all APIs under the base URL https://api.acme.com.
As part of this strategy, the organization intends to migrate all Mule applications and the on-premises load balancer to CloudHub 1.0.
What is the simplest and most cost-effective approach for deploying the Mule applications and load balancing while preserving the public URLs?
- A For each migrated Mule application, deploy an API proxy Mule application to CloudHub 1.0, with all traffic to the Mule applications routed through a CloudHub 1.0 Dedicated Load Balancer (DLB).Update the CNAME record to api.acme.com in the organization’s DNS server to point to the A record of the CloudHub 1.0 DLB.Apply mapping rules in the DLB to map each API proxy application to its corresponding Mule application.
- B Deploy the Mule applications to CloudHub 1.0.Create a CNAME record for api.acme.com in the CloudHub 1.0 Shared Load Balancer (SLB) that points to the A record of the on-premises load balancer.Apply mapping rules in the SLB to map URLs to their corresponding Mule applications.
- C Deploy the Mule applications to CloudHub 1.0.Update the CNAME record for api.acme.com in the organization’s DNS server to point 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.
- D Deploy the Mule applications to the CloudHub 1.0.Update the CNAME record for api.acme.com in the organization’s DNS server to point to the A record of a CloudHub 1.0 Dedicated Load Balancer (DLB).Apply mapping rules in the DLB to map URLs to their corresponding Mule applications.
Community Discussion