Explanation:
The application tier typically requires internal load balancing as it communicates with the web tier (frontend) and database tier (backend) within the VPC. An internal HTTP(S) load balancer (option C) is designed to distribute traffic to backend services within a Google Cloud network, making it suitable for internal tiers like the application layer.
Thus, configuring a new internal HTTP(S) load balancer (option C) isolates the application tier and ensures proper internal traffic distribution.
Ultimate access to all questions.
No comments yet.
You are setting up load balancing for a three-tier application (web, application, and database). An external HTTP(S) load balancer is already configured for the web tier. How should you configure load balancing for the application tier servers?
A
Configure a forwarding rule on the existing load balancer for the application tier.
B
Configure equal cost multi-path routing on the application servers.
C
Configure a new internal HTTP(S) load balancer for the application tier.
D
Configure a URL map on the existing load balancer to route traffic to the application tier.