Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Exam Professional Cloud Developer Topic 7 Question 89 Discussion

Actual exam question for Google's Professional Cloud Developer exam
Question #: 89
Topic #: 7
[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

by Vanna at Aug 07, 2024, 04:21 PM

Limited Time Offer

25%

Off

Get Premium Professional Cloud Developer Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Chantay
3 months ago
I think option A could work too, as it keeps everything in one document for each user.
upvoted 0 times
...
Kallie
4 months ago
Hah, option D? What is this, a joke? Creating a root collection for posts and then subcollections for profiles? That's just asking for trouble!
upvoted 0 times
...
Reuben
4 months ago
I'm not sure about that. Wouldn't it be easier to just store the posts as a nested list in the user profile? Option A seems simpler to me.
upvoted 0 times
...
Anastacia
4 months ago
Agree with Natalie. Option C seems like the most logical and scalable approach. Creating subcollections for each user's posts is a smart way to organize the data.
upvoted 0 times
Kristal
3 months ago
I'm leaning towards Option D actually. Separating user profiles and posts could help with performance.
upvoted 0 times
...
Alline
3 months ago
Yeah, creating subcollections for each user's posts will definitely help with scalability in the long run.
upvoted 0 times
...
Jani
3 months ago
I see your point, but I still think Option C is the way to go. It keeps everything related to a user together.
upvoted 0 times
...
Tammi
3 months ago
I agree, option C does seem like the best choice for organizing the data efficiently.
upvoted 0 times
...
Val
3 months ago
I think Option B could work too, having a separate collection for user posts might make it easier to query.
upvoted 0 times
...
Graciela
3 months ago
I agree with you, Option C does seem like the best choice. It will make it easier to manage user posts.
upvoted 0 times
...
...
Rodrigo
4 months ago
I see both sides, but I think option C is more scalable in the long run.
upvoted 0 times
...
Theodora
4 months ago
I disagree, I believe option B is better. It will separate user profiles and posts clearly.
upvoted 0 times
...
Natalie
4 months ago
I think option C is the way to go. Separating user profiles and posts into different collections makes it easier to manage and scale the data.
upvoted 0 times
Taryn
3 months ago
Option C sounds good, it allows for easy access to user profiles and their corresponding posts.
upvoted 0 times
...
Rosina
4 months ago
I think option B might be better, it keeps user profiles and posts in separate collections but at the same level.
upvoted 0 times
...
Bok
4 months ago
I agree, having separate collections for user profiles and posts will make it easier to query and maintain the data.
upvoted 0 times
...
...
Therese
4 months ago
I think option C is the best choice. It will keep the user profiles and posts organized.
upvoted 0 times
...

Save Cancel