Design a VPC‑native GKE cluster with alias IP ranges to minimize address consumption for current and planned growth (current: 10 nodes, 20 Pods/node, 150 services; planned: 100 nodes, 200 Pods/node, 1500 services). Which topology should you use?

The correct option provides sufficient IP addresses for both current and planned growth while minimizing consumption. For Pods: Current: 10 nodes 20 Pods/node = 200 Pods. Planned: 100 nodes 200 Pods/node = 20,000 Pods. A /17 range provides 32,768 addresses, which is ample for 20,000 Pods (plus overhead). For Services: Current: 150 services. Planned: 1,500 services. A /21 range provides 2,048 addresses, which is sufficient for 1,500 services. The primary subnet /25 (128 addresses) is for node IPs. The incorrect options either provide insufficient IP addresses, especially for planned growth, or do not specify the necessary secondary ranges for Pods and Services, which is crucial for VPC-native GKE clusters. Resizing subnets later can be disruptive and is not the optimal design for planned growth.