
Ultimate access to all questions.
A company has a transit gateway in AWS Account A, shared with other accounts using AWS Resource Access Manager (AWS RAM) to enable connectivity to multiple VPCs within the same AWS Region. AWS Account B has a VPC (10.0.0.0/16) with subnets 10.0.0.0/24 in us-west-2a and 10.0.1.0/24 in us-west-2b, both of which can communicate with other VPCs.
A network engineer adds two new subnets: 10.0.2.0/24 in us-west-2b and 10.0.3.0/24 in us-west-2c, all sharing a single route table with the default route 0.0.0.0/0 pointing to the transit gateway. While resources in subnet 10.0.2.0/24 can communicate with other VPCs, resources in subnet 10.0.3.0/24 cannot.
What steps should the network engineer take to enable communication between resources in subnet 10.0.3.0/24 and other VPCs?
A
In Account B, add 10.0.2.0/24 and 10.0.3.0/24 as the destinations to the route table. Use the transit gateway as the target.
B
In Account B, update the transit gateway attachment. Attach the new subnet ID that is associated with us-west-2c to Account B's VPC.
C
In Account A, create a static route for 10.0.3.0/24 in the transit gateway route tables.
D
In Account A, recreate propagation for 10.0.0.0/16 in the transit gateway route tables.