nerdexam
Google

ASSOCIATE-CLOUD-ENGINEER · Question #271

You are running out of primary internal IP addresses in a subnet for a custom mode VPC. The subnet has the IP range 10.0.0.0/20, and the IP addresses are primarily used by virtual machines in the proj

The correct answer is A. Add a secondary IP range 10.1.0.0/20 to the subnet.. To provide more IP addresses for virtual machines in a subnet that is running out of primary IP addresses, a secondary IP range can be added to the existing subnet, which can then be used for alias IP configurations on the VMs.

Submitted by takeshi77· Mar 30, 2026Planning and configuring a cloud solution

Question

You are running out of primary internal IP addresses in a subnet for a custom mode VPC. The subnet has the IP range 10.0.0.0/20, and the IP addresses are primarily used by virtual machines in the project. You need to provide more IP addresses for the virtual machines. What should you do?

Options

  • AAdd a secondary IP range 10.1.0.0/20 to the subnet.
  • BChange the subnet IP range from 10.0.0.0/20 to 10.0.0.0/18.
  • CChange the subnet IP range from 10.0.0.0/20 to 10.0.0.0/22.
  • DConvert the subnet IP range from IPv4 to IPv6.

How the community answered

(37 responses)
  • A
    78% (29)
  • B
    14% (5)
  • C
    5% (2)
  • D
    3% (1)

Why each option

To provide more IP addresses for virtual machines in a subnet that is running out of primary IP addresses, a secondary IP range can be added to the existing subnet, which can then be used for alias IP configurations on the VMs.

AAdd a secondary IP range 10.1.0.0/20 to the subnet.Correct

Adding a secondary IP range to the subnet allows virtual machines to be configured with alias IP addresses from this new range, effectively providing more available IP addresses without modifying the existing primary range or requiring a new subnet.

BChange the subnet IP range from 10.0.0.0/20 to 10.0.0.0/18.

Subnet primary IP ranges cannot be changed or expanded after creation; doing so would typically require creating a new subnet and migrating resources, which is disruptive.

CChange the subnet IP range from 10.0.0.0/20 to 10.0.0.0/22.

Changing the subnet IP range from /20 to /22 would decrease the number of available IP addresses (a /22 is smaller than a /20), making the problem worse.

DConvert the subnet IP range from IPv4 to IPv6.

Converting to IPv6 addresses would provide a vast number of new addresses, but it's a significant network architecture change and does not directly solve the need for more IPv4 addresses for existing VMs in the current setup.

Concept tested: VPC subnet IP ranges and alias IPs

Source: https://cloud.google.com/vpc/docs/alias-ips

Topics

#VPC subnets#CIDR expansion#IP addressing#custom mode VPC

Community Discussion

No community discussion yet for this question.

Full ASSOCIATE-CLOUD-ENGINEER Practice