Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Amazon Exam ANS-C01 Topic 5 Question 40 Discussion

Actual exam question for Amazon's ANS-C01 exam
Question #: 40
Topic #: 5
[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:

Brigette
2 months ago
I'm not sure about option D. I think option E might be needed instead.
upvoted 0 times
...
Mariann
2 months ago
Indeed, C and D are the way to go. AWS CloudFormation makes it easy to automate the entire VPC peering setup process.
upvoted 0 times
...
Bobbie
3 months ago
Haha, imagine if we also needed to create a security group and a network interface just to set up a simple VPC peering connection! That would be overkill.
upvoted 0 times
Weldon
2 months ago
C: I know, setting up cross-account VPC peering connections can be complex, so it's great that AWS CloudFormation simplifies the process.
upvoted 0 times
...
Arlette
2 months ago
B: Agreed, it's nice that the template takes care of most of the setup for us.
upvoted 0 times
...
Cristal
2 months ago
A: Yeah, that would definitely be overkill. Good thing we only need the VPC peering connection components in the Originating account.
upvoted 0 times
...
...
Angella
3 months ago
I agree, C and D are the missing components. We need to create a route table entry and a VPC gateway attachment to complete the peering connection.
upvoted 0 times
Carry
2 months ago
D) Resources:VPCGatewayToRemoteVPC:Type: ''AWS::EC2::VPCGatewayAttachment''
upvoted 0 times
...
Thaddeus
2 months ago
C) Resources:newEC2Route:Type: AWS::EC2::Route
upvoted 0 times
...
Wendell
2 months ago
B) Resources:NetworkInterfaceToRemoteVPC:Type: ''AWS::EC2NetworkInterface''
upvoted 0 times
...
Aliza
2 months ago
A) Resources:NewEC2SecurityGroup:Type: AWS::EC2::SecurityGroup
upvoted 0 times
...
...
Yoko
3 months ago
I agree with Merrilee. Option C and D provide the required components for the connection to work properly.
upvoted 0 times
...
Merrilee
3 months ago
I think option C and D are necessary for creating the VPC peering connection.
upvoted 0 times
...
Markus
3 months ago
The VPC peering connection is already created in the Originating account, so we just need to add the necessary components to make it operational. Options C and D seem to be the correct ones.
upvoted 0 times
Gilma
2 months ago
Yes, I agree. Those components are necessary to establish the cross-account VPC peering connection.
upvoted 0 times
...
Marsha
3 months ago
I think we need to add Resources:newEC2Route and Resources:VPCGatewayToRemoteVPC to make the VPC peering connection operational.
upvoted 0 times
...
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77