mediumMultiple Select
Google ACE Practice Question: Which TWO statements are correct about deploying…
Which TWO statements are correct about deploying an application with an HTTP(S) load balancer on Compute Engine?
⚠ Common exam trap
A common mix-up: candidates confuse the TCP proxy load balancer's ability to handle HTTP traffic with the HTTP(S) load balancer's Layer 7 capabilities, leading them to incorrectly think TCP proxy is restricted to non-HTTP traffic.
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
✓
A network load balancer can be used for UDP traffic.
Option A is correct because a network load balancer (TCP/UDP load balancing) operates at Layer 4 and supports UDP traffic, which is essential for non-TCP protocols. Option E is correct because an HTTP(S) load balancer requires a backend service that references instance groups or NEGs, and that backend service must have a health check to determine which backends are healthy and eligible to receive traffic. Option B is incorrect because a TCP proxy load balancer handles TCP traffic, including HTTP/HTTPS, not only non-HTTP traffic. Option C is incorrect because SSL proxy load balancers are specifically designed to terminate SSL/TLS (HTTPS) traffic. Option D is incorrect because internal load balancers do not require a proxy instance; they use backend services and health checks like external load balancers.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
A network load balancer can be used for UDP traffic.
Why this is correct
A network load balancer is a pass-through, Layer 4 load balancer that forwards packets directly to backend instances without modifying or inspecting payload contents. Because it operates at the packet level, it can handle both TCP and UDP traffic, including protocols like DNS, NTP, or real-time UDP streams, making the statement correct.
- ✗
A TCP proxy load balancer can only be used for non-HTTP traffic.
Why it's wrong here
A TCP proxy load balancer terminates the client's TCP connection and opens a new TCP connection to the backend, but it does not inspect or parse HTTP payloads. Since HTTP runs over TCP, a TCP proxy load balancer can absolutely be used for HTTP traffic; it simply routes it at the TCP layer, so the statement that it is 'only for non-HTTP traffic' is false.
- ✗
SSL proxy load balancers cannot terminate HTTPS traffic.
Why it's wrong here
SSL proxy load balancers are specifically designed to terminate SSL/TLS encryption, including HTTPS traffic, before forwarding plaintext requests to backends. They perform SSL offloading and also allow for centralized TLS management, so the claim that they cannot terminate HTTPS traffic is incorrect.
- ✗
Internal load balancers require a proxy instance.
Why it's wrong here
Internal load balancers in Google Cloud are internal passthrough network load balancers that forward traffic directly to backend VMs without any proxy instance in the data path. They are fully managed and do not require you to provision or configure a separate proxy VM, contradicting the stated requirement.
- ✓
An HTTP(S) load balancer requires a backend service with a health check.
Why this is correct
An HTTP(S) load balancer is a proxy-based Layer 7 load balancer that requires every backend service to have at least one health check configured. The health check continuously verifies that backend instances are ready to receive traffic; without it, the load balancer cannot determine which instances are healthy and would not be able to route traffic correctly.
Go deeper
Related to this question
Learn chapter
GCP Service Accounts and Workload Identity
Key term
TCP Proxy Load Balancer
A TCP Proxy Load Balancer is a network device that terminates incoming TCP connections from clients, establishes a new TCP connection to a backend server, and relays data between the two, enabling advanced traffic management and security features.
Key term
UDP
UDP (User Datagram Protocol) is a communication protocol that sends data quickly without first checking if the receiver is ready or if the data arrived correctly.
About these practice questions
This ACE question is part of Courseiva's 775-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 →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This ACE 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 ACE exam.