Question : QuickTechie.com Inc has three different AWS acount for Admin, Billing and Technical Team, all are in three different regions. The Technical Team created a file sharing site where all the technology employees data is uploaded. The Admin team uploads data about the all employee attendance to their DB hosted in the VPC. The billing team needs to access data from the technology team to know the employees to calculate the salary based on the attendance. How QuickTechie can set up this configuration in AWS? 1. Setup VPC peering for the VPCs of Admin and Billing. 2. Setup VPC peering for the VPCs of Admin and Tehnology Team 3. Setup VPC peering for the VPCs of Billing and technology Team as well as between the VPCs of Billing and Admin. 4. It is not possible to configure VPC peering since each department in separate regions.
Correct Answer : 4 Explanation: To create a VPC peering connection with another VPC, you need to be aware of the following limitations and rules:
You cannot create a VPC peering connection between VPCs that have matching or overlapping CIDR blocks.
You cannot create a VPC peering connection between VPCs in different regions.
You have a limit on the number active and pending VPC peering connections that you can have per VPC. For more information about VPC limits, see Amazon VPC Limits in the Amazon VPC User Guide.
VPC peering does not support transitive peering relationships; in a VPC peering connection, your VPC will not have access to any other VPCs that the peer VPC may be peered with. This includes VPC peering connections that are established entirely within your own AWS account. For more information about unsupported peering relationships, see Invalid VPC Peering Connection Configurations. For examples of supported peering relationships, see VPC Peering Scenarios.
You cannot have more than one VPC peering connection between the same two VPCs at the same time.
The Maximum Transmission Unit (MTU) across a VPC peering connection is 1500 bytes.
A placement group can span peered VPCs; however, you will not get full-bisection bandwidth between instances in peered VPCs. For more information about placement groups, see Placement Groups in the Amazon EC2 User Guide for Linux Instances.
Unicast reverse path forwarding in VPC peering connections is not supported. For more information, see Routing for Response Traffic.
You cannot reference a security group from the peer VPC as a source or destination for ingress or egress rules in your security group. Instead, reference CIDR blocks of the peer VPC as the source or destination of your security group's ingress or egress rules.
Private DNS values cannot be resolved between instances in peered VPCs.
Question : In QuickTechie.com Inc, you have two departments Admin and HR both have AWS accounts. You work as a technical member with Admin department. HR department has their own VPC and similarly Admin. Now as a admin you wish to make VPC peering with HR VPC. To enable the flow of traffic between the peer VPCs (Admin and HR) using private IP addresses, you have to 1. add a route to one or more of your (Admin) VPC's route tables that points to the IP address range of the peer VPC 2. The owner of the peer VPC (HR) adds a route to one of their VPC's route tables that points to the IP address range of your VPC
3. Both 1 and 2 4. For Peering the VPC's private IP addresses are not supported.
Correct Answer : 3 Explanation: To establish a VPC peering connection, the owner of the requester VPC (or local VPC) sends a request to the owner of the peer VPC to create the VPC peering connection. The peer VPC can be owned by you, or another AWS account. The owner of the peer VPC has to accept the VPC peering connection request to activate the VPC peering connection. To enable the flow of traffic between the peer VPCs using private IP addresses, add a route to one or more of your VPC's route tables that points to the IP address range of the peer VPC. The owner of the peer VPC adds a route to one of their VPC's route tables that points to the IP address range of your VPC.
Question : You have a VPC peering connection (pcx-) between VPC A and VPC B, which are in the same AWS account, and do not have overlapping CIDR blocks.
You set up VPC A for your accounting records, and VPC B for your financial records, and now you want each VPC to be able to access each others' resources without restriction.
Select the correct route tables for each VPC point to the relevant VPC peering connection to access the entire CIDR block of the peer VPC. 1. A 2. B 3. C 4. A,B 5. B,C
2. Create two separate VPCs in different zones. Setup two EC2 instances by installing a DB in the two different VPCs and enable the failover mechanism. Setup the App server with one of the public subnets of any VPC. 3. Create a VPC with one private and one public subnet in separate AZs. Setup the EC2 instance with a DB in the private subnet and the web application in a public subnet. 4. Create a VPC with two private subnets and a public subnet. In separate AZs and setup RDS with the multi AZ feature by creating a subnet group. Launch a web application in the public subnet.