Architects debate placing a city API in a public subnet versus a private subnet in a VPC. Under shared responsibility, whose decision is that architecture choice?
Select an answer to reveal the explanation.
Short Explanation
AWS gives you the neighborhood layout tools; you still choose the house on the busy street versus the quiet cul-de-sac. Public versus private subnet placement is a customer architecture and control decision. That choice drives how exposed the workload is.
Full Explanation
Customers are responsible for how they configure networking and exposure in their VPCs, including whether resources are placed in public or private subnets. AWS provides VPC networking capabilities but does not unilaterally place every customer workload. Inspector assesses vulnerabilities; it does not replace customer subnet architecture decisions, and EC2 instances are not always internet-facing.