Examkin

Question

Difficulty: HardDesigning Infrastructure for Business Requirements and Cost Optimization

A financial analytics firm is migrating its transactional relational database to Google Cloud. The workload requires strict ACID compliance, relational SQL join support, and multi-zone High Availability within a single GCP region (`us-central1`). Peak operational throughput is estimated at 2,5002,500 write transactions per second. The primary business requirement is to minimize operational management overhead and infrastructure costs while maintaining regional resilience. Which architecture best satisfies these technical and cost-optimization requirements?

  1. Provision Cloud SQL for PostgreSQL configured with regional High Availability (HA) across two zones, utilizing Cloud Storage Object Lifecycle Management to archive inactive historical audit data.Answer
  2. B
    Provision a multi-zone Cloud Spanner instance configured for high-throughput relational processing across all regional zones.
  3. C
    Deploy a multi-zone Google Kubernetes Engine (GKE) cluster running self-managed PostgreSQL container pods with StatefulSets on Regional Persistent Disks.
  4. D
    Provision a Compute Engine virtual machine instance running PostgreSQL and assign primitive Owner IAM roles to the database application service account to simplify resource permissions.

Answer

Provisioning Cloud SQL for PostgreSQL with regional High Availability (HA) and offloading inactive historical records to Cloud Storage using lifecycle policies provides the optimal balance of managed relational performance, automated failover, and minimal cost.
Cloud SQL for PostgreSQL with regional HA provides automated multi-zone failover, full relational compatibility, and sufficient IOPS performance for 2,5002,500 write ops/sec. Combined with Cloud Storage lifecycle rules for historical data, it fulfills all technical requirements at minimal cost and administrative effort.

Step-by-Step Solution

1
Evaluate workload database requirements
Workload requires relational SQL, strong ACID guarantees, and max 2,5002,500 writes/sec within a single region (`us-central1`).
Determines whether standard relational databases (Cloud SQL) or horizontally scaled global databases (Cloud Spanner) are needed.
2
Compare managed database platform costs and operational overhead
Cloud SQL for PostgreSQL easily supports up to 2,5002,500 writes/sec in a single region with automated regional failover at a fraction of Cloud Spanner's cost.
Selecting Cloud SQL minimizes infrastructure cost while fulfilling all SLA and functional demands.
3
Select data archiving strategy for cost optimization
Exporting inactive historical audit logs to Cloud Storage Nearline/Coldline with Object Lifecycle Management reduces primary database storage usage.
Optimizes ongoing storage expenditure by leveraging cheaper object storage tiers for cold data.

Key Concept

Cloud Database Selection and Cost Right-Sizing
Estimated Time:2m 0s
Rate this question

Topics

Designing Infrastructure for Business Requirements and Cost Optimization