Certified MuleSoft Platform Integration Architect

By Salesforce · Question Mode

QuestionQ52

VerifiedDesigning for the runtime plane technology architecture

An organization intends to extend its Mule APIs to the EU (Frankfurt) region. At present, all Mule applications are deployed to CloudHub 1.0 in the default North American region from the North America control plane, using this naming convention:

\{API-name\}-\{environment\} (for example, Orders-sapi-dev, Orders-sapi-qa, Orders-sapi-prod, etc.).

There are no network restrictions blocking communications between APIs.

Which strategy should be implemented to deploy the same Mule APIs to the CloudHub 1.0 EU region from the North America control plane while minimizing latency between APIs and target users and systems in Europe?

Explanation

CloudHub 1.0 deployments use Runtime Manager’s Region setting. Selecting EU (Frankfurt) places the application and its load balancer in that region, reducing latency to European users and systems. In the North America control plane, Frankfurt uses the de-c1 DNS suffix, so an application named {API-name}-{environment} is accessed at {API-name}-{environment}.de-c1.cloudhub.io.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!