MCIA-Level-1 Exam Dumps | An organization plans to extend its Mule APIs to the EU (Frankfurt) region. Currently, all Mule applications

<< Prev Question Next Question >>

Question 66/120

An organization plans to extend its Mule APIs to the EU (Frankfurt) region.
Currently, all Mule applications are deployed to CloudHub 1.0 in the default North American region, from the North America control plane, following this naming convention: {API-name}-{environment} (for example, Orderssapi-dev, Orders-sapi--qa, Orders-sapi--prod, etc.).
There is no network restriction to block communications between APIs.
What strategy should be implemented in order to deploy the same Mule APIs to the CloudHub 1.0 EU region from the North America control plane, as well as to minimize latency between APIs and target users and systems in Europe?

A. In Runtime Manager, for each Mule application deployment, set the Region property to EU (Frankfurt) and reuse the same Mule application mame as in the North American region.
Communicate the new urls {API-name}-{environment}.de-ci.cloudhub.io to the consuming API clients In Europe.

B. In API Manager, set the Region property to EU (Frankfurt) to create an API proxy named {API-name}-proxy-{environment} for each Mule application.
Communicate the new url {API-name}-proxy-{environment}.de-c1.cloudhub.io to the consuming API clients In Europe.

C. In Runtime Manager, for each Mule application deployment, leave the Region property blank (default) and change the Mule application name to {API-name}-
{environment).de-cl.
Communicate the new urls {API-name}-{environment}.de-ci1.cloudhub.io to the consuming API clients in Europe.

D. In API Manager, leave the Region property blank (default) to deploy an API proxy named
{API-name}~proxy~- (environment}.de-cl for each Mule application.
Communicate the new url {API-name}-proxy-{environment}.de-cl.cloudhub.io to the consuming API clients in Europe.

Question 66/120

LEAVE A REPLY

Download PDF File