Professional Cloud ArchitectDesign and plan a cloud solution architectureEasy
A global company is migrating its legacy content management system (CMS) to Google Cloud. The CMS hosts millions of static assets (images, videos, documents) that are accessed globally by users. They need a storage solution that offers extremely high availability, global access with low latency, and efficient caching at the edge. The content is infrequently updated but frequently read.
- ACloud Storage Regional bucket with external HTTP(S) Load Balancer
- BCloud SQL with Cloud CDN
- CFilestore Enterprise with Cloud VPN
- DCloud Storage Multi-Regional bucket with Cloud CDN
Show answer & explanationAnswer & explanation
Correct answer: D. Cloud Storage Multi-Regional bucket with Cloud CDN
A Cloud Storage Multi-Regional bucket provides high availability and global access for static assets. Integrating it with Cloud CDN ensures low-latency delivery to global users through edge caching, which is ideal for infrequently updated and frequently read content.
Why the other options are wrong
- A. A Regional bucket would not provide the best global access and availability. An external HTTP(S) Load Balancer could front it, but Cloud CDN is explicitly designed for content delivery network capabilities.
- B. Cloud SQL is a relational database, entirely unsuitable for storing and serving millions of static assets. While Cloud CDN is relevant, the storage backend is incorrect.
- C. Filestore is a managed file storage service, not typically used for serving static web assets globally with CDN capabilities. Cloud VPN is for network connectivity, not content delivery.
Cloud Storage Multi-Regional + Cloud CDN
A combination of Google Cloud services for highly available, globally accessible, and low-latency delivery of static content.
- Cloud Storage Multi-Regional provides geo-redundancy and high availability.
- Cloud CDN caches content at Google's edge locations worldwide.
- Ideal for static assets, media, and web content with global users.
Memory trick: Store it globally, cache it locally, deliver it swiftly.