:

When established, Direct Peering provides a direct path from your on-premises network to Google

services, including Google Cloud products that can be exposed through one or more public IP

addresses. Traffic from Google's network to your on-premises network also takes that direct path,

including traffic from VPC networks in your projects. Google Cloud customers must request that

direct egress pricing be enabled for each of their projects after they have established Direct Peering

with Google. For more information, see Pricing.

Reference: https://cloud.google.com/interconnect/docs/how-to/direct-peering

:

:

:

A: Using VPC Flow Logs VPC Flow Logs records a sample of network flows sent from and received by

VM instances, including instances used as GKE nodes. These logs can be used for network

monitoring, forensics, real-time security analysis, and expense optimization.

https://cloud.google.com/vpc/docs/using-flow-logs (B): Firewall Rules Logging overview Firewall

Rules Logging allows you to audit, verify, and analyze the effects of your firewall rules. For example,

you can determine if a firewall rule designed to deny traffic is functioning as intended. Firewall Rules

Logging is also useful if you need to determine how many connections are affected by a given

firewall rule. You enable Firewall Rules Logging individually for each firewall rule whose connections

you need to log. Firewall Rules Logging is an option for any firewall rule, regardless of the action

(allow or deny) or direction (ingress or egress) of the rule.

https://cloud.google.com/vpc/docs/firewall-rules-logging

For private connectivity with at least 1 Gbps bandwidth and without using the public internet,

Partner Interconnect is the suitable choice if you do not require the 10 Gbps minimum of Dedicated

Interconnect. With Partner Interconnect, you create a VLAN attachment and work with a service

provider that facilitates the connection between your on-premises network and Google Cloud. This

solution supports connections as low as 50 Mbps and up to 10 Gbps.

Reference: Google Cloud - Choosing the right Interconnect product

The correct answer is B and C. You must create firewall rules for health checks and reserve a static IP

address for the load balancer before creating the internal HTTP(S) load balancer.

The other options are not correct because:

Option A is not a prerequisite task. You can choose a region when you create the load balancer, but

you do not need to do it beforehand.

Option D is not a prerequisite task. You can determine the subnet mask for a proxy-only subnet when

you create the subnet, but you do not need to do it beforehand.

Option E is not related to the internal HTTP(S) load balancer. Serverless VPC Access is a feature that

allows you to connect your serverless applications to your VPC network, but it is not required for the

load balancer.

:

: