Explanation:
To deploy an internal HTTP(S) load balancer, two critical prerequisites are required. First, firewall rules must allow health checks from Google's IP ranges (130.211.0.0/22 and 35.191.0.0/16), ensuring the load balancer can monitor backend instances. Second, a proxy-only subnet must be configured in the same region as the backend services, requiring determination of its subnet mask (must be /23 or larger). While choosing a region (A) is part of the setup, it is typically specified during resource creation rather than a strict prerequisite. Reserving a static IP (C) is optional, as ephemeral IPs can be used. Serverless VPC Access (E) is unrelated to this load balancer type.
Ultimate access to all questions.
Before deploying an internal HTTP(S) load balancer for your web server VM instances, which two prerequisite tasks must be completed? (Choose two.)
A
Choose a region.
B
Create firewall rules for health checks.
C
Reserve a static IP address for the load balancer.
D
Determine the subnet mask for a proxy-only subnet.
E
Determine the subnet mask for Serverless VPC Access.
No comments yet.