For this question, refer to the Mountkirk Games case study. You are in charge of the new Game Backend Platform architecture. The game communicates with the backend over a REST API.
You want to follow Google-recommended practices. How should you design the backend?
A. Create an instance template for the backend. For every region, deploy it on a multi-zone managed instance group. Use an L4 load balancer.
B. Create an instance template for the backend. For every region, deploy it on a single-zone managed instance group. Use an L4 load balancer.
C. Create an instance template for the backend. For every region, deploy it on a multi-zone managed instance group. Use an L7 load balancer.
D. Create an instance template for the backend. For every region, deploy it on a single-zone managed instance group. Use an L7 load balancer.
I think answer is C.
This game type is mobile.
Check this link : https://cloud.google.com/solutions/gaming/cloud-game-infrastructure#dedicated_game_server
I recommend this section : ‘Request/response based servers’
explain : In particular, however, mobile game servers, without a critical demand for real-time communication, have adopted HTTP request and response semantics like those used in web hosting.
this game use HTTP load balancer. HTTP load balancer is L7.
Agree should be C. You’ll use App load balancer for APIs not network.
Cloud TCP Proxy Load Balancing is intended for non-HTTP traffic
“Cloud TCP Proxy Load Balancing is intended for non-HTTP traffic. For HTTP traffic, use HTTP Load Balancing instead. For proxied SSL traffic, use SSL Proxy Load Balancing.”
REST API is based on HTTP Protocal, I think L7 LB is more propriate…
A is correct.Check this: https://cloud.google.com/load-balancing/docs/tcp/
For rest api tcp proxy load balancer (L3/L4) is recommended
answer should be C not A. Use L7Load balancer in front of Instance groups across the regions.