Exam Professional Cloud Database Engineer topic 1 question 92 discussion

bigquery - Analytics and reporting

This question is poorly worded. I interpret it as: you have a ticketing system that needs an analytics and reporting app. Which database for this analytics and reporting app (not the ticketing system)? It should be BQ. However, it could also be read as what database for the ticketing system which also happens to need analytics and reporting. Which means the answer should be Spanner. Very confusing, but I'm leaning towards B for BQ based on my first interpretation.

C. The answer is cloud spanner. They need a DDBB, big query is not a DDBB

Marketing analytics https://cloud.google.com/bigquery?hl=en#marketing-analytics

C because OLTP supported in spanner not in BQ

the question ask about the database for the new app which is analytic and reporting so this should BQ.

option B - managing hundreds of terabytes of data and supporting an online marketing analytics and reporting application, BigQuery (Option B) is the most suitable choice

The answer is C Bigquery is not a Database " You need to select a relational database " Bigquery is a Datawarehouse

It might be both B and C. B- for analytic purpose but I would be inclining to C as we need OLTP database for ticketing systems.

Bigquery is relational and recomanded for analytics: https://cloud.google.com/products/databases

This is an analytics problem suited for BigQuery. Cloud Spanner isn't a good solution for analytics queries that scan a full table to do aggregations of the data because the query would span multiple (or all) shards).

C. Cloud SQL could not scale to 100s of TBs. Eliminate A. Neither Big Query nor Bigtable are relational (although BigQuery does support SQL). Eliminate B and D. That leaves C.

Cloud SQL has a double-digit TB storage limit so it's Cloud Spanner.

Big query is data warehouse not a relational database

Analytical Database with no transactions my vote B

B - This is a new application used for analytics, it does not need to take care of the DML required by the ticketing system

Spanner