An architectural team at a global financial settlement firm is translating a multi-tier conceptual architecture into concrete logical and physical designs on Google Cloud. The logical tier mandates two key requirements: first, a core relational transaction ledger that guarantees active-active multi-region ACID consistency with low write latency; second, strict network-level security perimeters between the transaction engine and third-party audit reporting components to block unauthorized data exfiltration even if IAM credentials are leaked. Which physical architecture implementation correctly maps these logical requirements to Google Cloud services?
- Provision Cloud Spanner with a multi-region instance configuration for the relational transaction ledger, and isolate the transaction processing and audit reporting projects into separate security perimeters using VPC Service Controls.Cevap
- BProvision Cloud SQL for PostgreSQL with cross-region read replicas for the relational transaction ledger, and restrict communication between project environments using IAM primitive Editor roles.
- CProvision Cloud Spanner with a multi-region instance configuration for the transaction ledger, and rely exclusively on IAM Service Account User role bindings without configuring VPC Service Controls perimeters.
- DProvision an Autopilot GKE Enterprise cluster to host stateless event ingestion webhooks, while deploying Cloud SQL for global multi-region transactional consistency and Cloud Spanner for long-term audit logging.
Cevap
Provision Cloud Spanner with a multi-region instance configuration for the relational transaction ledger, and isolate the transaction processing and audit reporting projects into separate security perimeters using VPC Service Controls.
The correct solution maps the logical requirements to physical GCP components by choosing Cloud Spanner for multi-region active-active relational consistency and VPC Service Controls to enforce perimeter-based network protection against data exfiltration.
Adım Adım Çözüm
Anahtar Kavram
Translating logical data storage and security requirements into GCP physical services (Cloud Spanner and VPC Service Controls)