Google Professional Cloud Network Engineer Question 35
Select 3Google Cloud PlatformYou are designing a Google Kubernetes Engine (GKE) cluster for your organization. The workloads running on the GKE cluster require a high number of individual Pods, and your team wants to ensure sufficient IP address space for scaling. Additionally, the cluster must allow secure, private communication with the GKE control plane. What configurations should you choose to meet these requirements?
- A
Use VPC-native (alias IP) networking and allocate secondary IP ranges for Pods and Services.
- B
Configure private clusters to enable private communication with the GKE control plane.
- C
Disable IP masquerading to reduce IP address consumption for Pods.
- D
Use a single secondary range for both Pods and Services to simplify configuration.
- E
Manually assign a CIDR block for the Pod IP range that is large enough to accommodate future scaling.
Show answer and explanation
Correct answers: A, B, E
Explanation
To design a scalable and secure GKE cluster, VPC-native (alias IP) networking must be enabled to allocate secondary IP ranges for Pods and Services. This allows better IP address management and avoids conflicts. For secure communication with the GKE control plane, private clusters should be used. Additionally, manually assigning a large CIDR block for the Pod IP range ensures the cluster has enough IP addresses for scaling. Using a single secondary range for Pods and Services is not recommended, and disabling IP masquerading does not address the requirements in this scenario.
- A. Correct.
Correct. VPC-native (alias IP) networking is required to use secondary IP ranges for Pods and Services, which allows for better IP address management and scalability.
- B. Correct.
Correct. Private clusters enable secure private communication with the GKE control plane, meeting the requirement for secure connectivity.
- C. Incorrect.
Incorrect. Disabling IP masquerading does not directly impact IP address consumption for Pods, and it may introduce additional networking constraints depending on your environment.
- D. Incorrect.
Incorrect. Using a single secondary range for both Pods and Services is not recommended because it can lead to IP address exhaustion and conflicts. Separate secondary ranges should be allocated for Pods and Services.
- E. Correct.
Correct. Manually assigning a sufficiently large CIDR block for the Pod IP range ensures the cluster can scale without running out of IP addresses.