Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
AWS Certified Solutions Architect - Professional · AWS
Select 2 answers.
This question asks for 2 answers, but our data marks only 1. Compare with the community discussion below for the full answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
B = Sharing subnets does not solve connectivity issues and complicates networks. Secure connectivity between on-premises and AWS. Support for multiple teams (accounts or VPCs). Minimal cost (traffic < 50 Mbps). Operation within the same Region (no multi-Region complexity). Operational simplicity (fewer components = fewer failures). No over-engineering (avoid unnecessary TGW/DX).
Put a single, centrally managed VPC in a shared services account and share subnets via AWS RAM so teams can deploy into those subnets without owning their own VPCs. Connect that VPC to on‑prem with a Site‑to‑Site VPN (cheap and fits <50 Mbps). Avoid Direct Connect (E) because it’s expensive for this bandwidth, and avoid Transit Gateway (C) and per‑account VPCs (A) because they add unnecessary cost and complexity for this scenario.
A implies that each group gets their own VPC. A further implies that each account gets their own VPN "something", i.e. presumably more than one VPN connection to on-prem would exist. I.e. more expensive than a single VPN from a shared services account.