CLOUD-NETWORK practice question 3 of 30

You want to create a service in GCP using IPv6. What should you do?

Full set: 233 questions
Answer options
A: Create the instance with the designated IPv6 address.
B: Configure a TCP Proxy with the designated IPv6 address.
C: Configure a global load balancer with the designated IPv6 address. Correct answer
D: Configure an internal load balancer with the designated IPv6 address.
Correct Answer:
C. Configure a global load balancer with the designated IPv6 address.
Explanation

To create a scalable, highly available service with a public IPv6 address in Google Cloud, the standard method is to use a global external load balancer. The External HTTP(S) Load Balancer, SSL Proxy Load Balancer, and TCP Proxy Load Balancer all support IPv6 termination. You can configure a forwarding rule with an IPv6 address, which directs traffic from IPv6 clients to your backend instances or services. This approach provides a single, stable IPv6 endpoint for your service.

Why Incorrect

A. While instances can have IPv6 addresses, this doesn't inherently create a scalable "service," which typically implies load balancing and high availability.
B. This is too specific. A TCP Proxy is one type of global load balancer, but "global load balancer" is a broader, more encompassing correct answer.
D. Internal load balancers operate within a VPC network using internal IPv4 addresses and do not support external IPv6 addresses.

References

1. Google Cloud Documentation

"IPv6 termination for External HTTP(S) Load Balancers". "When you configure an external HTTP(S) load balancer

you can assign an IPv6 address to the load balancer's forwarding rule."

2. Google Cloud Documentation

"IPv6 support"

Load Balancing. This table shows that External HTTP(S)

SSL Proxy

and TCP Proxy Load Balancers all support IPv6. These are all types of global load balancers.

3. Google Cloud Documentation

"Configuring IPv6 for instances and instance templates". This document confirms that instances can have IPv6 addresses but focuses on individual VM connectivity

not the creation of a load-balanced service.

Scroll to Top