Google Professional Cloud Network Engineer Question 31
Select 2Google Cloud PlatformYou are deploying a Google Kubernetes Engine (GKE) cluster using the VPC-native mode. The workloads running in your cluster are expected to scale significantly over time. During the planning phase, you must ensure that there is enough IP address space for both Pods and Services while also allowing access to the GKE control plane. Which of the following configurations should you choose to meet these requirements?
- A
Reserve a large secondary IP range in your VPC for Pods and another large secondary IP range for Services.
- B
Ensure that the primary IP range of the VPC has enough space to allocate all Pods and Services.
- C
Enable private Google access to allow workloads to communicate with the GKE control plane without using public IPs.
- D
Use the default secondary IP ranges assigned by GKE and rely on auto-scaling to allocate additional IPs as needed.
- E
Plan for at least /24 subnet masks for both the Pod and Service secondary ranges to ensure scalability.
Show answer and explanation
Correct answers: A, C
Explanation
When planning for a GKE cluster in VPC-native mode, it is critical to allocate large enough secondary IP ranges for both Pods and Services to ensure scalability. Additionally, enabling private Google access ensures secure and efficient communication with Google services, including the GKE control plane. The primary IP range of the VPC is not used for Pods or Services in VPC-native clusters, and relying solely on defaults or small ranges can lead to IP exhaustion.
- A. Correct.
Correct: In VPC-native GKE clusters, Pods and Services use secondary IP ranges. Reserving sufficiently large secondary IP ranges ensures your cluster can scale without running out of IP addresses.
- B. Incorrect.
Incorrect: The primary IP range of the VPC is not used for Pods or Services in VPC-native clusters. Instead, secondary IP ranges are required for these purposes.
- C. Correct.
Correct: Enabling private Google access allows your workloads to communicate with Google services, including the GKE control plane, without requiring public IPs.
- D. Incorrect.
Incorrect: Relying on default secondary IP ranges may not provide sufficient IP address space for scaling workloads, which can lead to resource exhaustion.
- E. Incorrect.
Incorrect: While /24 subnet masks might provide adequate space for smaller deployments, they may not be sufficient for large-scale clusters or future scaling needs.