How should you design the backend?

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.

Download Printable PDF. VALID exam to help you PASS.

6 thoughts on “How should you design the backend?

  1. 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.

  2. “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…

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.