Question 280
A postincident review documents: A migration needs to analyze data held in Cloud SQL and BigQuery but engineers plan to copy every table on each query. Which ongoing check targets the underlying failure?
Explanation
Correct Answer
Document analytical freshness and source ownership in multi-database architecture. This is preventive rather than a one-time repair; it addresses the underlying failure: The design lacks an explicit ingestion or federation strategy across operational and analytical stores.
Incorrect Answers
The proposed check would include embedding size, indexing, recall, and update behavior in database requirements, helping with cases where an application wants semantic search over product text but has no plan for storing or indexing embedding vectors. The recurring exposure described here is that the design lacks an explicit ingestion or federation strategy across operational and analytical stores.
For the situation in which a regulated data archive holds multi-gigabyte images in database rows and backups become unnecessarily large, it makes sense to use object storage for large blobs where transactional database semantics are not required. Here, the design lacks an explicit ingestion or federation strategy across operational and analytical stores, so the safeguard misses the recurring fault.
This safeguard helps protect cases where a Cloud SQL read replica increasingly falls minutes behind after a bulk-import job starts. It leaves the main recurring failure untouched: the design lacks an explicit ingestion or federation strategy across operational and analytical stores.