PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #148
When comparing Google Cloud managed NoSQL services, which cost component should you consistently emphasize for a precise TCO analysis?
The correct answer is B. Query execution and index upkeep costs. In Google Cloud NoSQL services (Firestore, Bigtable, Datastore), the dominant and most variable cost drivers are read/write/delete operations and index maintenance. Firestore charges per document read and write; maintaining composite indexes multiplies write costs because every i
Question
When comparing Google Cloud managed NoSQL services, which cost component should you consistently emphasize for a precise TCO analysis?
Options
- AStorage capacity costs
- BQuery execution and index upkeep costs
- CCMEK for data at rest
How the community answered
(26 responses)- A8% (2)
- B88% (23)
- C4% (1)
Explanation
In Google Cloud NoSQL services (Firestore, Bigtable, Datastore), the dominant and most variable cost drivers are read/write/delete operations and index maintenance. Firestore charges per document read and write; maintaining composite indexes multiplies write costs because every indexed field triggers additional writes on each document update. Bigtable charges per node-hour and per read/write operation rate. These operational costs grow non-linearly with query complexity and data mutation rates, making them the most impactful factor in a precise TCO model. Storage costs (Option A) are relatively predictable and cheap per GB. CMEK (Option C) is a security feature, not a primary cost driver.
Topics
Community Discussion
No community discussion yet for this question.