Answer-first summary for fast verification
Answer: HTTP(S) Load Balancer, Managed Instance Group on Compute Engine
The correct answers are **HTTP(S) Load Balancer** and **Managed Instance Group on Compute Engine**. - **HTTP(S) Load Balancer** is suitable because it's a global service that can route traffic to backend services in multiple regions, ensuring global accessibility. [Learn more](https://cloud.google.com/load-balancing/docs/https). - **Managed Instance Group on Compute Engine** allows the use of custom Linux distributions and supports auto-scaling to meet demand. [Learn more](https://cloud.google.com/compute/docs/instance-groups). Other options are not suitable because: - **Cloud Functions** does not support custom Linux distributions. [Learn more](https://cloud.google.com/functions). - **App Engine Standard environment** does not allow specifying a custom Linux distribution. [Learn more](https://cloud.google.com/appengine/docs/standard). - **Network Load Balance** is regional, not global, making it unsuitable for a globally accessible application. [Learn more](https://cloud.google.com/load-balancing/docs/network).
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your organization is planning to deploy a Python web application on Google Cloud. The application requires a custom Linux distribution and must be globally accessible, scaling automatically to meet demand. Which two solutions would you recommend?
A
HTTP(S) Load Balancer
B
Cloud Functions
C
App Engine Standard environment
D
Managed Instance Group on Compute Engine
E
Network Load Balance
No comments yet.