Examkin

Soru

Zorluk: OrtaSelecting and Designing Storage and Database Resources

A global pharmaceutical company is architecting a data storage solution on Google Cloud for a regional clinical trial inventory tracking application. The relational database will host a 400 GB dataset located entirely within a single GCP region (`us-central1`) to satisfy strict data residency requirements. The workload experiences standard OLTP transactional traffic with predictable growth unlikely to exceed 2 TB over the next three years. The database must automatically fail over to a secondary zone during a zonal outage, and security compliance mandates that encryption keys must be generated and rotated by the enterprise security team using Google Cloud KMS. Which database architecture best satisfies these technical and compliance requirements while avoiding unnecessary cost and complexity?

  1. A
    Deploy a multi-region Cloud Spanner instance configured with Customer-Supplied Encryption Keys (CSEK).
  2. Deploy a Cloud SQL for PostgreSQL regional instance configured for High Availability (HA) across two zones, integrated with Customer-Managed Encryption Keys (CMEK) via Cloud KMS.Cevap
  3. C
    Deploy a Cloud SQL for PostgreSQL regional instance configured for High Availability (HA), utilizing Customer-Supplied Encryption Keys (CSEK) supplied during instance creation.
  4. D
    Export operational updates daily into Cloud Storage and transfer them using a Transfer Appliance to maintain synchronous regional relational consistency.

Cevap

Deploy a Cloud SQL for PostgreSQL regional instance configured for High Availability (HA) across two zones, integrated with Customer-Managed Encryption Keys (CMEK) via Cloud KMS.
The correct architecture uses Cloud SQL for PostgreSQL configured for High Availability (HA) with Customer-Managed Encryption Keys (CMEK). Cloud SQL supports relational datasets up to 64 TB within a single region and provides automatic cross-zone failover via synchronous replication to a standby instance. Integrating with Cloud KMS via CMEK allows enterprise security teams to retain authority over key generation, rotation, and lifecycle management.

Adım Adım Çözüm

1
Evaluate workload scale and regional data residency constraints.
The dataset is 400 GB located in a single region with predictable moderate growth (< 2 TB), making Cloud SQL standard relational instances the optimal choice over horizontally scalable global solutions like Cloud Spanner.
Cloud SQL handles relational database sizes up to 64 TB within a single region cost-effectively without multi-region sharding overhead.
2
Assess high availability requirements for zonal resilience.
Configuring Cloud SQL in High Availability (HA) mode provisions a primary instance in one zone and a standby instance in a second zone within the same region with synchronous replication.
Zonal failover is handled automatically by Cloud SQL HA in the event of an outage in the primary zone.
3
Verify security and key management requirements.
Customer-Managed Encryption Keys (CMEK) using Cloud KMS allow internal security teams to retain key control and manage rotation policies for Cloud SQL data at rest.
Cloud SQL supports CMEK via Cloud KMS, whereas Customer-Supplied Encryption Keys (CSEK) are not supported on Cloud SQL database instances.

Anahtar Kavram

Selecting Cloud SQL for regional relational workloads under multi-terabyte scale with High Availability and CMEK key compliance.
Bu soruyu puanla

Konular

Selecting and Designing Storage and Database Resources