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.
An enterprise runs a high-throughput microservices application on Google Kubernetes Engine (GKE) serving both gRPC and HTTP/2 traffic. The DevOps engineering team is implementing a progressive deployment pipeline to release new microservice versions safely.
The deployment strategy must satisfy the following technical requirements:
Which architecture and traffic management strategy should the team implement?
Cloud Run is a fully managed serverless container runtime that supports multi-revision deployments and built-in traffic splitting. Cloud Tasks is a fully managed asynchronous task execution and queuing service.
The workload was natively hosted on Cloud Run as an asynchronous event-driven application where tasks are queued and processed independently by tagged revision endpoints.
An External Passthrough Network Load Balancer is a regional Layer 4 load balancer that distributes incoming TCP and UDP traffic to backend virtual machines or GKE nodes based on IP protocol, address, and port 5-tuples.
The workload required extreme Layer 4 packet processing throughput with direct server return (DSR) and had no requirement for Layer 7 protocol parsing or header-based traffic shifting.
Cloud Service Mesh (which consolidates Anthos Service Mesh and Traffic Director) provides fully managed, application-aware service networking for microservices architectures across Google Cloud. It utilizes Envoy proxy sidecars injected directly into Google Kubernetes Engine (GKE) workloads to manage Layer 7 ingress and east-west mesh communication.
VirtualService or Gateway API routes), traffic can be split precisely by weight (e.g., 95% baseline, 5% canary) regardless of the number of running Pod replicas in each deployment.Cloud Service Mesh provides native Layer 7 control plane capabilities, enabling dynamic percentage weighting, advanced header-based steering, and automated host ejection via outlier detection within a single cohesive framework.
Standard Kubernetes Service objects perform Layer 4 round-robin load balancing across all matching Pod endpoints governed by labelSelector definitions. Traffic distribution relies purely on the ratio of canary Pods to baseline Pods.
The environment were constrained to basic open-source Kubernetes primitives without a service mesh, traffic splitting could tolerate coarse granularity tied to Pod counts, and Layer 7 header inspection was not required.
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