Soru

Zorluk: OrtaSelecting and Designing Storage and Database Resources

A healthcare organization operating in a single Google Cloud region needs to deploy a relational database layer for its patient billing application. The system requires full ACID transactional support, standard ANSI SQL capability, automatic regional high availability failover, and data encryption using customer-managed encryption keys (CMEK) integrated with Cloud KMS. The database dataset size is expected to remain around 400 GB with moderate query volume. The architectural team wants to optimize operational efficiency and minimize cost. Which storage and database design best satisfies these business and technical requirements?

  1. Deploy Cloud SQL for PostgreSQL configured with High Availability (regional failover) and encrypted with Customer-Managed Encryption Keys (CMEK) via Cloud KMS.Cevap
  2. B
    Deploy Cloud Spanner with a regional instance configuration using Google-managed encryption keys.
  3. C
    Deploy Cloud SQL for PostgreSQL with High Availability using Customer-Supplied Encryption Keys (CSEK) supplied at query runtime.
  4. D
    Deploy a Cloud Storage dual-region bucket using VPC Service Controls to host application data files and prevent exfiltration.

Cevap

Deploy Cloud SQL for PostgreSQL configured with High Availability (regional failover) and Customer-Managed Encryption Keys (CMEK) via Cloud KMS.
The correct solution uses Cloud SQL for PostgreSQL configured with High Availability (HA) and Customer-Managed Encryption Keys (CMEK). Cloud SQL supports standard ANSI SQL and ACID transactions for single-region relational workloads up to 64 TB. Configuring HA provides regional zero-data-loss synchronous replication across zones with automatic failover, and Cloud KMS integration provides CMEK encryption compliance.

Adım Adım Çözüm

1
Evaluate workload data model and scale requirements
The application requires an ACID-compliant relational database with standard ANSI SQL support for a 400 GB single-region dataset.
Cloud SQL easily scales up to tens of terabytes in a single region, making it appropriate for 400 GB without needing globally distributed databases like Cloud Spanner.
2
Evaluate availability and security governance constraints
Regional HA and Cloud KMS CMEK integration must be enabled.
Cloud SQL supports automated regional failover across primary and standby zones and natively integrates with Cloud KMS for customer-managed key encryption.
3
Select the optimal database architecture
Cloud SQL for PostgreSQL with HA and CMEK satisfies all technical requirements while remaining cost-effective.
This combination fulfills compliance and availability requirements without incurring the management and cost overhead of Spanner or improper storage services.

Anahtar Kavram

Relational Database Selection (Cloud SQL vs. Cloud Spanner) and Security Governance
Bu soruyu puanla