Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
An administrator is planning the IP address architecture for two distinct workloads deployed in Google Cloud:
us-central1-a that requires a persistent public IPv4 address for direct inbound connections.Which combination of static external IP address scopes must the administrator reserve for these resources?
In Google Cloud, static external IP addresses are allocated at either a regional or global scope depending on the resource type and architecture they serve. Regional static external IP addresses are tied to a specific geographic region (such as us-central1) and can be attached to zonal resources (like Compute Engine VM network interfaces) or regional load balancers located within that exact region. Global static external IP addresses are internet-accessible anycast IP addresses that route traffic across Google's worldwide private fiber network directly to global load balancing frontends.
us-central1). A VM network interface can only be assigned a regional static external IP address that belongs to the same region as the VM. Assigning a us-central1 regional IP satisfies this constraint.This is the only valid configuration supported by Google Cloud networking rules. Compute Engine instances cannot accept global external IP addresses directly on their network interfaces, and multi-region global external load balancers require global IP addresses for their anycast forwarding rules.
Global static external IP addresses are distributed, anycast IPv4 or IPv6 addresses managed at the project level. They are designed exclusively to serve as the entry point for global load balancers, terminating user traffic at Google's global Points of Presence (PoPs).
us-central1).gcloud compute instances create/add-access-config), or API will fail with a configuration error.nic0) on Compute Engine VMs.This configuration would only be correct if both workloads were implemented behind global load balancing architectures (for example, two distinct multi-region load-balanced services) rather than one being a direct-access standalone VM instance.
To expose a VM instance behind a global IP address, the VM must be placed into a backend service managed by a global load balancer rather than having the public IP directly bound to its virtual NIC.
This configuration represents an inverted assignment of IP address scopes, attempting to bind a global IP address directly to a zonal compute instance while allocating a regional IP to a global load balancing service.
This option would not be valid in any standard scenario, as Compute Engine VM network interfaces never support direct assignment of global external IP addresses under any circumstance.
A common point of confusion for beginners is assuming that "global" IPs can be applied to any individual cloud asset; however, Google Cloud strictly enforces regional boundaries on VM instances and restricts global external IPs to global load balancers.
Regional static external IP addresses are routable public IP addresses allocated from a specific Google Cloud region's pool. They are used for regional resources, including Compute Engine VM network interfaces, regional external Application Load Balancers, regional external proxy Network Load Balancers, external passthrough Network Load Balancers, Cloud NAT, and Cloud VPN.
us-central1 is valid for the VM instance (Workload 1), it fails the requirement for a global, multi-region External Application Load Balancer (Workload 2).us-central1, preventing it from acting as a single global anycast entry point distributing traffic across multiple backends worldwide.This option would be correct if Workload 2 were explicitly designed as a regional External Application Load Balancer targeting backends exclusively in us-central1 rather than a global, multi-region web application.
Google Cloud provides two distinct architectures for Application Load Balancers: Global External Application Load Balancers (which require global IP addresses) and Regional External Application Load Balancers (which use regional IP addresses).
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated