Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Professional Cloud Database Engineer Exam - Topic 2 Question 65 Discussion

You are building an application that allows users to customize their website and mobile experiences. The application will capture user information and preferences. User profiles have a dynamic schema, and users can add or delete information from their profile. You need to ensure that user changes automatically trigger updates to your downstream BigQuery data warehouse. What should you do?
C) Use Firestore in Native mode, and store user profile data as a document. Update the user profile with preferences specific to that user and use the user identifier to query.
A) Store your data in Bigtable, and use the user identifier as the key. Use one column family to store user profile data, and use another column family to store user preferences.
B) Use Cloud SQL, and create different tables for user profile data and user preferences from your recommendations model. Use SQL to join the user profile data and preferences
D) Use Firestore in Datastore mode, and store user profile data as a document. Update the user profile with preferences specific to that user and use the user identifier to query.

Google Professional Cloud Database Engineer Exam - Topic 2 Question 65 Discussion

Actual exam question for Google's Professional Cloud Database Engineer exam
Question #: 65
Topic #: 2
[All Professional Cloud Database Engineer Questions]

You are building an application that allows users to customize their website and mobile experiences. The application will capture user information and preferences. User profiles have a dynamic schema, and users can add or delete information from their profile. You need to ensure that user changes automatically trigger updates to your downstream BigQuery data warehouse. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

Use Firestore in Datastore mode for new server projects. Firestore in Datastore mode allows you to use established Datastore server architectures while removing fundamental Datastore limitations. Datastore mode can automatically scale to millions of writes per second. Use Firestore in Native mode for new mobile and web apps. Firestore offers mobile and web client libraries with real-time and offline features. Native mode can automatically scale to millions of concurrent clients.


Contribute your Thoughts:

0/2000 characters
Cammy
1 month ago
B could work, but managing SQL joins adds extra overhead. Firestore is simpler!
upvoted 0 times
...
Nicholle
1 month ago
A is interesting, but Bigtable feels too complex for this use case.
upvoted 0 times
...
Jonelle
1 month ago
I agree, but D seems good too. Datastore mode might be more scalable.
upvoted 0 times
...
Kimi
2 months ago
I think option C is the best. Firestore is flexible for dynamic schemas.
upvoted 0 times
...
Gearldine
2 months ago
I agree, A looks like a solid choice for scalability!
upvoted 0 times
...
Dorothea
2 months ago
B seems too complicated with SQL joins.
upvoted 0 times
...
Jeniffer
2 months ago
Not sure if Firestore can handle all that data efficiently.
upvoted 0 times
...
Johnna
2 months ago
Firestore is great for real-time updates!
upvoted 0 times
...
Kiera
2 months ago
I think option C is the best for dynamic schemas.
upvoted 0 times
...
Edda
3 months ago
Haha, Cloud SQL? What is this, the 90s? Firestore all the way, baby!
upvoted 0 times
...
Loise
3 months ago
Hmm, I'm not sure about Bigtable for this use case. Seems a bit overkill.
upvoted 0 times
...
Nieves
3 months ago
D) is also a good choice, but I think C) gives you a bit more flexibility with the native Firestore features.
upvoted 0 times
...
Flo
4 months ago
I agree, Firestore in Native mode looks like the way to go here. Keeps things simple and scalable.
upvoted 0 times
...
Ollie
4 months ago
C) seems like the best option to handle the dynamic schema and automatically update the BigQuery data warehouse.
upvoted 0 times
...
Gretchen
4 months ago
I feel like using Bigtable could be overkill for this scenario. It seems more suited for large-scale analytics rather than user profile management.
upvoted 0 times
...
Viola
4 months ago
I practiced a similar question where we had to choose between SQL and NoSQL databases. I think using Cloud SQL could work, but it might not handle dynamic schemas as easily.
upvoted 0 times
...
Jerry
4 months ago
I'm a bit unsure about the differences between Firestore in Native mode and Datastore mode. I think they both store documents, but which one is better for this use case?
upvoted 0 times
...
Lera
4 months ago
I remember we discussed how Firestore can handle dynamic schemas well, so options C and D might be good choices.
upvoted 0 times
...
Nohemi
5 months ago
I'm a bit torn between options C and D. I'll need to research the differences between Firestore in Native mode and Datastore mode to see which one would be a better fit for this use case.
upvoted 0 times
...
Ona
5 months ago
I'm feeling pretty confident about this one. I think option C using Firestore in Native mode would be the way to go. It seems like the most flexible and scalable solution for handling the dynamic user profiles and triggering updates to the data warehouse.
upvoted 0 times
...
Shantay
5 months ago
Okay, I think I have a strategy here. I'll need to consider how the user data is structured and how it needs to be accessed in the BigQuery data warehouse. That should help me narrow down the best storage solution.
upvoted 0 times
...
Bernardo
5 months ago
Hmm, I'm a bit confused about the different storage options here. I'll need to review the pros and cons of Bigtable, Cloud SQL, and Firestore to decide which one would be the most suitable.
upvoted 0 times
...
Sherron
5 months ago
This seems like a tricky question. I'm not sure which option would be the best approach, but I'll try to think it through step-by-step.
upvoted 0 times
Laurene
26 days ago
This is definitely a tough one. I lean towards Firestore for flexibility.
upvoted 0 times
...
...

Save Cancel