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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Google Professional Cloud Developer Exam - 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

by Cory at Jun 24, 2024, 10:48 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Junita
4 months ago
I’m surprised they’re not using a more relational approach with MySQL.
upvoted 0 times
...
Reynalda
4 months ago
Wait, why would you create a subcollection for profiles? That seems odd.
upvoted 0 times
...
Remona
4 months ago
Option B could work too, but it feels less organized.
upvoted 0 times
...
Theodora
4 months ago
Definitely agree with C! Subcollections are the way to go.
upvoted 0 times
...
Frederick
5 months ago
I think option C makes the most sense for organizing posts.
upvoted 0 times
...
Ben
5 months ago
I’m a bit confused about the subcollections. Wouldn't option D make more sense if we prioritize posts over profiles?
upvoted 0 times
...
Verda
5 months ago
I practiced a similar question, and I think nesting posts within user profiles might complicate queries. So, option C seems like the best choice.
upvoted 0 times
...
Hui
5 months ago
I'm not entirely sure, but I feel like having a separate collection for posts could lead to better performance. Maybe option B?
upvoted 0 times
...
Dorsey
5 months ago
I remember we discussed the importance of structuring data in Firestore for scalability. I think option C makes sense for that.
upvoted 0 times
...
Fallon
5 months ago
I feel pretty confident about this one. Based on the information provided, I think option C is the best approach - creating one root collection for user profiles and a subcollection for each user's posts. This will allow us to easily query and access the data we need.
upvoted 0 times
...
Cletus
5 months ago
Okay, let's think this through step-by-step. We want to store user profiles and user posts, and the question is asking about the Firestore collection design. I'd start by considering how the data will be accessed and queried.
upvoted 0 times
...
Demetra
5 months ago
Hmm, I'm a bit unsure about this one. I know Firestore has different ways to model data, but I'm not sure which approach would be best here. I'll need to carefully consider the tradeoffs between the options.
upvoted 0 times
...
Izetta
5 months ago
This seems like a straightforward design question. I'd start by thinking about the relationships between user profiles and user posts, and how that should be reflected in the Firestore structure.
upvoted 0 times
...
Raymon
6 months ago
I'm a bit confused by this question. I'm not sure which approach would be best. Maybe I'll try a few options and see what works.
upvoted 0 times
...
Jess
2 years 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
2 years 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
2 years 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
2 years ago
C) Create one root collection for user profiles, and create one subcollection for each user's posts.
upvoted 0 times
...
Norah
2 years ago
Definitely, it's important to structure the Firestore collections in a way that makes sense for the data.
upvoted 0 times
...
Margarita
2 years ago
Agreed, it will keep the data organized and easily accessible.
upvoted 0 times
...
Pete
2 years ago
I think option C is the best choice. Each user's posts should have their own subcollection.
upvoted 0 times
...
...
Micheline
2 years 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
2 years 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
2 years 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
2 years 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
2 years 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
2 years 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 years 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
2 years ago
I agree, option C seems like the best choice for organizing the data efficiently.
upvoted 0 times
...
...
Micheline
2 years 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