Question

Difficulty: MediumCreating Conceptual, Logical, and Physical Architectures

A digital publishing platform is transitioning from a conceptual cloud design to a physical architecture on Google Cloud. The logical architecture requires an event-driven ingestion endpoint for webhooks, a fully managed stateless processing tier to sanitize and transform JSON content, a standard regional relational database for content metadata, and a perimeter security mechanism to prevent data exfiltration to unauthorized external storage. Which physical GCP architecture accurately implements these logical requirements while minimizing operational overhead and unnecessary cost?

  1. Incorporate Cloud Pub/Sub for event ingestion, Cloud Run for stateless payload transformation, Cloud SQL for PostgreSQL for regional metadata storage, and VPC Service Controls to enclose the resources within a security perimeter.Answer
  2. B
    Incorporate Cloud Pub/Sub for event ingestion, a Google Kubernetes Engine (GKE) Autopilot cluster for stateless payload transformation, Cloud SQL for PostgreSQL for regional metadata storage, and VPC Service Controls to enclose the resources.
  3. C
    Incorporate Cloud Pub/Sub for event ingestion, Cloud Run for stateless payload transformation, a multi-region Cloud Spanner instance for metadata storage, and VPC Service Controls to enclose the resources.
  4. D
    Incorporate Cloud Pub/Sub for event ingestion, Cloud Run for stateless payload transformation, Cloud SQL for PostgreSQL for regional metadata storage, and restrictive IAM roles without VPC Service Controls.

Answer

The optimal physical architecture uses Cloud Pub/Sub for event ingestion, Cloud Run for serverless processing, Cloud SQL for regional relational storage, and VPC Service Controls for exfiltration protection.
The solution that combines Cloud Pub/Sub, Cloud Run, Cloud SQL, and VPC Service Controls correctly translates every logical architectural tier into its minimal, fully managed physical GCP equivalent while enforcing exfiltration boundaries.

Step-by-Step Solution

1
Analyze logical ingestion and processing requirements
Identify that simple stateless event processing maps best to Cloud Run to eliminate cluster management overhead.
Cloud Run scales automatically from zero for stateless transformation tasks without infrastructure configuration.
2
Evaluate data storage tier requirements
Map the standard regional relational requirement to Cloud SQL rather than Cloud Spanner.
Cloud SQL meets regional relational needs without the high cost and global scaling complexity of Cloud Spanner.
3
Evaluate security perimeter constraints
Select VPC Service Controls to establish exfiltration boundaries.
IAM permissions govern user authorization but cannot prevent authorized identities from copying data to external unmanaged storage buckets unless protected by a VPC Service Controls perimeter.

Key Concept

Translating Logical Architecture to Physical GCP Component Specifications
Rate this question