A company has an AWS account that contains three VPCs (Dev, Test, and Prod) in the same region. Test is
peered to both Prod and Dev. All VPCs have non-overlapping CIDR blocks. The company wants to push minor
code releases from Dev to Prod to speed up time to market. Which of the following options helps the company
accomplish this?
A.
Create a new peering connection Between Prod and Dev along with appropriate routes.
B.
Create a new entry to Prod in the Dev route table using the peering connection as the target.
C.
Attach a second gateway to Dev. Add a new entry in the Prod route table identifying the gateway as the
target.
D.
The VPCs have non-overlapping CIDR blocks in the same account. The route tables contain local routes for
all VPCs.
Explanation:
http://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/vpc-pg.pdf
A
0
0
A
Source: http://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/vpc-pg.pdf#create-vpc-peering-connection
0
0
D
0
2
A
There are two VPCpeering connections:VPC A is peered with both VPC B and VPC C.VPC B and VPC C are not peered,and you cannot use VPC A as a transit point for peering between VPC B and VPC C. If you want to enablerouting of traffic between VPC B and VPC C, you must create a unique VPC peering connection between them
0
0
answer is a Check JM
0
0
A
0
0
Answer is A
0
0
A
0
0
Code moves from Dev to Test and then Test to Prod. That is the normal cycle and the peering is already there.
Answer is D.
1
1
Sorry Answer is C
0
0
A
‘NO TRANSITIVE PEERING’
DEV–> TEST –> PROD —-> NOT POSSIBLE
DEV—> PEERING CONNECTION(over Private Network) —> PROD
0
0
A is a correct answer. There is no other way to connect directly from Dev to Prod as is asked in the question.
0
0
D cannot be the answer – non-overlapping IP addresses is a prerequisite of VPC Peering but it has to be setup explicitly for it to work. And being in the same account does not mean that they can communicate by default – VPC peering has to be setup first.
1
0
A
http://jayendra-patil.blogspot.in/2016/03/aws-vpc-peering.html
0
0
A
Please see p55 of this link:
http://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/vpc-pg.pdf#create-vpc-peering-connection
0
0
Answer is A
One VPC Peered with Multiple VPCs
http://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/peering-configurations-full-access.html#one-to-many-vpcs-full-access
VPC A is peered with all other VPCs, but the other VPCs are not peered to each other. The VPCs are in the same AWS account and do not have overlapping CIDR blocks.
Note
None of the other VPCs can send traffic directly to each other through VPC A. VPC peering does not support transitive peering relationships, nor edge to edge routing. You must create a VPC peering connection between the other VPCs in order to route traffic between them
0
0
A – transitive peering is not supported
0
0
A
0
0
Seriously… who is this idiot giving answers in Green. Almost 60% of them are incorrect.
Such a waste of time..
Causing unnecessary doubt.
0
0
A is a correct answer.
0
0
Correct Answer is A:
http://docs.aws.amazon.com/AmazonVPC/latest/PeeringGuide/vpc-pg.pdf
See page 23 of this document.
0
0