A company ran out of IP address space in one of the Availability Zones in an AWS Region that the company uses. The Availability Zone that is out of space is assigned the 10.10.1.0/24 CIDR block. The…

Question

Options

• AUpdate the AWS::EC2::Subnet resource for the Availability Zone in the CloudFormation stack.
• BUpdate the AWS::EC2::VPC resource in the CloudFormation stack. Change the CidrBlock
• CCopy the CloudFormation stack. Set the AWS::EC2::VPC resource CidrBlock property to
• DCreate a new AWS::EC2::Subnet resource for the Availability Zone in the CloudFormation stack.

• A
  4% (2)
• B
  5% (3)
• C
  12% (7)
• D
  79% (45)

Explanation

Explanation

Why D is Correct: Creating a new subnet (AWS::EC2::Subnet) within the existing VPC leverages the available 10.10.1.0/22 CIDR capacity directly - since the VPC (10.10.0.0/16) already has room, you simply define an additional subnet in the same Availability Zone without disrupting existing resources or requiring complex changes.

Why the Distractors Are Wrong:

• Option A is wrong because updating the existing /24 subnet's CIDR block is not possible in AWS - subnet CIDR blocks are immutable after creation and cannot be resized.
• Option B is wrong because changing the VPC's CidrBlock in CloudFormation would replace the VPC (a destructive action), causing massive downtime and operational overhead - and the VPC already has sufficient capacity anyway.
• Option C is wrong because copying the entire CloudFormation stack is unnecessarily complex and would create duplicate infrastructure, introducing significant operational overhead.

Memory Tip

Think "Add, don't modify" - in AWS networking, you can't resize existing subnets, but you can always add new ones. If the VPC has space, the simplest solution is always a new subnet, not touching existing resources. When you see "LEAST operational overhead" with available VPC CIDR space, think new subnet.

No community discussion yet for this question.