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 is preparing a deployment strategy for a mission-critical checkout microservice hosted on Cloud Run. To adhere to Site Reliability Engineering (SRE) principles and minimize customer impact, your deployment plan must satisfy the following criteria:
Which deployment and release strategy should you implement?
This approach attempts to update an existing service without creating distinct versioned revisions, relying on manual or scripted rebuilds of prior source code in Cloud Build whenever errors are detected in Cloud Logging.
You were operating in a personal sandbox or development environment where downtime is inconsequential and continuous delivery pipelines are unnecessary.
Google Cloud Deploy provides managed, opinionated continuous delivery pipelines that natively integrate with Cloud Run and Google Kubernetes Engine (GKE). It supports progressive deployment patterns such as canary rollouts, allowing organizations to define automated, multi-phase traffic-shifting progressions across target environments while incorporating automated verification tests.
Canary deployments governed by SLO error budget consumption represent the gold standard of SRE release engineering. Leveraging Google Cloud Deploy removes the operational risk of custom, brittle shell scripts while ensuring automated rollbacks execute seamlessly if an updated revision consumes disproportionate error budget.
An instantaneous blue-green switch provisions a completely separate infrastructure environment (Green) alongside the active production environment (Blue), verifies health using synthetic load testing or smoke tests, and points DNS or load balancer routing to the new environment at 100% capacity.
The workload was a legacy stateful service that does not support multi-version concurrency or partial traffic splitting, requiring absolute schema separation and offline synthetic certification before cutover.
Config Sync and Fleet Packages automate the distribution and synchronization of Kubernetes manifests across multi-cluster GKE Fleets. A fleet package rollout strategy with maxConcurrent: 1 applies resource bundles sequentially to one cluster at a time across the organization's fleet.
You were deploying shared cluster infrastructure add-ons (such as ingress controllers or daemonsets) across dozens of distributed GKE clusters in multiple regions.
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