A user has created a VPC with CIDR 20.0.0.0/16 using the wizard. The user has created public and VPN only
subnets along with hardware VPN access to connect to the user’s data centre. The user has not yet launched
any instance as well as modified or deleted any setup. He wants to delete this VPC from the console. Will the
console allow the user to delete the VPC?
A.
Yes, the console will delete all the setups and also delete the virtual private gateway
B.
No, the console will ask the user to manually detach the virtual private gateway first and then allow
deleting the VPC
C.
Yes, the console will delete all the setups and detach the virtual private gateway
D.
No, since the NAT instance is running
Explanation:
The user can create subnets as per the requirement within a VPC. If the user wants to connect VPC from his
own data centre, he can setup a public and VPN only subnet which uses hardware VPN access to connect with
his data centre. When the user has configured this setup with Wizard, it will create a virtual private gateway to
route all traffic of the VPN subnet. If the virtual private gateway is attached with VPC and the user deletes the
VPC from the console it will first detach the gateway automatically and only then delete the VPC.
C
0
0
Should be D
0
0
C
Deleting the VPC will also remove the NAT instance (ie Internet Gateway) if it exists. It will detach the VPG so that it can be used with another VPC in the future.
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html#working-with-vpcs
0
0
A
If you have a VPN connection, you don’t have to delete it or the other components related to the VPN (such as the customer gateway and virtual private gateway). If you plan to use the customer gateway with another VPC, we recommend that you keep the VPN connection and the gateways. Otherwise, your network administrator must configure the customer gateway again after you create a new VPN connection.
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Subnets.html#working-with-vpcs
0
0
C
0
0
c
0
0
Option C is correct.
VPC with Public and Private Subnets and Hardware VPN Access:
This configuration adds an IPsec Virtual Private Network (VPN) connection between your Amazon VPC and your data center – effectively extending your data center to the cloud while also providing direct access to the Internet for public subnet instances in your Amazon VPC.
Creates:
A /16 network with two /24 subnets. One subnet is directly connected to the Internet while the other subnet is connected to your corporate network via IPsec VPN tunnel. (VPN charges apply.)
No NAT instance created in this case.
0
0
Deleting Your VPC:
You can delete your VPC at any time. However, you must terminate all instances in the VPC first. When you delete a VPC using the Amazon VPC console, we delete all its components, such as subnets, security groups, network ACLs, Internet gateways, VPC peering connections, and DHCP options.
If you have a VPN connection, you don’t have to delete it or the other components related to the VPN (such as the customer gateway and virtual private gateway). If you plan to use the customer gateway with another VPC, we recommend that you keep the VPN connection and the gateways. Otherwise, your network administrator must configure the customer gateway again after you create a new VPN connection.
0
0