Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your team manages a multi-tier production web application running across Compute Engine Managed Instance Groups (MIGs) and Google Kubernetes Engine (GKE) clusters. Active Assist generates several cost optimization recommendations, identifying overprovisioned GKE node pools (CLUSTER_OVERPROVISIONED) and underutilized VM machine types.
You need to apply these remediation actions safely and validate that the changes successfully reduce cloud spending without degrading application reliability or user experience.
Which end-to-end strategy should you execute?
This option applies aggressive instance downsizing across all workloads and relies solely on raw infrastructure saturation metrics (CPU and memory utilization reaching >90%) to validate that the resource waste has been eliminated.
CLUSTER_UNDERPROVISIONED, introducing severe reliability risks.The workload was a fault-tolerant, non-production batch processing pipeline where compute density and maximum resource saturation are prioritized over latency and real-time user responsiveness.
Implementing remediation from Active Assist recommendations requires modifying declarative infrastructure configurations—such as Managed Instance Group (MIG) instance templates and GKE node pool machine types—followed by continuous validation using both operational observability and financial reporting tools.
Cloud optimization is an iterative process of assessment, implementation, and re-measurement. Applying Active Assist recommendations via formal configuration templates while measuring user-centric SLIs alongside detailed billing analytics provides the complete feedback loop required to confirm both technical health and financial efficiency.
This approach attempts to cut costs immediately by manually deleting active virtual machines and GKE worker nodes without updating the managing controllers (MIGs or GKE cluster autoscalers), while using passive Cloud Billing budget alerts as the sole metric for validation.
kubectl delete node disrupts active Pod workloads without safely draining them or reconfiguring the node pool definition.You were conducting destructive chaos testing or taking down standalone, unmanaged compute instances that were explicitly marked as abandoned and scheduled for permanent decommissioning.
This approach configures Horizontal Pod Autoscaler (HPA) for Kubernetes workloads while leaving the underlying GKE node pool machine types and MIG instance templates untouched, treating the Active Assist recommendation status toggle as the validation mechanism.
The performance bottleneck was strictly caused by application Pod concurrency limits while the underlying GKE cluster node capacity and VM sizing were already optimal.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated