You are in the process of deploying an internal HTTP(S) load balancer for your web server virtual machine (VM) instances. What two prerequisite tasks must be completed before creating the load…

Question

Options

• AChoose a region.
• BCreate firewall rules for health checks.
• CReserve a static IP address for the load balancer.
• DDetermine the subnet mask for a proxy-only subnet.
• EDetermine the subnet mask for Serverless VPC Access.

• A
  15% (8)
• B
  74% (40)
• C
  7% (4)
• E
  4% (2)

Explanation

Two prerequisites are required before creating an internal HTTP(S) load balancer in Google Cloud. First (Option B), you must create firewall rules that allow health check probes from Google's health check IP ranges (130.211.0.0/22 and 35.191.0.0/16) to reach your backend instances - without these rules, health checks fail and the load balancer cannot determine which backends are healthy. Second (Option D), an internal HTTP(S) load balancer requires a dedicated proxy-only subnet in the region; this subnet provides IP addresses for the managed Envoy proxies that front the load balancer. You must determine the subnet mask for this proxy-only subnet before creating the load balancer. Option A (choosing a region) is a configuration choice during creation, not a separate prerequisite task. Option C (static IP) is optional. Option E (Serverless VPC Access) applies to serverless products connecting to VPCs, not to internal HTTP(S) load balancers.

No community discussion yet for this question.