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 is correct.
NAT instance is created automatically by VPC wizard.
D
D, b/c Deletion of the VPC, possible only after terminating all instances within the VPC, deletes all the components with the VPC for e.g. subnets, security groups, network ACLs, route tables, Internet gateways, VPC peering connections, and DHCP options
d
C is correct answer.
D is correct according PassLeader tests
The wizard will create a NAT gateway by default, so d
Just tested, it will try to delete the vpc and the NAT gateway. So right answer: C
Just tested. i have created a VPC with public and private subnets using the wizard. once done, i was able to deleted the VPC without the need to manually delete the NAT or the router instance.
correct answer is C.
Good trick to pass this question – you cannot terminate a VPC, you can delete one 😉 Answer is D
Could be that this was changed by AWS. I guess NAT instance was replaced by NAT Gateway. And it seems that now, deletion of VPC is allowed.