MENU
You are developing an application hosted on Google Cloud that uses a MySQL relational database schem
a. 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?
Suggested Answer: A
Get Premium Professional Cloud Developer Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
https://cloud.google.com/spanner/docs/migrating-mysql-to-spanner#migration-process
Cloud SQL: Cloud SQL is a web service that allows you to create, configure, and use relational databases that live in Google's cloud. It is a fully-managed service that maintains, manages, and administers your databases, allowing you to focus on your applications and services.
https://cloud.google.com/sql/docs/mysql Cloud SQL for MySQL is a fully-managed database service that helps you set up, maintain, manage, and administer your MySQL relational databases on Google Cloud Platform.
33 comments · newest first
KR
Krissy
10 months ago
Firestore? That's not even a relational database!
IS
Isreal
10 months ago
I agree, Cloud SQL handles backups automatically!
DE
Delsie
11 months ago
Wait, why would you use Bigtable for a relational database?
SA
Sage
11 months ago
Cloud Spanner sounds cool, but is it really necessary here?
AH
Ahmad
11 months ago
Cloud SQL is the way to go for MySQL.
FA
Fatima
11 months ago
I feel like Firestore wouldn’t work well for this scenario either, since it’s more suited for NoSQL. Cloud SQL seems like the safest bet.
BR
Breana
11 months ago
I’m a bit confused about Bigtable; I don’t think it’s suitable for relational data like MySQL, right?
MA
Marcelle
12 months ago
I remember practicing a question similar to this, and I think Cloud Spanner might be overkill for just a MySQL database.
HO
Hortencia
12 months ago
I think Cloud SQL is the best option here since it’s fully managed and supports MySQL, but I'm not entirely sure about the backup features.
CH
Christiane
1 year ago
I'm leaning towards option A, Configure Cloud SQL to host the database. It seems like the most straightforward and low-maintenance solution, which is important since the team doesn't have a lot of time to manage the database.
LO
Loreta
1 year ago
The key here is that the team doesn't have time to fully manage the database, so I think the best approach is to go with a fully managed service like Cloud SQL. That way, Google will handle the heavy lifting, and the team can focus on the application development.
LA
Laurena
1 year ago
Hmm, I'm a bit unsure about this one. I know Cloud SQL is a good option, but I'm also wondering if Bigtable or Cloud Spanner might be better for handling the large volume of data. I'll need to review the differences between these services more closely.
DI
Dianne
1 year ago
This seems like a straightforward question. I think the best option is to go with Cloud SQL since it's a managed MySQL service that can handle the high volume of reads and writes, as well as backups and capacity planning.
LO
Lorrine
2 years ago
Cloud SQL is the way to go. It's the easiest and most straightforward option to get our database up and running quickly.
PA
Pamela
1 year ago
I think Cloud SQL is more user-friendly and efficient for our needs.
ST
Stefania
1 year ago
B) Deploy MySQL from the Google Cloud Marketplace to the database using a client, and import the schema.
MI
Micah
1 year ago
Cloud SQL is definitely the best choice for us. It's easy to manage and reliable.
MA
Marguerita
1 year ago
A) Configure Cloud SQL to host the database, and import the schema into Cloud SQL.
QU
Quentin
2 years ago
Haha, Firestore for a MySQL database? That's like trying to put a square peg in a round hole. E is definitely not the way to go here.
ME
Meaghan
1 year ago
B) Deploy MySQL from the Google Cloud Marketplace to the database using a client, and import the schema.
JA
Jani
1 year ago
A) Configure Cloud SQL to host the database, and import the schema into Cloud SQL.
SH
Sharika
2 years ago
I think Cloud SQL is the most cost-effective option for us right now.
JU
Justine
2 years ago
I'm not sure, I think Cloud Spanner might be a better choice for scalability.
TI
Tiffiny
2 years ago
I agree with Ivette. Cloud SQL seems like the best option for our needs.
MO
Mozelle
2 years ago
I'd go with D, Cloud Spanner. It's a great fit for the high read/write requirements and we don't have to worry about database administration.
AN
Antonio
1 year ago
Definitely, it's a scalable and fully managed solution that will save us time on database administration tasks.
BE
Bernadine
2 years ago
That sounds like a good choice. Cloud Spanner can handle the high volume of reads and writes efficiently.
KR
Kris
2 years ago
D) Configure Cloud Spanner to host the database, and import the schema into Cloud Spanner.
IV
Ivette
2 years ago
I think we should go with option A and configure Cloud SQL to host the database.
KI
Kimberely
2 years ago
Option A seems like the obvious choice here. Cloud SQL takes care of the database management so we can focus on the application.
LA
Lavonne
2 years ago
User 3: Definitely, it's important to have a reliable solution like Cloud SQL for our database needs.
LA
Lauran
2 years ago
User 2: Yeah, Cloud SQL will handle the database management for us, so we can focus on other tasks.
AN
Angelo
2 years ago
User 1: I agree, option A with Cloud SQL sounds like the best choice for us.