ANS-C01 · Question #228
Company A recently acquired Company B. Company A has a hybrid AWS and on-premises environment that uses a hosted AWS Direct Connect connection, a Direct Connect gateway, and a transit gateway…
The correct answer is B. Create an association proposal from the Company B account to associate the Company B transit. Explanation Option B is correct because AWS allows a transit gateway in one account to be associated with a Direct Connect gateway in a different account through a cross-account association proposal. By creating an association proposal from Company B's account to link its…
Question
Company A recently acquired Company B. Company A has a hybrid AWS and on-premises environment that uses a hosted AWS Direct Connect connection, a Direct Connect gateway, and a transit gateway. Company A has a transit VIF to access the resources in its production environment in the us-east-1 Region. Company B has applications that run across multiple VPCs in the us-west-2 Region in a single AWS account. A transit gateway connects all Company B's application VPCs. The CIDR blocks for both companies do not overlap. Company A needs to use the existing Direct Connect connection to access Company B's applications from the on-premises environment. Which solution will meet these requirements?
Options
- ACreate a new Direct Connect gateway in the Company B account. Associate the Company B
- BCreate an association proposal from the Company B account to associate the Company B transit
- CCreate multiple virtual private gateways. Attach the virtual private gateways to each of Company
- DCreate a new Direct Connect gateway in the Company B account. Associate the Company B
How the community answered
(39 responses)- A5% (2)
- B85% (33)
- C3% (1)
- D8% (3)
Explanation
Explanation
Option B is correct because AWS allows a transit gateway in one account to be associated with a Direct Connect gateway in a different account through a cross-account association proposal. By creating an association proposal from Company B's account to link its transit gateway to Company A's existing Direct Connect gateway, on-premises traffic can flow through Company A's existing Direct Connect connection and transit VIF to reach Company B's VPCs in us-west-2 - no new Direct Connect connection is needed.
Why the distractors are wrong:
- Options A and D both involve creating a new Direct Connect gateway in Company B's account, which is unnecessary and adds complexity; the existing Direct Connect gateway in Company A's account can be used cross-account via an association proposal.
- Option C uses virtual private gateways (VGWs), which are designed for site-to-site VPN or Direct Connect connections at the individual VPC level - this approach doesn't scale across multiple VPCs and cannot directly attach to a transit gateway for this use case.
Memory Tip: Think of a Direct Connect gateway as a shared resource - it can accept association proposals from transit gateways in other AWS accounts, making it ideal for post-acquisition scenarios. Remember: "Proposal = Cross-account bridge" - when you see cross-account + existing DX, think association proposal, not a new gateway.
Topics
Community Discussion
No community discussion yet for this question.