Google Professional Cloud Network Engineer Question 292
Select 2Google Cloud PlatformYou are tasked with deploying a Google Kubernetes Engine (GKE) cluster in a Virtual Private Cloud (VPC). The cluster must use VPC-native networking with alias IPs to integrate seamlessly with other workloads in the VPC. Which of the following steps are required to configure a VPC-native cluster using alias IPs?
- A
Enable the 'Private Google Access' setting on the VPC.
- B
Ensure the VPC has a subnet with secondary IP ranges defined.
- C
Specify the
--enable-ip-aliasflag when creating the cluster. - D
Create a dedicated VPC specifically for the GKE cluster.
- E
Ensure the VPC's subnet uses a custom route mode instead of auto mode.
Show answer and explanation
Correct answers: B, C
Explanation
To create a VPC-native GKE cluster using alias IPs, the VPC subnet must have secondary IP ranges defined to allocate Pod and Service IPs. Additionally, the --enable-ip-alias flag must be specified during cluster creation to enable this functionality. Other settings, such as Private Google Access or custom route mode, are not requirements for using alias IPs.
- A. Incorrect.
Enabling 'Private Google Access' is not required to create a VPC-native cluster with alias IPs. It is optional and relevant for accessing Google APIs and services privately.
- B. Correct.
A VPC subnet must have secondary IP ranges defined because alias IPs are allocated from these secondary ranges, which are used for Pods and Services in the GKE cluster.
- C. Correct.
The
--enable-ip-aliasflag must explicitly be used when creating the cluster to enable VPC-native networking and alias IPs. - D. Incorrect.
It is not required to create a dedicated VPC for the GKE cluster. The cluster can reside in an existing VPC as long as it meets the requirements.
- E. Incorrect.
The VPC's subnet does not need to use a custom route mode. Both auto mode and custom mode VPCs can support VPC-native clusters as long as the subnet has secondary IP ranges defined.