Examkin

Question

Difficulty: MediumCreating Conceptual, Logical, and Physical Architectures

A global telehealth provider is translating its conceptual architectural design for an emergency vitals monitoring platform into a physical Google Cloud architecture. The logical design specifies three core requirements: real-time streaming ingestion of wearable device vitals, zero-infrastructure serverless microservices for data processing to minimize operational overhead, and a security perimeter preventing authorized users from copying Patient Health Information (PHI) to external Google Cloud projects. Which combination of Google Cloud services correctly maps to this physical architecture?

  1. Cloud Pub/Sub for streaming ingestion, Cloud Run for serverless microservices, Cloud Bigtable for time-series vitals storage, and VPC Service Controls for perimeter security.Answer
  2. B
    Cloud Pub/Sub for streaming ingestion, Google Kubernetes Engine (GKE) Standard clusters for containerized microservices, Cloud Bigtable for time-series vitals storage, and VPC Service Controls for perimeter security.
  3. C
    Cloud Pub/Sub for streaming ingestion, Cloud Run for serverless microservices, Cloud Spanner as the primary database for localized time-series vitals storage, and VPC Service Controls for perimeter security.
  4. D
    Cloud Pub/Sub for streaming ingestion, Cloud Run for serverless microservices, Cloud Bigtable for time-series vitals storage, and IAM fine-grained roles alone for data security.

Answer

Cloud Pub/Sub for streaming ingestion, Cloud Run for serverless microservices, Cloud Bigtable for time-series vitals storage, and VPC Service Controls for perimeter security.
The correct physical architecture maps conceptual streaming ingestion to Cloud Pub/Sub, serverless compute with zero cluster management to Cloud Run, high-throughput time-series metrics storage to Cloud Bigtable, and perimeter data exfiltration protection to VPC Service Controls.

Step-by-Step Solution

1
Map ingestion tier requirement to physical GCP service
Cloud Pub/Sub is selected for decoupled, real-time streaming ingestion of wearable device vitals with dynamic scaling.
Conceptual streaming telemetry requires high-throughput message ingestion without server management.
2
Map compute tier requirement to physical GCP service
Cloud Run is selected for stateless container execution without infrastructure management overhead.
The requirement specifies zero-infrastructure serverless microservices, making Cloud Run optimal over GKE.
3
Map storage tier and security perimeter requirements to physical GCP services
Cloud Bigtable is selected for scalable time-series telemetry storage, and VPC Service Controls is selected for perimeter security.
Cloud Bigtable handles high-write time-series data cost-effectively (unlike Cloud Spanner), while VPC Service Controls prevents data exfiltration that IAM alone cannot block.

Key Concept

Mapping conceptual architectural layers (ingestion, compute, storage, security) to physical GCP services based on operational, scale, and compliance constraints.
Rate this question

Topics

Creating Conceptual, Logical, and Physical Architectures