GCP Associate Cloud Engineer Practice Question

Your company is getting ready to deploy a multi-region application on Google Cloud.

The public-facing front-end will use a global external HTTP(S) Load Balancer and must keep the same IPv4 address across redeployments.
A back-end service that runs only in us-central1 will later be exposed by an internal TCP/UDP Load Balancer and needs a fixed virtual IP (VIP) inside the 10.20.0.0/24 subnet of the subnet named prod-subnet.

You want to reserve both IP addresses ahead of time with the gcloud CLI so no other team can allocate them. Which set of commands follows Google Cloud conventions for address scope and required flags?

gcloud compute addresses create web-v4 --global --subnet=default --addresses=35.199.0.5
gcloud compute addresses create ilb-vip --region=us-central1
gcloud compute addresses create web-v4 --global
gcloud compute addresses create ilb-vip --region=us-central1 --addresses=10.20.0.15 --purpose=VPC_PEERING
gcloud compute addresses create web-v4 --region=us-central1
gcloud compute addresses create ilb-vip --global --subnet=prod-subnet --addresses=10.20.0.15 --purpose=INTERNAL_LOAD_BALANCER
gcloud compute addresses create web-v4 --global --ip-version=IPV4
gcloud compute addresses create ilb-vip --region=us-central1 --subnet=prod-subnet --addresses=10.20.0.15

Report Issue

Answer Description

To reserve a static IPv4 address for a global external HTTP(S) Load Balancer, use gcloud compute addresses create with the --global flag; no --region flag is needed because the address is global in scope.

An internal TCP/UDP Load Balancer uses a regional, subnet-specific address. Reserve it with gcloud compute addresses create specifying --region, --subnet, and the desired address. The --purpose flag is optional for internal load-balancer VIPs; omitting it still allows the address to be used for the load balancer.

Therefore, the only command set that correctly applies --global to the external address, omits --region for that address, and reserves the internal VIP regionally without using --global or unnecessary purpose flags is the correct choice. Other options either use --region for the global address, try to make the internal VIP global, or set an incorrect purpose, so they will fail or reserve addresses that cannot be used as intended.

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.