Before creating an internal HTTP(S) load balancer, which two tasks must you complete? (Choose two.)

Before creating an internal HTTP(S) load balancer, you must create firewall rules to allow health-check probes. These probes originate from Google's health check systems and need to reach your backend instances to determine their health. Without these rules, the load balancer cannot properly assess backend availability, leading to service issues. You also need to determine the subnet mask for a proxy-only subnet. Internal HTTP(S) load balancers require a dedicated proxy-only subnet in each region where they operate. This subnet hosts the Envoy proxies that handle traffic, and its IP range must be defined before the load balancer can be configured. Choosing a region is a prerequisite for many Google Cloud resources, but it's not a specific task before creating the load balancer itself, as the region is selected during the creation process. Reserving a static IP address is not required for an internal HTTP(S) load balancer, as it uses an internal, ephemeral IP address by default, or an internal static IP can be assigned later. Serverless VPC Access is unrelated to internal HTTP(S) load balancers.