MENU
An AWS CloudFormation template is being used to create a VPC peering connection between two existing operational VPCs, each belonging to a different AWS account. All necessary components in the 'Remote' (receiving) account are already in place.
The template below creates the VPC peering connection in the Originating account. It contains these components:
AWSTemplateFormation Version: 2010-09-09
Parameters:
Originating VCId:
Type: String
RemoteVPCId:
Type: String
RemoteVPCAccountId:
Type: String
Resources:
newVPCPeeringConnection:
Type: 'AWS::EC2::VPCPeeringConnection'
Properties:
VpcdId: !Ref OriginatingVPCId
PeerVpcId: !Ref RemoteVPCId
PeerOwnerId: !Ref RemoteVPCAccountId
Which additional AWS CloudFormation components are necessary in the Originating account to create an operational cross-account VPC peering connection with AWS CloudFormation? (Select two.)
Suggested Answer: C, E
Get Premium ANS-C01 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
TH
Thea
11 months ago
Isn't the VPC peering connection enough on its own? Not sure about all this.
BO
Bonita
11 months ago
Totally agree, routes are a must for traffic flow!
SO
Solange
11 months ago
Wait, why would you need a network interface for peering? Seems off.
LE
Levi
11 months ago
I think a security group is also necessary for proper access.
ST
Staci
12 months ago
You definitely need a route to the remote VPC.
AL
Almeta
12 months ago
I’m a bit confused about the network interface option. I don’t recall needing that for a basic peering setup, but maybe it’s required for specific configurations?
CR
Cristy
1 year ago
I feel like we practiced a similar question where we had to set up routes for peering connections. I think option C is definitely one of the answers we need.
MA
Marti
1 year ago
I'm not entirely sure, but I think we might need a security group to allow traffic between the VPCs. Option A could be relevant, right?
KA
Katlyn
1 year ago
I remember we discussed the importance of having a route in the route table for the peering connection to work properly. So, I think option C might be necessary.
LY
Lynelle
1 year ago
Ah, I see now. In addition to the VPC peering connection, we'll likely need to set up a VPC gateway attachment and a route table entry to route traffic to the remote VPC. I'm feeling more confident about this after reviewing the options.
AL
Alita
1 year ago
Okay, let me think this through. I know we need to set up the VPC peering connection itself, but there might be some additional routing or security group configurations needed as well. I'll carefully review the question and options to determine the correct answer.
FR
Franchesca
1 year ago
Hmm, I'm a bit unsure about the additional components needed here. I'll need to review the CloudFormation documentation to make sure I understand the full setup process for a cross-account VPC peering connection.
IR
Ira
1 year ago
This looks like a straightforward VPC peering connection setup, but I'll need to double-check the additional components required in the Originating account. I'm pretty confident I can figure this out.
RA
Raina
1 year ago
This seems like a tricky one. The template provided creates the VPC peering connection, but there could be other pieces required to make it fully operational. I'll need to think through the end-to-end setup and consider all the possible components.
BE
Bernardine
1 year ago
I recall that using full text without permission is generally frowned upon, so I think options A and D are definitely not right.
JU
Juan
2 years ago
I'm surprised option A isn't one of the correct answers. You'd think you'd need a security group to allow traffic between the VPCs, but I guess the peering connection takes care of that.
LA
Lai
2 years ago
The AWS CloudFormation template already includes the necessary components for creating the cross-account VPC peering connection.
LI
Lindsay
2 years ago
The VPC peering connection allows communication between the VPCs without the need for a separate security group.
DA
Dana
2 years ago
Option A is not needed because the VPC peering connection handles the traffic between VPCs.
PA
Paris
2 years ago
Haha, I can already see someone choosing option B and trying to create a 'NetworkInterfaceToRemoteVPC' - that's just not how it works!
JE
Jesus
2 years ago
That makes sense, we need to focus on creating a new route and attaching a VPC gateway for the peering connection.
MA
Malcom
2 years ago
I think the necessary components are actually option C and option D.
MA
Mari
2 years ago
Yeah, creating a 'NetworkInterfaceToRemoteVPC' wouldn't help in setting up a VPC peering connection.
IL
Iluminada
2 years ago
I agree, option B is definitely not the right choice here.
EL
Elliott
2 years ago
But option A is for creating a security group, not for VPC peering connection.
TH
Theola
2 years ago
You're right, I misunderstood the question. Option E is definitely needed for the VPC peering connection.
JU
Julianna
2 years ago
I'm not sure why option E is there, it doesn't seem relevant to the question. But yeah, C and D are the right answers.
VI
Vicki
2 years ago
Yeah, you're right. Options C and D are the necessary components for creating the connection.
BL
Blythe
2 years ago
I think option E is not needed for creating a VPC peering connection.
LE
Levi
2 years ago
The correct answers are C) Resources:newEC2Route:Type: AWS::EC2::Route and D) Resources:VPCGatewayToRemoteVPC:Type: ''AWS::EC2::VPCGatewayAttachment''. These components are necessary to create routing between the two VPCs and establish the peering connection.
AV
Avery
2 years ago
That makes sense, those components are essential for setting up the VPC peering connection between the two accounts.
TA
Tamekia
2 years ago
I think the additional components needed are Resources:newEC2Route:Type: AWS::EC2::Route and Resources:VPCGatewayToRemoteVPC:Type: ''AWS::EC2::VPCGatewayAttachment''
TH
Theola
2 years ago
I disagree, I believe option A and E are the correct components needed.
EL
Elliott
2 years ago
I think option C and D are necessary for creating the VPC peering connection.