Google Professional Cloud Network Engineer Question 291
Select 3Google Cloud PlatformYou have created a VPC-native GKE cluster with alias IPs enabled. During the setup, you need to ensure that the cluster can efficiently allocate IPs for Pods without exhausting the subnet IP range. Which of the following steps should you take to configure the subnets and secondary IP ranges correctly?
- A
Create a primary IP range for the subnet and ensure it is large enough for the cluster and other resources.
- B
Create a secondary IP range specifically for the Pods and ensure it’s separate from the primary IP range.
- C
Assign the same secondary IP range to both Pods and Services for simplicity.
- D
Create a secondary IP range for Services that is distinct from the secondary IP range for Pods.
- E
Disable the alias IPs and enable legacy networks for simpler IP management.
Show answer and explanation
Correct answers: A, B, D
Explanation
When creating a VPC-native GKE cluster with alias IPs, it is crucial to configure the IP ranges correctly. The primary IP range is used for the subnet, while secondary IP ranges are specifically allocated for Pods and Services. These secondary ranges must be distinct to prevent IP conflicts and to allow the cluster to scale efficiently. Disabling alias IPs or using legacy networks is not aligned with best practices for VPC-native clusters.
- A. Correct.
Correct: A primary IP range for the subnet is required for the overall network, and it needs to be large enough to accommodate the cluster and other network resources.
- B. Correct.
Correct: A secondary IP range for Pods is essential in VPC-native clusters. This range must be separate from the primary IP range to avoid conflicts.
- C. Incorrect.
Incorrect: Assigning the same secondary IP range to both Pods and Services would lead to IP conflicts and is not supported in GKE.
- D. Correct.
Correct: Services require a distinct secondary IP range separate from the Pods' range to ensure smooth IP allocation and avoid conflicts.
- E. Incorrect.
Incorrect: Disabling alias IPs and using legacy networks is not recommended as it reduces scalability and goes against the purpose of VPC-native clusters.