Gke Gateway Traffic Shedding Load Balancing

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

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?

Enable Adaptive Concurrency Tuning (ACT) on Compute Engine node pools and configure Cloud Scheduler to trigger shell scripts that scale down non-essential Pod replicas.

Deploy a multi-cluster Gateway using the gke-l7-global-external-managed-mc GatewayClass, define HTTPRoute rules with traffic splitting and Service Extensions to shed or deprioritize non-essential traffic, and configure service capacity thresholds on backend services to overflow excess load to secondary clusters.

Deploy an internal Application Load Balancer with single-cluster Ingress and configure Cloud Armor rate limiting rules to block requests matching non-critical URLs.

Deploy a regional external passthrough Network Load Balancer and configure Differentiated Services Code Point (DSCP) traffic classes via Cloud Interconnect application awareness to drop non-essential packets at the edge.

Professional Cloud DevOps Engineer

Gke Gateway Traffic Shedding Load Balancing

Related questions