Explanation:
Option C is the correct choice because Autopilot in GKE is specifically designed to minimize operational costs by automating node utilization monitoring and eliminating idle nodes, thus ensuring efficient resource allocation. Options A and B, while useful for certain scenarios, do not directly address cost control in GKE as effectively as Autopilot. Option D, though it mentions cost-saving measures, does not provide the dynamic resource adjustment capabilities of Autopilot. For more details, refer to Google Cloud's documentation on Autopilot.
Ultimate access to all questions.
No comments yet.
As the lead architect for your organization's migration of on-premises deployments to Google Kubernetes Engine (GKE), your goal is to control costs effectively. Which strategy should you adopt?
A
Utilize Horizontal Pod Autoscaler to adjust the number of Pod replicas based on metrics like CPU utilization.
B
Establish a managed instance group with Compute Engine instances, configuring it to scale based on load.
C
Enable Autopilot in GKE for automated monitoring of node utilization and the removal of idle nodes.
D
Deploy a cluster with predetermined capacity, leveraging sustained use discounts for budget management.