A SysOps administrator is unable to launch Amazon EC2 instances into a VPC because there are no available private IPv4 addresses in the VPC. Which combination of actions must the SysOps…

The correct answer is A. Associate a secondary IPv4 CIDR block with the VPC C. Create a new subnet for the VPC. Every time you run out of IP's in your subnet, create a SECONDARY CIDR in your VPC. That will create a second local route in your RT's. Now you have more IP's available where you can create Remember: you CANNOT modify the CIDR of a VPC or subnet…

Submitted by akirajp· Mar 30, 2026Networking and Content Delivery

Question

A SysOps administrator is unable to launch Amazon EC2 instances into a VPC because there are no available private IPv4 addresses in the VPC. Which combination of actions must the SysOps administrator take to launch the instances? (Choose two.)

Options

AAssociate a secondary IPv4 CIDR block with the VPC
BAssociate a primary IPv6 CIDR block with the VPC
CCreate a new subnet for the VPC
DModify the CIDR block of the VPC
EModify the CIDR block of the subnet that is associated with the instances

How the community answered

(64 responses)

A
81% (52)
B
11% (7)
D
5% (3)
E
3% (2)

Explanation

Every time you run out of IP's in your subnet, create a SECONDARY CIDR in your VPC. That will create a second local route in your RT's. Now you have more IP's available where you can create Remember: you CANNOT modify the CIDR of a VPC or subnet. https://docs.aws.amazon.com/vpc/latest/userguide/configure-your-vpc.html#vpc-resize

Topics

#VPC CIDR expansion#subnet creation#IPv4 address exhaustion#VPC networking

Community Discussion

No community discussion yet for this question.

Full SOA-C02 Practice