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 enterprise runs a critical web application on regional Compute Engine Managed Instance Groups (MIGs) across staging and production environments. You are tasked with implementing an automated patching and lifecycle promotion pipeline that strictly adheres to immutable infrastructure principles and minimizes the blast radius of potential regressions.
The deployment strategy must satisfy the following requirements:
Which strategy should you implement?
This approach relies on a startup script executed during VM initialization to download and apply the latest software packages from upstream repositories whenever a new instance boots.
The goal was to test dynamic bootstrap scripts in non-production environments where startup latency and non-deterministic builds were acceptable.
This approach provisions a separate standalone MIG for canary traffic behind a load balancer and uses Config Sync to manage infrastructure manifests across environments.
--canary-version) allows managing the canary within the existing production MIG without duplicating instance group infrastructure.The workload was running entirely on GKE clusters managed by Config Sync using GitOps commit sha promotion.
This solution implements an immutable infrastructure pattern combined with canary deployments in Compute Engine Managed Instance Groups (MIGs) and automated remediation triggered by Cloud Monitoring alerts.
rolling-action start-update command with --version=template=CURRENT_INSTANCE_TEMPLATE and --canary-version=template=NEW_TEMPLATE,target-size=10%, the production MIG shifts only 10% of its capacity to the new template while keeping 90% on the baseline version.This approach aligns with Google Cloud site reliability engineering and DevOps best practices by separating artifact creation from environment promotion, employing progressive rollouts, and using metric thresholds for automated rollback decisions.
This approach uses VM Manager Patch Management (OS Config agent) to apply software and security updates in-place to existing, long-running virtual machine instances across staging and production.
The workload relied strictly on mutable, stateful virtual machines where recreating instances from templates was prohibited and VM Manager was mandated for scheduled OS updates.
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