nerdexam
Google

PROFESSIONAL-CLOUD-DEVELOPER · Question #244

You are developing an application hosted on Google Cloud that uses a MySQL relational database schema. The application will have a large volume of reads and writes to the database and will require bac

The correct answer is A. Configure Cloud SQL to host the database, and import the schema into Cloud SQL.. The requirements are: MySQL relational schema, high read/write volume, automated backups, capacity planning, and minimal management. Cloud SQL (A) is Google's fully managed relational database service that supports MySQL natively - it handles automated backups, failover, storage

Designing and implementing data storage solutions

Question

You are developing an application hosted on Google Cloud that uses a MySQL relational database schema. The application will have a large volume of reads and writes to the database and will require backups and ongoing capacity planning. Your team does not have time to fully manage the database but can take on small administrative tasks. How should you host the database?

Options

  • AConfigure Cloud SQL to host the database, and import the schema into Cloud SQL.
  • BDeploy MySQL from the Google Cloud Marketplace to the database using a client, and import the
  • CConfigure Bigtable to host the database, and import the data into Bigtable.
  • DConfigure Cloud Spanner to host the database, and import the schema into Cloud Spanner.
  • EConfigure Firestore to host the database, and import the data into Firestore.

How the community answered

(65 responses)
  • A
    77% (50)
  • B
    3% (2)
  • C
    12% (8)
  • D
    6% (4)
  • E
    2% (1)

Explanation

The requirements are: MySQL relational schema, high read/write volume, automated backups, capacity planning, and minimal management. Cloud SQL (A) is Google's fully managed relational database service that supports MySQL natively - it handles automated backups, failover, storage scaling, and patching with minimal administrative overhead. Deploying MySQL from Marketplace (B) still requires manual VM-level management. Bigtable (C) is a NoSQL wide-column store - incompatible with a relational MySQL schema. Cloud Spanner (D) is a fully managed relational database but uses its own dialect (not MySQL-compatible), requiring significant schema and query rewrites. Firestore (E) is a NoSQL document database, unsuitable for a relational schema.

Topics

#Cloud SQL#Managed Databases#Database Selection#MySQL

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVELOPER Practice