An organization is sizing an Anypoint VPC to extend their internal network to Cloudhub.

An organization is sizing an Anypoint VPC to extend their internal network to Cloudhub.

For this sizing calculation, the organization assumes 150 Mule applications will be deployed among three (3) production environments and will use Cloudhub’s default zero-downtime feature. Each Mule application is expected to be configured with two (2) Cloudhub workers. This is expected to result in several Mule application deployments per hour.
A . 10.0.0.0/21(2048 IPs)
B . 10.0.0.0/22(1024IPs)
C . 10.0.0.0/23(512 IPs)
D . 10.0.0.0/24(256 IPs)

Answer: A

Explanation:

* When you create an Anypoint VPC, the range of IP addresses for the network must be specified in the form of a Classless Inter-Domain Routing (CIDR) block, using CIDR notation.

* This address space is reserved for Mule workers, so it cannot overlap with any address space used in your data center if you want to peer it with your VPC.

* To calculate the proper sizing for your Anypoint VPC, you first need to understand that the number of dedicated IP addresses is not the same as the number of workers you have deployed.

* For each worker deployed to CloudHub, the following IP assignation takes place: For better fault tolerance, the VPC subnet may be divided into up to four Availability Zones.

* A few IP addresses are reserved for infrastructure. At least two IP addresses per worker to perform at zero-downtime.

* Hence in this scenario 2048 IP’s are required to support the requirement.