A SysOps administrator creates two VPCs, VPC1 and VPC2, in a company's AWS account The SysOps administrator deploys a Linux Amazon EC2 instance in VPC1 and deploys an Amazon RDS for MySQL DB…

Question

Options

• AEnter the DB instance connection string into the VPC1 route table.
• BConfigure VPC peering between the two VPCs.
• CAdd the same IPv4 CIDR range for both VPCs.
• DConnect to the DB instance by using the DB instance's public IP address.

• A
  4% (2)
• B
  77% (41)
• C
  6% (3)
• D
  13% (7)

Explanation

VPC Peering (B) is correct because it creates a private network connection between two VPCs, allowing resources in each to communicate using private IP addresses as if they were on the same network - exactly what's needed for a private RDS instance in VPC2 to be reachable from EC2 in VPC1.

Why the distractors fail:

• A is wrong because route tables route traffic to destinations (like subnets or gateways), not connection strings - a connection string is an application-layer concept, not a network routing concept.
• C is wrong because overlapping CIDR ranges actually prevent VPC peering; VPCs must have non-overlapping CIDR blocks, and simply sharing a range doesn't create connectivity.
• D is wrong because the DB instance is in a private subnet, meaning it has no public IP address and is intentionally unreachable from the internet.

Memory tip: Think of VPC Peering as building a private "bridge" between two isolated neighborhoods (VPCs). Without that bridge, traffic between them has no path - no matter how close the neighborhoods are on a map, they're cut off until you explicitly connect them.

No community discussion yet for this question.