Bird
0
0

Which of the following is the correct way to create a VPC peering connection using AWS CLI?

easy📝 Configuration Q12 of 15
AWS - VPC Fundamentals
Which of the following is the correct way to create a VPC peering connection using AWS CLI?
Aaws ec2 create-route-table --vpc-id vpc-123abc
Baws ec2 create-vpc-peering-connection --vpc-id vpc-123abc --peer-vpc-id vpc-456def
Caws ec2 create-subnet --vpc-id vpc-123abc --cidr-block 10.0.0.0/24
Daws ec2 create-internet-gateway --vpc-id vpc-123abc
Step-by-Step Solution
Solution:
  1. Step 1: Identify the correct AWS CLI command for VPC peering

    The command to create a VPC peering connection is create-vpc-peering-connection with source and peer VPC IDs.
  2. Step 2: Check options

    aws ec2 create-vpc-peering-connection --vpc-id vpc-123abc --peer-vpc-id vpc-456def uses the correct command and parameters. Other options create unrelated resources like internet gateway, subnet, or route table.
  3. Final Answer:

    aws ec2 create-vpc-peering-connection --vpc-id vpc-123abc --peer-vpc-id vpc-456def -> Option B
  4. Quick Check:

    VPC peering CLI = create-vpc-peering-connection [OK]
Quick Trick: Look for 'create-vpc-peering-connection' command [OK]
Common Mistakes:
MISTAKES
  • Using internet gateway or subnet commands instead
  • Confusing route table creation with peering
  • Missing peer VPC ID parameter

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More AWS Quizzes