Explanation:
The requirement is to serve content from two backends while adhering to Google's recommended practices. The correct approach involves creating a HTTPS Load Balancer with a backend service for the MIG to handle /app/ requests and a backend bucket for Cloud Storage to manage /static/ requests. Configuring www.my-new-gcp-ace-website.com as an A record pointing to the load balancer's address ensures proper routing. This method leverages Google's Cloud HTTPS Load Balancer for efficient path-based routing without the need for additional proxies like HAProxy, aligning with best practices for simplicity and scalability. References: Cloud DNS Records, Adding Backend Buckets, URL Maps.
Ultimate access to all questions.
No comments yet.
You aim to serve files under the URL https://www.my-new-gcp-ace-website.com/static/ from Cloud Storage, while the URL https://www.my-new-gcp-ace-website.com/app/ should be managed by a Compute Engine managed instance group (MIG). Following Google's recommended practices, how should you configure load balancing?
A
B
C
D