Google Professional Cloud Network Engineer Question 290
Single answerGoogle Cloud PlatformYou are tasked with creating a GKE cluster for your organization's new microservices application. The application requires extensive inter-service communication, and you want to minimize IP address management overhead, ensure scalability, and integrate seamlessly with Google Cloud VPC. How can you configure the cluster to meet these requirements?
- A
Create a GKE cluster with VPC-native (alias IP) enabled and specify a custom subnet for the cluster's Pods.
- B
Create a GKE cluster without VPC-native (alias IP) enabled and rely on manually assigned IP ranges for Pods.
- C
Create a GKE cluster with VPC-native (alias IP) enabled and let Google Cloud automatically allocate Pod IP ranges.
- D
Create a GKE cluster without VPC-native (alias IP) enabled and configure a secondary range for the Pod IPs.
Show answer and explanation
Correct answer: A
Explanation
Enabling VPC-native (alias IP) for GKE clusters is essential for managing Pod IP addresses efficiently, especially in scenarios requiring scalability and integration with Google Cloud VPC. This approach allows Pods to use a secondary IP range from the VPC subnet, avoiding IP conflicts and ensuring seamless communication. Specifying a custom subnet for Pods provides additional control over the IP range, which is beneficial for organizational needs.
- A. Correct.
Correct. Enabling VPC-native (alias IP) ensures Pods receive IP addresses from a secondary CIDR range in the VPC subnet, simplifying IP address management and enabling scalability. Specifying a custom subnet for Pods allows you to control the IP range allocation.
- B. Incorrect.
Incorrect. Disabling VPC-native (alias IP) requires manual IP address management for Pods, leading to increased complexity and potential IP conflicts.
- C. Incorrect.
Incorrect. While enabling VPC-native (alias IP) is correct, relying on Google Cloud to automatically allocate Pod IP ranges limits control over the IP configuration, which may not meet specific organizational requirements.
- D. Incorrect.
Incorrect. Disabling VPC-native (alias IP) while configuring a secondary range for the Pod IPs is not possible. Alias IPs are required to utilize a secondary range in the VPC.