Question: What is Cloud Bigtable NOT good for?
- It’s not good for highly structured databases or transactional databases.
- It's not good for very large amounts of data.
- It's not good for flat data and databases with lots of read-write actions.
- It's not good for analytical data.
Explanation
Cloud Bigtable is a NoSQL wide-column database designed for large-scale analytical and operational workloads. It is optimized for high throughput, low latency, and very large datasets. Workloads that depend on relational schemas, joins, or multi-row transaction behavior require a different database model. In Google Cloud positioning, Cloud Bigtable fits high-volume key-value and time-series patterns rather than traditional relational transaction processing.
Why the other options are incorrect
Very large amounts of data is a core use case for Cloud Bigtable, not a limitation.
Flat data and databases with lots of read-write actions aligns with Cloud Bigtable access patterns.
Analytical data is supported because Cloud Bigtable is built for analytical and operational workloads.
Source for verification
https://cloud.google.com/bigtable/docs/overview
https://cloud.google.com/bigtable/docs/schema-design
The answer(s) to the question is highlighted in the BOLD text above. You can also find more questions and answers related to the exams on the "Google Cloud Platform Business Professional" page.