You have established a VPN connection between your on-premises and an AWS VPC. You also need to ensure that instances in the VPC can reach the Internet. So you have also attached an Internet gateway. How would you set up the route tables to ensure that traffic can flow via the VPN and the Internet?

Answer options:

A.Set up 2 Route tables. One route table with a default route to the Internet and another one with the default route to the Virtual Private gateway. Attach the Route tables to the subnet in the VPC.B.Set up one route table. Add one route of 0.0.0.0/0 to the Internet and one specific prefix route for the Virtual Private gateway. Attach the Route table to the subnet in the VPC.C.Set up one route table. Add one route of 0.0.0.0/0 to the Internet and another route of 0.0.0.0/0 route for the Virtual Private gateway. Attach the Route table to the subnet in the VPC.D.Set up 2 Route tables. One route table with a default route to the Internet and another one with the specific prefix route to the Virtual Private gateway. Attach the Route tables to the subnet in the VPC.

Answer – B
You should create a specific route for the Virtual Private gateway.
The AWS Documentation mentions the following.
You can use an AWS managed VPN connection to enable instances in your VPC to communicate with your own network. To do this, create and attach a virtual private gateway to your VPC, and then add a route with the destination of your network and a target of the virtual private gateway (vgw-xxxxxxxx). You can then create and configure your VPN connection.
Options A and D are invalid because you can only have one route table for a subnet.
Option C is invalid since you need to have a more specific route for the Virtual Private gateway.
For more information on Route tables, please refer to the below URL
https://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_Route_Tables.html