A user has created a VPC with public and private subnets using the VPC wizard. The user has not
launched any instance manually and is trying to delete the VPC. What will happen in this
scenario?
A.
It will not allow to delete the VPC as it has subnets with route tables
B.
It will not allow to delete the VPC since it has a running route instance
C.
It will terminate the VPC along with all the instances launched by the wizard
D.
It will not allow to delete the VPC since it has a running NAT instance
Explanation:
A Virtual Private Cloud (VPC. is a virtual network dedicated to the user’s AWS account. A user can
create a subnet with VPC and launch instances inside that subnet. If the user has created a public
private subnet, the instances in the public subnet can receive inbound traffic directly from the
Internet, whereas the instances in the private subnet cannot. If these subnets are created with
Wizard, AWS will create a NAT instance with an elastic IP. If the user is trying to delete the VPC it
will not allow as the NAT instance is still running.
D
D
Old way must have had NAT instances come with VPC’s where today, NAT gateways don’t get automatically stood up with VPC’s ? See question #209. The answer is opposite.
Answer is D to pass exam
Explanation:
A Virtual Private Cloud (VPC) is a virtual network dedicated to the user’s AWS account. A user can create a subnet with VPC and launch instances inside that subnet. If the user has created a public private subnet, the instances in the public subnet can receive inbound traffic directly from the Internet, whereas the instances in the private subnet cannot. If these subnets are created with Wizard, AWS will create a NAT instance with an elastic IP. If the user is trying to delete the VPC it will not allow as the NAT instance is still running.