Google Professional-Cloud-Architect Exam With Confidence Using Practice Dumps

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

According to Google Cloud's Anthos (now GKE Enterprise) documentation, Config Sync and Policy Controller are the official tools for multi-cluster and multi-cloud management. These tools allow for a GitOps approach to infrastructure and configuration.

Config Sync: Automatically synchronizes Kubernetes configurations (like YAML files for Namespaces, Roles, or Deployments) from a central Git repository to all registered clusters, whether they are in GKE or EKS. This ensures consistency across providers.

Policy Controller: Built on the open-source Gatekeeper project (using Open Policy Agent), it enforces security policies and compliance at scale. For example, it can prevent a developer from deploying a container that runs as root or requires excessive resources across both AWS and Google Cloud environments.

While Option A uses similar open-source technologies, Option C is the "Google-recommended" integrated solution that is fully managed and supported. This centralized management reduces the complexity of maintaining custom controllers (as mentioned in A) or scripts (as mentioned in B), providing a robust, enterprise-grade framework for hybrid and multi-cloud governance.