GCP Associate Cloud Engineer Practice Question

You plan to expose an Internal HTTP(S) Load Balancer for a private GKE cluster that lives in the subnet "web-subnet" (10.0.0.0/20) of VPC "prod-vpc" in region us-central1. The application team requires that the virtual IP 10.0.100.10 remain fixed even if the load balancer is recreated. Which gcloud action should you perform before creating the load balancer to meet this requirement while following Google-recommended practice?

Skip reserving an address and set the annotation loadBalancerIP: "10.0.100.10" on the Kubernetes Service; the IP will be held automatically.
Add 10.0.100.10 as a reserved address in a Cloud NAT gateway attached to prod-vpc.
Run: gcloud compute addresses create lb-ip --global --addresses 10.0.100.10
Run: gcloud compute addresses create lb-ip --region us-central1 --subnet web-subnet --addresses 10.0.100.10 --purpose SHARED_LOADBALANCER_VIP

Report Issue

Answer Description

A regional static internal address must be reserved ahead of time so the forwarding rule for the Internal HTTP(S) Load Balancer can reference it. The reservation must be scoped to the same region as the subnet, specify that subnet, supply the desired address, and set purpose to SHARED_LOADBALANCER_VIP. Reserving a global static IP in Google Cloud allocates a global anycast external IP, not an internal one, so it would not satisfy the requirement. Kubernetes annotations alone do not guarantee that the IP remains allocated to your project; if the address is not pre-reserved, it is released when the Service is deleted. Cloud NAT uses external addresses to provide egress for private VMs and has no effect on an internal frontend address.

Ask Bash

Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.