Google Professional Cloud Network Engineer Question 189
Single answerGoogle Cloud PlatformYou are designing a new Google Kubernetes Engine (GKE) environment for your organization. The development team wants to focus on writing and deploying applications without managing cluster infrastructure. However, they also require fine-tuned control over workloads and custom configurations for networking and security policies. Which GKE mode should you choose for this use case?
- A
GKE Autopilot mode, because it eliminates the need to manage nodes and provides full control over workload configurations.
- B
GKE Standard mode, because it allows for granular control over cluster configurations and workload management.
- C
GKE Autopilot mode, because it offers predefined configurations for advanced networking and security needs.
- D
GKE Standard mode, because it automatically manages nodes and abstracts cluster infrastructure management.
Show answer and explanation
Correct answer: B
Explanation
GKE Standard mode is the appropriate choice in this scenario because it balances the need for custom configurations and granular control over workloads, networking, and security policies. While GKE Autopilot mode abstracts much of the infrastructure management, it does not provide the same level of customization, which the development team requires.
- A. Incorrect.
GKE Autopilot mode eliminates the need to manage nodes but does not provide the same level of control over workload and cluster configurations as Standard mode. This is incorrect for the stated requirements.
- B. Correct.
GKE Standard mode allows for granular control over cluster configurations, workload management, and custom networking/security requirements. This aligns with the needs of the development team, making it the correct choice.
- C. Incorrect.
GKE Autopilot mode does not support advanced networking and security configurations as flexibly as Standard mode. It is more suited for simplified operations with predefined configurations.
- D. Incorrect.
GKE Standard mode does not automatically manage nodes; instead, it provides manual control over cluster infrastructure. This description is incorrect.