A global pharmaceutical firm is designing a clinical trial telemetry platform on Google Cloud. The conceptual architecture defines three functional tiers: a message buffer for regional event ingestion from medical devices, a managed compute layer for stateless transformation that scales to zero during off-peak hours, and a network security boundary preventing data exfiltration to unauthorized external cloud locations. Which combination of Google Cloud physical services correctly maps to these conceptual architectural layers while satisfying all operational and security constraints?
- Cloud Pub/Sub for regional event ingestion, Cloud Run for stateless serverless transformation, and VPC Service Controls to define a security perimeter around storage and compute resources.Answer
- BCloud Pub/Sub for regional event ingestion, Google Kubernetes Engine (GKE) with standard clusters for stateless serverless transformation, and VPC Service Controls to define a security perimeter.
- CCloud Pub/Sub for regional event ingestion, Cloud Run for stateless serverless transformation, and fine-grained IAM roles without VPC Service Controls to enforce exfiltration security boundaries.
- DCloud Spanner for regional event ingestion buffering, Cloud Run for stateless serverless transformation, and VPC Service Controls to define a security perimeter.
Answer
The architectural requirements are best met by pairing Cloud Pub/Sub for regional event ingestion, Cloud Run for stateless scale-to-zero compute, and VPC Service Controls to establish a perimeter preventing data exfiltration.
The correct architecture translates conceptual messaging, compute, and security requirements into Cloud Pub/Sub for event ingestion, Cloud Run for scale-to-zero stateless processing, and VPC Service Controls for strict perimeter security against data exfiltration.
Step-by-Step Solution
Key Concept
Mapping conceptual business requirements (buffering, scale-to-zero compute, exfiltration prevention) to concrete logical and physical GCP services (Pub/Sub, Cloud Run, VPC Service Controls).
Estimated Time:1m 30s