Answer-first summary for fast verification
Answer: Create a subnet of size/25 with 2 secondary ranges of: /17 for Pods and /21 for Services. Create a VPC-native cluster and specify those ranges.
The question requires designing a VPC-native GKE cluster with alias IP ranges that can accommodate planned growth while minimizing IP consumption. Option A is correct because it provides a subnet and secondary ranges that are sufficiently large to accommodate the planned growth without over-provisioning. A /25 subnet for nodes, a /17 for Pods, and a /21 for Services meet the future requirements of 100 nodes, 20,000 Pods, and 1,500 Services respectively. Options B, C, and D either do not meet the future requirements or do not address the subnet sizing adequately.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
You are designing a Google Kubernetes Engine (GKE) cluster for your organization. The initial cluster will host 10 nodes, 20 Pods per node, and 150 services. Due to planned growth over the next two years, the cluster will scale to 100 nodes, 200 Pods per node, and 1,500 services. You need to implement a VPC-native cluster using alias IP ranges while optimizing IP address consumption.
How would you design this topology?
A
Create a subnet of size/25 with 2 secondary ranges of: /17 for Pods and /21 for Services. Create a VPC-native cluster and specify those ranges.
B
Create a subnet of size/28 with 2 secondary ranges of: /24 for Pods and /24 for Services. Create a VPC-native cluster and specify those ranges. When the services are ready to be deployed, resize the subnets.
C
Use gcloud container clusters create [CLUSTER NAME]--enable-ip-alias to create a VPC-native cluster.
D
Use gcloud container clusters create [CLUSTER NAME] to create a VPC-native cluster.