Question 240
After an incident where a commerce application needs a relational database with foreign keys and joins, but architects propose Bigtable for every record, which recurring control would best prevent the same defect?
Explanation
Correct Answer
Document transactional and relational semantics before adopting NoSQL storage. This is preventive rather than a one-time repair; it addresses the underlying failure: The service's access model conflicts with Bigtable's key-value and row-oriented transaction boundaries.
Incorrect Answers
This control would test actual database protocol connectivity rather than ping alone; it responds to the risk in which a new firewall rule blocks application TCP sessions to a private SQL instance although ICMP tests appear healthy. It would not address the current root cause: the service's access model conflicts with Bigtable's key-value and row-oriented transaction boundaries.
The proposed check would evaluate AlloyDB using application-scale benchmark evidence rather than product positioning, helping with cases where a high-throughput PostgreSQL-compatible analytics-heavy transactional application needs a managed service optimized for demanding reads. The recurring exposure described here is that the service's access model conflicts with Bigtable's key-value and row-oriented transaction boundaries.
The proposed check would use object storage for large blobs where transactional database semantics are not required, helping with cases where a regulated data archive holds multi-gigabyte images in database rows and backups become unnecessarily large. The recurring exposure described here is that the service's access model conflicts with Bigtable's key-value and row-oriented transaction boundaries.