An organization is sizing an Anypoint VPC to extend their internal network to Cloudhub. For this sizing calculation, the organization assumes 150…

To calculate the required IP addresses, consider the peak usage during zero-downtime deployments. Each of the 150 applications requires its 2 workers plus an additional 2 workers for the new version, totaling 4 workers simultaneously per application during the update. Therefore, the total number of required IP addresses is 150 applications × 4 IPs/application = 600 IPs. The smallest CIDR block that can accommodate 600 IPs is /22, which provides 1024 addresses. This size meets the requirement while providing a reasonable buffer for future growth.

A. 10.0.0.0/21 (2048 IPs) is larger than necessary, which would be an inefficient allocation of IP address space.

C. 10.0.0.0/23 (512 IPs) is insufficient as it cannot accommodate the required 600 IP addresses needed for peak deployment activity.

D. 10.0.0.0/24 (256 IPs) is significantly too small for the calculated requirement of 600 IP addresses.

1. MuleSoft Documentation, "Anypoint VPC Sizing". This documentation explains that during a zero-downtime update, CloudHub provisions new workers before destroying the old ones, requiring double the number of IPs per application temporarily.

2. MuleSoft Documentation, "Zero-Downtime Updates". It states: "During the application update process, there is a brief period of time when both the old and new versions of the application are running and accepting traffic, each with its own set of workers."

3. MuleSoft Knowledge Base, Article "How to calculate the number of IPs required for a VPC". This article provides the formula: Number of applications Number of workers per application 2.