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 e-commerce platform hosted on Google Kubernetes Engine (GKE) experiences an unprecedented traffic spike during a flash sale. The primary regional cluster reaches its maximum physical node quota and compute limits, causing critical user checkout requests to degrade alongside non-critical recommendation and browsing requests.
You need to implement a traffic shedding and load balancing strategy using Google Cloud native networking to shed non-essential traffic, prioritize critical transaction journeys, and automatically overflow excess global traffic to healthy secondary clusters once service capacity limits are exceeded. What should you do?
This option attempts to apply Adaptive Concurrency Tuning (ACT)—a proprietary autoscaling feature of Cloud Run—to GKE worker nodes, alongside Cloud Scheduler cron jobs to manually scale down Kubernetes workloads.
You were hosting microservices on Cloud Run and needed the serverless platform to automatically tune container request concurrency to prevent CPU starvation under high load.
The multi-cluster Gateway API (gke-l7-global-external-managed-mc) combined with HTTPRoute and GKE Gateway Service Extensions provides an advanced Layer 7 global traffic management and load balancing framework across multiple GKE clusters and Google Cloud regions.
gke-asia to gke-eu).Gateway, HTTPRoute, GCPBackendPolicy).This approach natively solves multi-cluster capacity overflow and granular Layer 7 load shedding directly at the Cloud Load Balancing layer without introducing custom proxies or unmanaged routing infrastructure.
This option configures a regional external passthrough Network Load Balancer (Layer 4) combined with Cloud Interconnect application awareness, which uses Differentiated Services Code Point (DSCP) marking in IP packet headers to apply traffic shaping and strict priority policies across hybrid on-premises Dedicated Interconnect connections.
You needed to prioritize critical outbound hybrid network traffic traveling across a constrained on-premises Dedicated Interconnect connection rather than managing public HTTP ingress load across GKE clusters.
This option sets up an Internal Application Load Balancer with standard single-cluster GKE Ingress and attempts to attach Cloud Armor security policies to restrict traffic rates on specific URL paths.
The application were strictly an internal enterprise tool accessed exclusively by corporate intranet users over private VPC routes without the need for multi-cluster global failover.
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