Examkin

Soru

Zorluk: ZorDesigning Infrastructure for Technical Requirements and High Availability

An enterprise media streaming provider is architecting its core backend services on Google Cloud for global live broadcast events. The system must meet the following technical requirements:
- Achieve a 99.99%99.99\% multi-region availability SLA for stateless subscriber entitlement validation requests.
- Ensure zero Recovery Point Objective (RPO) and synchronous multi-region consistency for transactional subscriber entitlement writes during a regional outage.
- Prevent authorized internal identity principals from exfiltrating database content to external Google Cloud projects.
- Minimize operational management overhead for the stateless API compute tier.

Which TWO architectural components should you combine to fulfill these requirements? (Select TWO)

  1. Deploy the stateless entitlement validation API on Cloud Run across multiple regions behind a Global External Application Load Balancer.Cevap
  2. B
    Provision dedicated Google Kubernetes Engine (GKE) clusters in multiple regions with custom ingress controllers to host the stateless entitlement validation API.
  3. Store subscriber entitlement records in a Multi-Region Cloud Spanner instance and enclose the database service inside a VPC Service Controls security perimeter.Cevap
  4. D
    Store subscriber entitlement records in a High Availability (HA) Regional Cloud SQL for PostgreSQL instance with cross-region read replicas.
  5. E
    Rely exclusively on fine-grained IAM roles (`roles/spanner.databaseUser`) to restrict database permissions and prevent data exfiltration.

Cevap

The optimal architecture combines deploying the stateless API on Cloud Run across multiple regions behind a Global External Application Load Balancer, and storing transactional database records in a Multi-Region Cloud Spanner instance protected by a VPC Service Controls perimeter.
The combination of Cloud Run behind a Global External Application Load Balancer and Multi-Region Cloud Spanner with VPC Service Controls satisfies all functional constraints. Cloud Run handles stateless API requests across regions with minimal operational effort. Multi-Region Cloud Spanner uses synchronous Paxos replication to deliver zero RPO across regional outages. VPC Service Controls establishes a perimeter boundary that prevents authorized identities from transferring sensitive database content to external, unapproved Google Cloud projects.

Adım Adım Çözüm

1
Analyze the stateless API compute tier requirements.
Cloud Run combined with a Global External Application Load Balancer delivers serverless regional failover, sub-second global latency routing, and 99.99%99.99\% availability without cluster maintenance overhead.
Serverless containers fulfill the low operational overhead mandate while the global load balancer provides automatic multi-region failover.
2
Analyze the database tier availability and data loss constraints.
Multi-Region Cloud Spanner provides synchronous global replication using Paxos consensus, guaranteeing transactional integrity and zero RPO even during regional outages.
Regional databases such as Cloud SQL use asynchronous cross-region replication, which exposes writes to data loss during regional disaster events.
3
Evaluate the data exfiltration prevention requirement.
Enclosing the database within a VPC Service Controls perimeter blocks egress data transfers to external, non-authorized Google Cloud resources.
IAM authorization checks user identity but does not enforce network/resource context boundaries required to stop data exfiltration.

Anahtar Kavram

Designing multi-region high availability architectures combining serverless compute, globally consistent database storage with zero RPO, and VPC Service Controls security perimeters.
Bu soruyu puanla

Konular

Designing Infrastructure for Technical Requirements and High Availability