Question

Difficulty: Very hardCreating Conceptual, Logical, and Physical Architectures

An enterprise organization is designing a multi-tier e-commerce system on Google Cloud and translating conceptual business requirements into logical and physical architecture components.

The conceptual architecture specifies four primary requirements:
1. A stateless HTTP API ingress layer to accept lightweight order payloads with minimal operational management overhead.
2. A relational data tier storing order transactions restricted strictly to a single GCP region with cost-effective, standard relational database capacity.
3. A hybrid network topology capable of delivering 10 Gbps predictable, low-latency bandwidth between on-premises systems and GCP VPCs.
4. A data security boundary that prevents authorized internal users from exfiltrating sensitive storage data to external, unauthorized Google Cloud projects.

Which TWO physical architecture decisions correctly implement these requirements while avoiding architectural anti-patterns? (Select TWO)

  1. Deploy Cloud Run for the stateless HTTP API ingress tier, and implement Cloud SQL for the regional transactional relational database tier.Answer
  2. Establish a Dedicated Interconnect connection for hybrid connectivity, and configure VPC Service Controls perimeters around Google Cloud Storage resources.Answer
  3. C
    Provision an Autopilot Google Kubernetes Engine (GKE) cluster to host the stateless HTTP API ingress services.
  4. D
    Deploy a multi-region Cloud Spanner instance to host the single-region transactional order database.
  5. E
    Deploy High Availability (HA) VPN tunnels with dynamic Cloud Router routing to fulfill the 10 Gbps hybrid network throughput requirement.

Answer

The correct physical architecture choices are deploying Cloud Run for stateless HTTP APIs paired with Cloud SQL for regional relational data, and establishing Dedicated Interconnect for 10 Gbps connectivity alongside VPC Service Controls for exfiltration prevention.
Translating conceptual requirements to physical GCP components requires choosing the optimal service for operational efficiency, network throughput, and security. Cloud Run efficiently handles stateless HTTP APIs without cluster maintenance, while Cloud SQL provides cost-effective regional relational data storage. Dedicated Interconnect provides the physical 10 Gbps bandwidth needed for high-throughput hybrid networking, and VPC Service Controls defines security boundaries that prevent data exfiltration even if IAM privileges are compromised.

Step-by-Step Solution

1
Analyze Compute Ingress and Relational Storage Requirements
Cloud Run satisfies stateless HTTP ingestion with zero server management. Cloud SQL satisfies single-region relational ACID requirements without unnecessary global Spanner overhead.
Matching conceptual tier requirements to the correct physical GCP product prevents over-provisioning and excessive operational costs.
2
Evaluate Network and Security Requirements
Dedicated Interconnect delivers physical 10 Gbps pipeline capacity (beyond HA VPN tunnel limits), while VPC Service Controls establishes network perimeters around Cloud Storage to block data exfiltration.
HA VPN cannot support 10 Gbps per tunnel, and IAM permissions alone cannot prevent data exfiltration to external GCP resources.

Key Concept

Translating Logical to Physical Architectures in GCP
Rate this question