You are planning to migrate the following on-premises data management solutions to Google Cloud:
* One MySQL cluster for your main database
* Apache Kafka for your event streaming platform
* One Cloud SQL for PostgreSQL database for your analytical and reporting needs You want to implement Google-recommended solutions for the migration. You need to ensure that the new solutions provide global scalability and require minimal operational and infrastructure management. What should you do?
Correct Answer: B
Cloud Spanner, Pub/Sub, and BigQuery are Google-recommended solutions for migrating your on-premises data management solutions to Google Cloud. They provide global scalability and require minimal operational and infrastructure management. Here is why:
Cloud Spanner is a fully managed, relational database service that offers strong consistency, high availability, and horizontal scalability across regions and continents. It is compatible with MySQL and can handle high-throughput OLTP workloads. It is a good choice for migrating your main database from MySQL to Google Cloud, as it can support your application's performance, availability, and growth requirements.
Pub/Sub is a fully managed, real-time messaging service that allows you to send and receive messages between independent applications. It is compatible with Apache Kafka and can handle high-volume event streaming and data ingestion. It is a good choice for migrating your event streaming platform from Kafka to Google Cloud, as it can support your application's reliability, scalability, and flexibility requirements.
BigQuery is a fully managed, serverless data warehouse that offers fast SQL queries, high scalability, and low cost. It is compatible with Cloud SQL for PostgreSQL and can handle complex analytical and reporting needs. It is a good choice for migrating your analytical and reporting database from Cloud SQL for PostgreSQL to Google Cloud, as it can support your application's speed, efficiency, and innovation requirements.
The other options are not correct because they either do not provide the required scalability, performance, or functionality. Option A is not correct because Cloud SQL is a regional, managed database service that does not offer the same level of scalability, availability, and consistency as Cloud Spanner. Option C is not correct because Memorystore is a regional, managed in-memory data store that does not offer the same level of functionality, durability, and integration as Pub/Sub. Option D is not correct because Cloud SQL is a regional, managed database service that does not offer the same level of scalability, performance, and cost-effectiveness as BigQuery.
Reference:
Migrating from MySQL to Cloud Spanner
Migrating from Apache Kafka to Cloud Pub/Sub
Migrating from Cloud SQL for PostgreSQL to BigQuery