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 Exam Professional-Cloud-Developer Topic 1 Question 85 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 85
Topic #: 1
[All Professional Cloud Developer Questions]

You are a developer at a social media company The company runs their social media website on-premises and uses MySQL as a backend to store user profiles and user posts. Your company plans to migrate to Google Cloud, and your team will migrate user profile information to Firestore. You are tasked with designing the Firestore collections. What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: C

Contribute your Thoughts:

Jess
3 months ago
Option C is the way to go, no doubt. Keeping those user posts nice and cozy in their own subcollections - it's like a Firestore hug for your data!
upvoted 0 times
Lauran
23 days ago
C) That's right! Having each user's posts in their own subcollection keeps the data organized and easy to access.
upvoted 0 times
...
Glenn
25 days ago
A) Create one root collection for user profiles, and store each user's post as a nested list in the user profile document.
upvoted 0 times
...
Chandra
26 days ago
C) Create one root collection for user profiles, and create one subcollection for each user's posts.
upvoted 0 times
...
Norah
30 days ago
Definitely, it's important to structure the Firestore collections in a way that makes sense for the data.
upvoted 0 times
...
Margarita
1 months ago
Agreed, it will keep the data organized and easily accessible.
upvoted 0 times
...
Pete
2 months ago
I think option C is the best choice. Each user's posts should have their own subcollection.
upvoted 0 times
...
...
Micheline
3 months ago
That's a good point, Belen. It really depends on how we want to structure the data for efficient querying and scalability.
upvoted 0 times
...
Belen
3 months ago
I see your point, Antione, but I think option D could also work well by organizing posts first and then linking them to user profiles.
upvoted 0 times
...
Antione
3 months ago
I disagree, I believe option B is better as it separates user profiles and posts into different collections for better organization.
upvoted 0 times
...
Lino
3 months ago
I'm going to have to go with option C. Nested subcollections just make sense for this use case, and it aligns with best practices for Firestore data modeling.
upvoted 0 times
...
Shayne
3 months ago
Option B is the best choice. Separating user profiles and posts into different root collections is more scalable and allows for more flexibility in the long run.
upvoted 0 times
...
Filiberto
3 months ago
I think option C is the way to go. It keeps the user profiles and posts nicely organized, and makes it easy to query data for a specific user.
upvoted 0 times
Tomas
2 months ago
Yeah, having a subcollection for each user's posts will definitely make it easier to manage and query the data.
upvoted 0 times
...
Haydee
3 months ago
I agree, option C seems like the best choice for organizing the data efficiently.
upvoted 0 times
...
...
Micheline
4 months ago
I think option C is the best choice because it allows for easy access to a user's posts within their profile.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77