Google Associate Cloud Engineer
Get started today
Ultimate access to all questions.
To provide a comprehensive understanding of the migration needs to Google Cloud, consider the following scenario:
Your organization is in the process of migrating its on-premises data management solutions to Google Cloud. The current on-premises setup includes:
• A MySQL cluster that serves as your primary operational database.
• An Apache Kafka setup used for event streaming purposes.
• A Cloud SQL for PostgreSQL database that supports your analytical and reporting requirements.
You aim to adopt Google-recommended migration strategies to ensure that the migrated solutions offer global scalability and demand minimal effort in terms of operational and infrastructure management. What steps should you take to achieve these goals?
To provide a comprehensive understanding of the migration needs to Google Cloud, consider the following scenario:
Your organization is in the process of migrating its on-premises data management solutions to Google Cloud. The current on-premises setup includes: • A MySQL cluster that serves as your primary operational database. • An Apache Kafka setup used for event streaming purposes. • A Cloud SQL for PostgreSQL database that supports your analytical and reporting requirements.
You aim to adopt Google-recommended migration strategies to ensure that the migrated solutions offer global scalability and demand minimal effort in terms of operational and infrastructure management. What steps should you take to achieve these goals?
Explanation:
Option B is the correct answer because the question requires solutions that provide global scalability and minimal operational and infrastructure management. Cloud Spanner is chosen over Cloud SQL for MySQL since Cloud Spanner is designed for global scalability. Apache Kafka is best replaced with Pub/Sub for event streaming as it fits well within Google's cloud ecosystem with high availability and scalability. For the analytical and reporting needs, BigQuery is more suitable for handling large-scale queries and analytics compared to Cloud SQL for PostgreSQL.