An enterprise is designing the network architecture for a public web application deployed on Compute Engine instances across multiple Google Cloud regions. The application serves HTTP/HTTPS traffic to a worldwide user base. The design requires routing incoming requests to the closest regional backend and caching static content at Google edge locations to reduce latency. Which TWO Google Cloud components should be planned for this implementation? (Select TWO)
- Global External Application Load Balancer for multi-region HTTP/HTTPS request distributionCevap
- Cloud CDN enabled on backend services to cache static content near end usersCevap
- CInternal Passthrough Network Load Balancer to route incoming internet traffic across regions
- DExternal Passthrough Network Load Balancer to handle HTTP protocol routing and edge caching
Cevap
The architectural plan must include the Global External Application Load Balancer and Cloud CDN.
To distribute global HTTP/HTTPS traffic efficiently, a Global External Application Load Balancer acts as a single global IP endpoint that forwards requests to the closest regional backend. Enabling Cloud CDN on its backend services leverages Google's global points of presence (PoPs) to cache static responses and lower overall latency.
Adım Adım Çözüm
Anahtar Kavram
Selecting load balancer types and caching mechanisms based on protocol, scope, and caching requirements.