New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon ANS-C01 Exam - Topic 6 Question 34 Discussion

Actual exam question for Amazon's ANS-C01 exam
Question #: 34
Topic #: 6
[All ANS-C01 Questions]

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.)

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Thea
3 months ago
Isn't the VPC peering connection enough on its own? Not sure about all this.
upvoted 0 times
...
Bonita
3 months ago
Totally agree, routes are a must for traffic flow!
upvoted 0 times
...
Solange
3 months ago
Wait, why would you need a network interface for peering? Seems off.
upvoted 0 times
...
Levi
4 months ago
I think a security group is also necessary for proper access.
upvoted 0 times
...
Staci
4 months ago
You definitely need a route to the remote VPC.
upvoted 0 times
...
Almeta
4 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?
upvoted 0 times
...
Cristy
4 months 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.
upvoted 0 times
...
Marti
4 months 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?
upvoted 0 times
...
Katlyn
5 months 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.
upvoted 0 times
...
Lynelle
5 months 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.
upvoted 0 times
...
Alita
5 months 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.
upvoted 0 times
...
Franchesca
5 months 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.
upvoted 0 times
...
Ira
5 months 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.
upvoted 0 times
...
Raina
5 months 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.
upvoted 0 times
...
Bernardine
5 months ago
I recall that using full text without permission is generally frowned upon, so I think options A and D are definitely not right.
upvoted 0 times
...
Juan
1 year 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.
upvoted 0 times
Lai
1 year ago
The AWS CloudFormation template already includes the necessary components for creating the cross-account VPC peering connection.
upvoted 0 times
...
Lindsay
1 year ago
The VPC peering connection allows communication between the VPCs without the need for a separate security group.
upvoted 0 times
...
Dana
1 year ago
Option A is not needed because the VPC peering connection handles the traffic between VPCs.
upvoted 0 times
...
...
Paris
1 year ago
Haha, I can already see someone choosing option B and trying to create a 'NetworkInterfaceToRemoteVPC' - that's just not how it works!
upvoted 0 times
Jesus
1 year ago
That makes sense, we need to focus on creating a new route and attaching a VPC gateway for the peering connection.
upvoted 0 times
...
Malcom
1 year ago
I think the necessary components are actually option C and option D.
upvoted 0 times
...
Mari
1 year ago
Yeah, creating a 'NetworkInterfaceToRemoteVPC' wouldn't help in setting up a VPC peering connection.
upvoted 0 times
...
Iluminada
1 year ago
I agree, option B is definitely not the right choice here.
upvoted 0 times
...
...
Elliott
1 year ago
But option A is for creating a security group, not for VPC peering connection.
upvoted 0 times
...
Theola
1 year ago
You're right, I misunderstood the question. Option E is definitely needed for the VPC peering connection.
upvoted 0 times
...
Julianna
1 year 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.
upvoted 0 times
Vicki
1 year ago
Yeah, you're right. Options C and D are the necessary components for creating the connection.
upvoted 0 times
...
Blythe
1 year ago
I think option E is not needed for creating a VPC peering connection.
upvoted 0 times
...
...
Levi
1 year 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.
upvoted 0 times
Avery
1 year ago
That makes sense, those components are essential for setting up the VPC peering connection between the two accounts.
upvoted 0 times
...
Tamekia
1 year ago
I think the additional components needed are Resources:newEC2Route:Type: AWS::EC2::Route and Resources:VPCGatewayToRemoteVPC:Type: ''AWS::EC2::VPCGatewayAttachment''
upvoted 0 times
...
...
Theola
1 year ago
I disagree, I believe option A and E are the correct components needed.
upvoted 0 times
...
Elliott
1 year ago
I think option C and D are necessary for creating the VPC peering connection.
upvoted 0 times
...

Save Cancel