Question

Difficulty: HardSelecting and Designing Storage and Database Resources

An enterprise digital publishing company is migrating its subscription management and billing database from an on-premises PostgreSQL instance to Google Cloud. The workload operates exclusively within a single GCP region (us-east4) and requires full ANSI SQL compliance, multi-zone high availability with automatic failover, and strict transactional ACID guarantees. Peak write throughput is estimated at 1,800 operations per second. Additionally, compliance policy mandates that data at rest must be encrypted using customer-managed encryption keys integrated with Cloud KMS for automated key rotation. Which storage and database architecture should the lead cloud architect select?

  1. Deploy Cloud SQL for PostgreSQL in a high-availability configuration across two zones in us-east4, configured with Customer-Managed Encryption Keys (CMEK) via Cloud KMS.Answer
  2. B
    Provision a multi-region Cloud Spanner instance across North American regions to ensure multi-zone high availability and transactional ACID compliance for the billing database.
  3. C
    Deploy Cloud SQL for PostgreSQL in a high-availability configuration using Customer-Supplied Encryption Keys (CSEK) passed per API call to satisfy governance key management requirements.
  4. D
    Configure a Cloud Bigtable cluster with multi-cluster routing in us-east4 and use Cloud Storage Transfer Appliance to maintain real-time ACID billing transaction sync.

Answer

Deploy Cloud SQL for PostgreSQL in a high-availability configuration across two zones in us-east4, configured with Customer-Managed Encryption Keys (CMEK) via Cloud KMS.
Deploying Cloud SQL for PostgreSQL in a regional high-availability configuration satisfies all transactional (ACID), regional availability, performance (1,800 writes/sec), and key management requirements. Cloud SQL supports multi-zone failover within a single region and integrates directly with Cloud KMS to encrypt database disks at rest using Customer-Managed Encryption Keys (CMEK).

Step-by-Step Solution

1
Analyze workload relational and transactional requirements.
The workload requires standard ANSI SQL relational schemas and strict ACID transactional guarantees within a single region at 1,800 writes/sec.
Cloud SQL for PostgreSQL fully supports single-region relational workloads up to tens of thousands of IOPS without requiring horizontally scaled global databases.
2
Evaluate high availability and multi-zone requirements.
Cloud SQL HA configuration provides regional multi-zone redundancy with automatic failover between primary and standby instances in us-east4.
This satisfies the multi-zone HA requirement without needing multi-region replication.
3
Evaluate key management governance requirements.
Customer-Managed Encryption Keys (CMEK) using Cloud KMS allow centralized key management, access auditing, and automated rotation.
CSEK is unnecessary and burdensome, while CMEK satisfies Cloud KMS governance policies seamlessly.

Key Concept

Selecting and Designing Storage and Database Resources
Estimated Time:2m 0s
Rate this question