nerdexam
Google

PROFESSIONAL-CLOUD-ARCHITECT · Question #369

A global media company is launching a new web application. The application backend is hosted on Compute Engine in us-central1 and serves both static assets (images, CSS, and JavaScript) and dynamic…

The correct answer is B. Enable Cloud CDN for the backend service that serves the static assets, and configure it as part D. Deploy the application frontend service to Compute Engine managed instance groups in regions. Enabling Cloud CDN on a global external HTTP(S) Load Balancer caches static assets at Google’s edge locations, reducing latency for users worldwide. Deploying the frontend service in multiple regions and using a global external HTTP(S) Load Balancer routes users to the nearest…

Submitted by takeshi77· Mar 30, 2026Designing and planning a cloud solution architecture

Question

A global media company is launching a new web application. The application backend is hosted on Compute Engine in us-central1 and serves both static assets (images, CSS, and JavaScript) and dynamic, user-specific content from a Cloud SQL database in the same region. Early user feedback from Europe and Asia indicates significant page load delays due to slow loading static content. You need to design a solution that minimizes latency for all global users accessing the static content. What should you do? (Choose two.)

Options

  • AUse a regional external Network Load Balancer in us-central1 to better distribute the incoming
  • BEnable Cloud CDN for the backend service that serves the static assets, and configure it as part
  • CVertically scale the Compute Engine instances in us-central1 by increasing their machine size.
  • DDeploy the application frontend service to Compute Engine managed instance groups in regions
  • ECreate Cloud SQL read replicas in regions in Europe and Asia, and direct all database read traffic

How the community answered

(43 responses)
  • A
    7% (3)
  • B
    81% (35)
  • C
    2% (1)
  • E
    9% (4)

Explanation

Enabling Cloud CDN on a global external HTTP(S) Load Balancer caches static assets at Google’s edge locations, reducing latency for users worldwide. Deploying the frontend service in multiple regions and using a global external HTTP(S) Load Balancer routes users to the nearest regional backend, further reducing the time to fetch static content from a geographically closer origin when it is not already served from cache.

Topics

#Cloud CDN#static asset caching#global load balancer#managed instance groups

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-ARCHITECT Practice