Google Cloud SQL - Database migration to Cloud SQL MCQ

Google Cloud SQL – 37 – Database migration to Cloud SQL MCQ

1 / 16

1. What is the primary goal of database migration to Google Cloud SQL?

Data encryption

Data compression

Data visualization

Transitioning data to cloud-native database services

2 / 16

2. Which database engines are currently supported by Google Cloud SQL for migration?

PostgreSQL and MongoDB

MySQL and PostgreSQL

SQL Server and Cassandra

MySQL and Oracle

3 / 16

3. Why is assessing data volume essential before migrating a database to Google Cloud SQL?

To identify security vulnerabilities

To estimate the time required for migration

To determine compatibility with Google Cloud SQL

To minimize data transfer costs

4 / 16

4. What does “offline migration” in the context of database migration mean?

Migrating data while the source database is read-only

Migrating data in batches

Migrating data without any downtime

Migrating data with minimal downtime

5 / 16

5. Which Google Cloud service provides continuous data replication for online database migration?

Google Dataflow

Google Cloud Storage

Database Migration Service (DMS)

Google BigQuery

6 / 16

6. What is the purpose of schema mapping during database migration?

Reducing storage costs

Aligning the source database schema with the target Google Cloud SQL instance

Optimizing query performance

Automating data compression

7 / 16

7. Which method involves exporting data from the source database and then importing it into Google Cloud SQL?

Hybrid migration

Online migration

Streaming migration

Offline migration

8 / 16

8. Why is thorough testing and validation essential during the database migration process?

To automate data compression

To ensure data accuracy and application compatibility

To assess the source database's performance

To minimize data transfer time

9 / 16

9. What role does a maintenance window or cut-over event play in database migration?

To automate data replication

To migrate data continuously

To optimize query performance

To transition from the old database to the new one

10 / 16

10. Which practice is NOT recommended for successful database migration to Google Cloud SQL?

Skipping data transfer to save time

Regularly monitoring and optimizing the Google Cloud SQL instance

Extensive testing and validation

Backing up the source data before migration

11 / 16

11. What is the primary focus of data backup before initiating database migration?

Minimizing data transfer costs

Ensuring data accuracy

Preventing data loss

Reducing data transfer time

12 / 16

12. Which migration method is best suited for scenarios where minimal downtime is a critical requirement?

Streaming migration

Offline migration

Online migration

Hybrid migration

13 / 16

13. What should you consider when selecting a target Google Cloud SQL database engine for migration?

Data volume

Source database engine compatibility

Data encryption method

Data visualization tools

14 / 16

14. Which migration method involves continuous data replication?

Data export/import

Hybrid migration

Streaming migration

Offline migration

15 / 16

15. What is the primary role of the Database Migration Service (DMS) in online database migration?

Data backup

Continuous data replication

Data visualization

Data transformation

16 / 16

16. Why should organizations document the database migration process?

For future reference and auditing

To automate data compression

To minimize downtime

To improve data transfer efficiency

Your score is

Google Cloud SQL – Database migration to Cloud SQL MCQ