What is the most straight-forward and cost effective approach to the Mule applications deployment and load balancing that preserves the public URLs?

An organization has decided on a cloudhub migration strategy that aims to minimize the organizations own IT resources. Currently, the organizational has all of its Mule applications running on its own premises and uses an 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 the Mule applications deployment and load balancing that preserves the public URLs?

A. Deploy the Mule applications to Cloudhub

Update the CNAME record for an api.acme.com in the organizations 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

B. For each migrated Mule application, deploy an API proxy Mule application to Cloudhub with all applications under the control of a dedicated load balancer (CLB)

Update the CNAME record for api.acme.com in the organization 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 applications

C. Deploy the Mule applications to Cloudhub

Create CNAME record for api.acme.com in the Cloudhub Shared load balancer (SLB) pointing to the A record of the on-premise load balancer

Apply mapping rules in the SLB to map URLs to their corresponding Mule applications

D. Deploy the Mule applications to Cloudhub

Update the CNAME record for api.acme.com in the organization 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.