PROFESSIONAL-CLOUD-DEVELOPER · Question #387
You are developing a new mobile game that will be deployed on GKE and Cloud Run as a set of microservices. Currently, there are no projections for the game's user volume. You need to store the…
The correct answer is D. Data type 1: Firestore. The correct answer is D because Firestore is the optimal choice for all three data types given the stated requirements. For leaderboard data (type 1), Firestore provides real-time updates, low latency reads, and automatic scaling - critical for competitive rankings with…
Question
You are developing a new mobile game that will be deployed on GKE and Cloud Run as a set of microservices. Currently, there are no projections for the game’s user volume. You need to store the following data types:
- Data type 1: leaderboard data
- Data type 2: player profiles, chats, and news feed
- Data type 3: player clickstream data for BI
You need to identify a data storage solution that is easy to use, cost-effective, scalable, and supports offline caching on the user’s device. Which data storage option should you choose for the different data types?
Options
- AData type 1: Memorystore
- BData type 1: Memorystore
- CData type 1: Firestore
- DData type 1: Firestore
How the community answered
(47 responses)- A17% (8)
- B4% (2)
- C11% (5)
- D68% (32)
Explanation
The correct answer is D because Firestore is the optimal choice for all three data types given the stated requirements. For leaderboard data (type 1), Firestore provides real-time updates, low latency reads, and automatic scaling - critical for competitive rankings with unpredictable user volume. For player profiles, chats, and news feed (type 2), Firestore's flexible document model handles these varied social data structures well, with built-in real-time listeners for chat. For player clickstream BI data (type 3), BigQuery (implied in option D) is the purpose-built serverless data warehouse for analytics at scale. Most importantly, Firestore is the only Google Cloud database that natively supports offline caching on mobile devices, satisfying that explicit requirement. Memorystore (options A/B) is an in-memory cache (Redis/Memcached) that lives server-side and does NOT support device-side offline caching, disqualifying it. Firestore is also easy to use, serverless (no capacity planning needed for unknown volume), and cost-effective at low usage.
Topics
Community Discussion
No community discussion yet for this question.