PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #130
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…
The correct answer is C. Use Firestore in Native mode, and store user profile data as a document. Update the user profile. Firestore in Native mode is the correct choice because: (1) it natively supports document-based storage with a schema-less, flexible structure ideal for dynamic user profiles; (2) it offers real-time listeners that can trigger Cloud Functions on document changes, enabling…
Question
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?
Options
- AStore your data in Bigtable, and use the user identifier as the key. Use one column family to store
- BUse Cloud SQL, and create different tables for user profile data and user preferences from your
- CUse Firestore in Native mode, and store user profile data as a document. Update the user profile
- DUse Firestore in Datastore mode, and store user profile data as a document. Update the user
How the community answered
(49 responses)- A14% (7)
- B6% (3)
- C78% (38)
- D2% (1)
Explanation
Firestore in Native mode is the correct choice because: (1) it natively supports document-based storage with a schema-less, flexible structure ideal for dynamic user profiles; (2) it offers real-time listeners that can trigger Cloud Functions on document changes, enabling automatic downstream BigQuery updates via the BigQuery Streaming API or the native Firestore-to-BigQuery export; and (3) it has a native BigQuery export integration. Option D (Firestore in Datastore mode) lacks Native mode's real-time listeners and direct BigQuery streaming integration. Options A and B (Bigtable and Cloud SQL) use rigid schemas that do not accommodate the dynamic, user-defined profile fields, and neither provides automatic BigQuery trigger mechanisms.
Topics
Community Discussion
No community discussion yet for this question.