Your company has provisioned 2000 virtual machines (VMs) in the private subnet of your Virtual Private Cloud (VPC) in the us-east1 region. You need to configure each VM to have a minimum of 128 TCP co

Question

Options

• AConfigure the NAT gateway in manual allocation mode, allocate 2 NAT IP addresses, and update
• BCreate a second Cloud NAT gateway with the default minimum number of ports configured per
• CUse the default Cloud NAT gateway's NAT proxy to dynamically scale using a single NAT IP
• DUse the default Cloud NAT gateway to automatically scale to the required number of NAT IP
• EConfigure the NAT gateway in manual allocation mode, allocate 4 NAT IP addresses, and update

• A
  12% (5)
• B
  5% (2)
• C
  2% (1)
• D
  81% (34)

Explanation

Each Cloud NAT IP address provides 64,512 usable ports. With 2,000 VMs each requiring a minimum of 128 simultaneous TCP connections, the total required ports are 2,000 × 128 = 256,000. Dividing by 64,512 per IP yields approximately 3.97, meaning at least 4 NAT IP addresses are needed. Option E satisfies this by manually allocating 4 IPs and configuring the minimum ports per VM to 128, providing 4 × 64,512 = 258,048 total ports - sufficient for all VMs simultaneously. Option D uses automatic NAT IP allocation mode, where Cloud NAT dynamically scales the number of IPs to meet demand, making it equally valid. Option A allocates only 2 IPs (129,024 ports for 2,000 VMs = ~64 ports each), which is insufficient for 128 connections per VM. Option B adding a second gateway without sufficient IP addresses does not resolve the capacity issue. Option C implies a single IP can auto-scale, which is incorrect - Cloud NAT auto-scales by adding more IPs.

No community discussion yet for this question.