Answer: External HTTPS Load Balancer

## Explanation The correct answer is **C) External HTTPS Load Balancer**. ### Why this is correct: 1. **External HTTPS Load Balancer** is specifically designed to terminate SSL/TLS connections at the load balancer level and then forward traffic to backend instances over HTTPS. 2. It operates at Layer 7 (application layer) of the OSI model and can handle HTTP/HTTPS traffic with SSL termination capabilities. 3. This load balancer can distribute traffic to instance groups, including managed instance groups and unmanaged instance groups. ### Why other options are incorrect: - **A) Network Load Balancer**: This operates at Layer 4 (transport layer) and is designed for TCP/UDP traffic. It does not terminate SSL/TLS connections. - **B) Internal TCP Load Balancer**: This is for internal traffic within a VPC and operates at Layer 4. It does not handle SSL termination. - **D) SSL Proxy Load Balancer**: This is designed for non-HTTP SSL traffic (like SMTP, IMAP, etc.) and terminates SSL connections, but it's not specifically designed to serve traffic to instance groups over HTTPS. It's more for TCP traffic with SSL termination. ### Key Features of External HTTPS Load Balancer: - SSL/TLS termination at the load balancer - HTTP/HTTPS traffic distribution - URL-based routing - Host and path-based routing - Support for WebSocket and HTTP/2 - Health checks for backend instances - Integration with Cloud CDN This load balancer is ideal for web applications that require SSL termination and HTTPS traffic distribution to backend instance groups.

Author: Rodrigo Sales