Pass the Google Google Cloud Certified Professional-Cloud-Architect Questions and answers with CertsForce

The Google Cloud database migration path follows a " like-for-like " managed service strategy. Cloud SQL is the recommended destination for MySQL and SQL Server workloads that do not require the massive horizontal scale of Spanner, fitting Cymbal’s " Technical Stack Modernization " goals. Memorystore is the managed service for Redis, and Firestore is the native NoSQL replacement for MongoDB.

For the image storage requirement, Cloud Storage Coldline is the mathematically correct choice for data accessed " less and less frequently " with a retention period exceeding 90 days . According to Cloud Storage documentation , Coldline is specifically designed for data accessed at most once a quarter (90 days). Using Object Lifecycle Management to move images from Standard to Coldline allows Cymbal to " reduce costs " while keeping images " immediately accessible " (unlike Archive storage, which may have different trade-offs). Option C is less optimal because Nearline is intended for 30-day access patterns; given the images stay for 90+ days and usage drops significantly, the deeper savings of Coldline are preferred. Option A is over-engineered (Spanner for all) and expensive, while Option B contradicts the requirement to " reduce costs " by increasing operational overhead

A " cloud-first " modernization strategy for a retail product catalog typically involves moving from legacy relational databases to high-performance, managed services. AlloyDB for PostgreSQL is Google Cloud ' s premier choice for demanding transactional workloads. It offers superior performance (up to 4x faster than standard PostgreSQL) and built-in high availability, making it ideal for the low-latency requirements of web applications and AI virtual agents.

Option A follows the architecturally sound pattern of separating structured data from unstructured assets. Cloud Storage is the industry standard for storing " product images, " providing massive scalability, high availability, and low cost through lifecycle management.

Option B is less ideal because Bigtable is not designed for storing binary image blobs efficiently, and Spanner can be significantly more expensive and complex to manage if global multi-region consistency is not a strict requirement for the " minimizing operational costs " goal. Option C is incorrect because Filestore (NFS) is not a suitable primary database for a modern web application catalog. Option D is technically flawed as Cloud Storage is not an efficient primary database for structured application queries, and BigQuery is an analytical warehouse, not an image store. By combining AlloyDB and Cloud Storage, Cymbal achieves a performant, scalable, and cost-optimized foundation for their digital transformation.