Google PCA Manage implementation of cloud architecture Practice Question
A company is planning to deploy a global web application on Google Cloud. They expect low latency for users worldwide and need to serve static content (images, CSS) as well as dynamic API responses. Which architecture should they use?
⚠ Common exam trap
Google Cloud often tests the misconception that DNS geo-routing alone (Option C) can provide low-latency global content delivery, but it lacks caching and introduces DNS resolution delays, making it unsuitable for static content without a CDN.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Cloud CDN in front of an external HTTPS Load Balancer with backend services in multiple regions.
Cloud CDN in front of an external HTTPS Load Balancer with backend services in multiple regions is correct because it provides global anycast IP termination, low-latency content delivery via Google's edge cache for static content, and dynamic API requests are forwarded to the nearest healthy backend in the closest region. This architecture meets both the low-latency requirement for users worldwide and the need to serve both static and dynamic content efficiently.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use Cloud CDN in front of an external HTTPS Load Balancer with backend services in multiple regions.
Why this is correct
Cloud CDN caches static content at edge, and Load Balancer routes dynamic requests to nearest backend.
- ✗
Use Cloud NAT to allow egress traffic from instances and distribute static content via a shared VPC.
Why it's wrong here
Cloud NAT is for outbound traffic, not content delivery.
- ✗
Use Cloud DNS with geo-routing to direct users to the closest regional Cloud Run service.
Why it's wrong here
Cloud DNS does not cache content; it only resolves DNS. Cloud Run is for serverless, but static content would still need a CDN.
- ✗
Use VPC Network Peering to connect multiple regional VPCs and serve content from a central location.
Why it's wrong here
Peering doesn't provide global caching or low latency; it just connects networks.
Go deeper
Related to this question
Learn chapter
Introduction to Google Cloud Platform
Key term
Cloud CDN
A Cloud CDN is a network of servers spread around the world that stores copies of your website or app content so it loads faster for users no matter where they are.
Key term
Latency
Latency is the time delay between a request being sent over a network and the response being received, often measured in milliseconds.
About these practice questions
Courseiva writes every PCA question from scratch — 955 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PCA practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCA exam.