Google Professional Cloud Network Engineer Question 293
Select 3Google Cloud PlatformYou are setting up a GKE cluster for a new application that requires multiple services to communicate within a private network. The application also needs to scale quickly, and you want to avoid IP conflicts between cluster pods and other networks. Which of the following steps are required to create a VPC-native GKE cluster using alias IPs?
- A
Enable the 'Private Google Access' setting on the subnet used by the cluster.
- B
Create a subnet in the VPC and assign a secondary IP range for pod IPs.
- C
Specify the secondary IP range for pods when creating the GKE cluster.
- D
Enable the 'Enable VPC-native (using alias IP)' option when creating the GKE cluster.
- E
Manually configure routes for pod IPs in the VPC after cluster creation.
- F
Use a custom network policy to manage pod-to-pod communication within the cluster.
Show answer and explanation
Correct answers: B, C, D
Explanation
To create a VPC-native GKE cluster using alias IPs, you need to ensure the VPC subnet has a secondary IP range for pod IPs. During cluster creation, the secondary range must be specified, and the 'Enable VPC-native (using alias IP)' option needs to be selected. This configuration allows Google Cloud to automatically manage pod IP allocation and routing, avoiding IP conflicts and enabling efficient scaling.
- A. Incorrect.
Private Google Access is not required to create a VPC-native cluster using alias IPs, though it may be useful for other purposes like accessing Google APIs privately.
- B. Correct.
A secondary IP range is mandatory for the VPC subnet to allocate unique IPs to pods in a VPC-native GKE cluster.
- C. Correct.
When creating a VPC-native cluster, you must specify the secondary IP range that will be used for pod IPs, ensuring no IP conflicts with other networks.
- D. Correct.
Enabling the 'Enable VPC-native (using alias IP)' option is required to configure the cluster to use the alias IPs feature for pod IP allocation.
- E. Incorrect.
Routes for pod IPs are automatically managed by Google Cloud in a VPC-native cluster, so manual configuration is not necessary.
- F. Incorrect.
A custom network policy is not required for creating a VPC-native cluster, though it can be used later to control pod-to-pod communication.