A company uses AWS Local Zones to extend workloads from a VPC in a single Region. The Local Zone workloads must have two-way communication with the Regional VPC workloads. Which approach is the MOST cost-effective?

The most cost-effective approach is to create a new subnet in the Local Zone using a CIDR block from the existing VPC. Local Zones are extensions of an AWS Region, allowing you to place resources like EC2 instances and EBS volumes closer to end-users. Subnets within a Local Zone are directly associated with the parent VPC in the Region, enabling seamless and direct two-way communication between resources in the Local Zone subnet and the Regional VPC without additional networking constructs like Transit Gateways or VPNs. Creating a new VPC in the Local Zone and using a Transit Gateway would introduce unnecessary complexity and cost, as Local Zones are designed to extend existing VPCs. Deploying third-party appliances or VPN connections adds management overhead and expense that is not required for communication within a single VPC extending to a Local Zone.