A SaaS company runs its media solution across 50 VPCs in multiple Regions and accounts. One VPC is a management VPC. Compute resources in each VPC operate independently. A new feature requires full connectivity among all 50 VPCs and one-way access from each customer VPC to the management VPC for license validation. The management VPC hosts the license-validation compute resource. The solution will continue to scale to more VPCs. Which combination of actions will provide the required connectivity with the least operational overhead? (Choose two.)

An AWS Transit Gateway (TGW) is the most scalable and operationally efficient solution for full mesh connectivity among 50 VPCs. It simplifies network management by acting as a central hub, avoiding the N-squared complexity of VPC peering. Deploying a Network Load Balancer (NLB) with AWS PrivateLink for the license validation service provides secure, one-way access from customer VPCs to the management VPC without traversing the public internet or requiring complex routing. PrivateLink also scales well and offers high availability. VPC peering between every pair of VPCs (N-squared connections) is unmanageable for 50 VPCs and does not scale. Deploying VPN appliances in every customer VPC is high operational overhead and not a native AWS solution for inter-VPC connectivity. Creating individual VPC peering connections between the management VPC and each customer VPC would only provide one-way access to the management VPC, not full connectivity among all 50 VPCs, and would still involve managing 49 peering connections.