Exam Associate Cloud Engineer topic 1 question 292 discussion

Cloud SQL for customer data. Cloud Storage (Archive) for historical logs, and Bigtable for sensor data. - Customer data: Complex queries and relational structure are best served by Cloud SQL rather than Firestore; Spanner is overkill and costlier unless you need global consistency and horizontal scale. - Historical logs: “Accessed infrequently” points to Archive as the most cost‑effective storage. If you anticipate more frequent reads (e.g., monthly), Coldline could be chosen instead, but Archive minimizes cost when reads are rare. - Sensor data: Bigtable excels at high‑throughput, time‑series ingestion and can handle eventual analyses with tolerance for some data loss; BigQuery is not ideal for sustained, ultra‑high write rates.

if I consider it infrequent more than once a year

- Structured Transactional data (Cloud SQL) - Logs + Infrequent access (Cloud Storage Archive Class) - Sensor Data (Big Table)

Structured - CloudSQL , Firestore is no-SQL (So not A) Large Volume and Infrequent - Coldline/Archive - It doesn't say how infrequent, but safe bet for 'historical logs' is Coldline at least or Archive (So not A) Also: Coldline Storage Use Case: Suitable for data that is infrequently accessed, like historical records, compliance archives, and disaster recovery data Real-time and write high velocity - BigTable is for high-performance, scalable db for real-time operations applications and massive amounts of data that require fast reads and writes. BigQuery's strength is NOT real-time transactional processing or frequent individual record updates/deletions. (So not B) C is the only viable answer left. (D doesn't make sense from the needs of the question).

Structured and complex queries --> Firestore can handle it Large volume and infrequent --> Cloud storage Nearline Real-time and write high velocity --> Bigtable