MuleSoft Certified Integration Architect – Level 1 — Question 100

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?

Answer options

• 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. 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
• 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. 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

Correct answer: A

Explanation

Option A is correct because it directly deploys the Mule applications to CloudHub and updates the CNAME record to point to the CloudHub Shared Load Balancer (SLB), ensuring the public URLs are preserved. Options B and C incorrectly involve pointing to an on-premises load balancer or a dedicated load balancer, which complicates the deployment and does not minimize IT resources. Option D suggests creating API Proxy applications, which adds unnecessary complexity and management overhead.