Google Cloud Professional Cloud Network Engineer — Question 243
You are designing a Google Kubernetes Engine cluster for your organization. The current cluster size is expected to host 10 nodes, with 20 Pods per node and 150 Services. Because of the migration of new Services over the next two years, there is a planned growth for 100 nodes, 200 Pods per node, and 1500 Services. You want to use VPC-native clusters with alias IP address ranges, while minimizing address consumption. How should you design this topology?
Answer options
- A. 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.
- B. Use gcloud container clusters create [CLUSTER_NAME]--enable-ip-alias to create a VPC-native Cluster.
- C. 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.
- D. Use gcloud container clusters create [CLUSTER_NAME] to create a VPC-native Cluster.
Correct answer: C
Explanation
Option C is correct because it provides an appropriately sized subnet and secondary ranges that can accommodate the growth of Pods and Services over the next two years. Option A is incorrect as a /28 subnet is too small for the required number of Pods and Services. Option B, while partially correct, does not specify the necessary subnet and secondary ranges to meet the growth needs. Option D fails to provide specific configuration details needed for address range minimization.