Courseiva

Google PCA Ensure solution and operations reliability Practice Question

You are deploying a new version of a microservice to Google Kubernetes Engine (GKE). The service must remain available during the rollout, and you need to minimize the risk of exposing bugs to all users at once. You want to gradually shift traffic to the new version while monitoring key metrics. Which strategy should you use?

⚠ Common exam trap

Test-takers frequently confuse a rolling update with a canary deployment; rolling updates replace pods but do not control traffic percentages or support metric-based analysis.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Implement a canary deployment using Istio or Anthos Service Mesh to route a small percentage of traffic to the new version.

A canary deployment using a service mesh allows you to route a small portion of traffic to the new version, monitor its behavior, and then gradually increase traffic or roll back if problems occur. This minimizes risk and maintains availability. Other strategies either switch all traffic at once or lack the granular control needed for gradual, metric-based rollouts.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Implement a canary deployment using Istio or Anthos Service Mesh to route a small percentage of traffic to the new version.

    Why this is correct

    A canary deployment with a service mesh like Istio allows you to route a small percentage of traffic to the new version, monitor metrics, and gradually increase traffic or roll back if issues arise. This minimizes risk and keeps the service available. It provides the fine-grained control needed for safe rollouts.

  • ✗

    Perform a rolling update by changing the Deployment's pod template.

    Why it's wrong here

    A rolling update replaces pods gradually, but it does not provide fine-grained traffic control or the ability to pause and roll back based on metrics. It also does not allow you to direct a specific percentage of traffic to the new version while monitoring. It is less controlled than a canary deployment.

  • ✗

    Use a blue/green deployment by creating a new Deployment and switching the Service selector.

    Why it's wrong here

    Blue/green deployment switches all traffic at once after the new version is ready. This exposes all users to the new version simultaneously, which does not minimize the risk of bugs affecting everyone. It also does not support gradual traffic shifting or metric-based progression.

  • ✗

    Create a new GKE cluster and deploy the new version there, then update DNS to point to the new cluster.

    Why it's wrong here

    Deploying to a new cluster and switching DNS is disruptive and does not provide gradual traffic shifting. DNS changes can take time to propagate, and all users are switched at once. This approach increases risk and does not support monitoring-based progression or easy rollback.

About these practice questions

Courseiva writes every PCA question from scratch — 807 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Google Cloud exam blueprint

This PCA practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCA exam.