Diagram
A left-to-right process flow showing a client request entering the closest Google Front End via one anycast IP, passing Cloud Armor edge policies and Cloud CDN cache check, then backend policy check to healthy regional MIG backends.
Automated Traffic Management with Load Balancing and Health Checks
Cloud Load Balancing distributes traffic across backends so no single VM, zone, or region becomes a single point of failure. A forwarding rule defines one entry point using an external IP address, and the load balancer spreads requests from that entry point across configured backends. When a backend or location becomes unreachable, the load balancer automatically steers traffic to remaining healthy capacity.
Health checks provide the signal that controls this steering. Traffic flows from the client to the forwarding rule, then from the load balancer to backend VMs that pass health checks and away from VMs that fail them. Health checking covers both a stopped VM and a running VM whose application is frozen, crashed, or out of memory, so business-critical steering depends on the data plane continuing to avoid unhealthy backends. MIGs add self-repair behind this steering through autohealing, which deletes and recreates unhealthy VMs from an instance template, and autoscaling, which adds or removes VMs on demand signals.
Domain 2 of 5
164 practice questions
Practice this DomainLast updated