A SysOps administrator is troubleshooting a connectivity issue between an Amazon EC2 instance in a private subnet of VPC A () and a database instance in a private subnet of VPC B (). The two VPCs are connected via an AWS Transit Gateway. The administrator verifies the following configuration details:
1. Security Groups: The EC2 instance security group allows all outbound traffic, and the database security group allows inbound traffic on port from VPC A's CIDR ().
2. Network ACLs: The Network ACLs for both subnets allow all inbound and outbound traffic.
3. Subnet Route Tables:
- VPC A's private subnet route table has a route: tgw-0123456789abcdef0 (Transit Gateway).
- VPC B's private subnet route table has a route: tgw-0123456789abcdef0 (Transit Gateway).
4. Transit Gateway Route Tables:
- The Transit Gateway has two route tables: `TGW-RT-1` and `TGW-RT-2`.
- The VPC A attachment is associated with `TGW-RT-1` and propagates its routes to `TGW-RT-2`.
- The VPC B attachment is associated with `TGW-RT-2` and propagates its routes to `TGW-RT-2`.
Which of the following explains why the EC2 instance cannot connect to the database?
- The Transit Gateway route table `TGW-RT-1` lacks a route to VPC B because the VPC B attachment only propagates to `TGW-RT-2`.Answer
- BVPC A and VPC B are associated with different Transit Gateway route tables, which completely prevents them from routing traffic to each other.
- CThe Network ACL associated with VPC B's subnet blocks the connection because stateless Network ACLs require explicit outbound rules for ephemeral ports -.
- DThe subnet route table in VPC A must target the VPC B Transit Gateway attachment ID (`tgw-attach-xxxx`) rather than the Transit Gateway ID (`tgw-xxxx`).