nerdexam
Google

PROFESSIONAL-CLOUD-DATABASE-ENGINEER · Question #35

You are responsible for designing a new database for an airline ticketing application in Google Cloud. This application must be able to: - Work with transactions and offer strong consistency. - Work…

The correct answer is B. Use Cloud Spanner in a multi-region configuration. The airline ticketing application has three hard requirements: (1) ACID transactions with strong consistency, (2) structured + semi-structured (JSON) data, and (3) transparent global multi-region scaling. Cloud Spanner is the only Google Cloud database that satisfies all three…

Database Architecture Design

Question

You are responsible for designing a new database for an airline ticketing application in Google Cloud. This application must be able to:

  • Work with transactions and offer strong consistency.
  • Work with structured and semi-structured (JSON) data.
  • Scale transparently to multiple regions globally as the operation

grows. You need a Google Cloud database that meets all the requirements of the application. What should you do?

Options

  • AUse Cloud SQL for PostgreSQL with both cross-region read replicas.
  • BUse Cloud Spanner in a multi-region configuration.
  • CUse Firestore in Datastore mode.
  • DUse a Bigtable instance with clusters in multiple regions.

How the community answered

(19 responses)
  • A
    11% (2)
  • B
    79% (15)
  • C
    5% (1)
  • D
    5% (1)

Explanation

The airline ticketing application has three hard requirements: (1) ACID transactions with strong consistency, (2) structured + semi-structured (JSON) data, and (3) transparent global multi-region scaling. Cloud Spanner is the only Google Cloud database that satisfies all three: it provides external strong consistency with distributed transactions, supports both relational (structured) and JSON data types, and scales horizontally across multiple regions with zero downtime. Option A (Cloud SQL) doesn't scale transparently across regions. Option C (Firestore) is NoSQL and lacks full SQL transaction support. Option D (Bigtable) is a wide-column NoSQL store, not SQL-compliant, and lacks strong transactional consistency.

Topics

#Google Cloud Databases#Database Selection#Global Scalability#Consistency Models

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DATABASE-ENGINEER Practice