Courseiva

Google PCA Design and plan a cloud solution architecture Practice Question

A global e-commerce company is designing a multi-region architecture on Google Cloud to ensure high availability and low latency for users worldwide. They want to use a global load balancer that can route traffic to the closest healthy backend and support HTTP(S) and TCP traffic. Which Google Cloud load balancing option should they use?

⚠ Common exam trap

The trap here is assuming a single load balancer can handle both HTTP(S) and TCP traffic globally, but Google Cloud separates these into different load balancer types.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Global external HTTP(S) load balancer and global external TCP proxy load balancer

Google Cloud offers separate global load balancers for different protocols. The global external HTTP(S) load balancer handles HTTP(S) traffic with proximity-based routing, while the global external TCP proxy load balancer handles TCP traffic with global anycast IP and proximity routing. Using both together provides the required support for both protocols in a multi-region architecture.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Global external HTTP(S) load balancer with TCP proxy

    Why it's wrong here

    The global external HTTP(S) load balancer does not support TCP proxy; TCP proxy is a separate load balancer. You cannot combine them into a single global load balancer. This option is technically invalid because these are distinct services. Thus, it does not meet the requirement.

  • ✗

    Global external TCP/UDP load balancer

    Why it's wrong here

    The global external TCP/UDP load balancer is for TCP and UDP traffic, but it does not support HTTP(S) and does not provide HTTP-specific features like URL mapping. It also does not route based on proximity for HTTP(S) traffic. Therefore, it does not meet the requirement for both HTTP(S) and TCP traffic with global routing.

  • ✓

    Global external HTTP(S) load balancer and global external TCP proxy load balancer

    Why this is correct

    To support both HTTP(S) and TCP traffic with global load balancing and proximity routing, you can use two separate load balancers: the global external HTTP(S) load balancer for HTTP(S) traffic and the global external TCP proxy load balancer for TCP traffic. Both are global and route to the closest healthy backend. This combination meets all requirements.

  • ✗

    Global external HTTP(S) load balancer

    Why it's wrong here

    The global external HTTP(S) load balancer provides global load balancing for HTTP(S) traffic, routing to the closest backend based on proximity. However, it does not support TCP traffic; it is designed for HTTP(S) only. Since the requirement includes TCP traffic, this option is insufficient.

About these practice questions

This PCA question is part of Courseiva's 807-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Google Cloud exam blueprint

This PCA practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCA exam.