Examkin

Question

Difficulty: MediumCreating Conceptual, Logical, and Physical Architectures

A municipal water management agency is designing a regional flood monitoring and telemetry system on Google Cloud. The conceptual design requires ingesting real-time sensor streams from 50,000 IoT devices, executing low-latency alerting pipeline logic, storing operational metadata in a regional relational database with standard SQL requirements, and enforcing strict perimeter security against data exfiltration. Which combination of Google Cloud physical services and security boundaries correctly translates these conceptual requirements into a logical and physical architecture without over-provisioning infrastructure?

  1. Ingest telemetry via Cloud Pub/Sub, process streams using Cloud Dataflow, store relational metadata in Cloud SQL, and establish a security perimeter using VPC Service Controls.Answer
  2. B
    Ingest telemetry via Cloud Pub/Sub, process streams using Cloud Dataflow, store relational metadata in Cloud Spanner, and establish a security perimeter using VPC Service Controls.
  3. C
    Ingest telemetry using custom container consumers on a GKE cluster, process streams using Cloud Dataflow, store relational metadata in Cloud SQL, and grant IAM Owner roles to operational service accounts.
  4. D
    Ingest telemetry via Cloud Pub/Sub, process streams using Cloud Dataflow, store relational metadata in Cloud SQL, and rely exclusively on granular IAM permissions without defining VPC Service Controls.

Answer

Ingest telemetry via Cloud Pub/Sub, process streams using Cloud Dataflow, store relational metadata in Cloud SQL, and establish a security perimeter using VPC Service Controls.
The correct solution maps each conceptual tier to its ideal physical service: Cloud Pub/Sub handles high-throughput ingestion, Cloud Dataflow processes real-time telemetry, Cloud SQL provides regional relational storage without Spanner's global cost overhead, and VPC Service Controls enforce perimeter defense against data exfiltration.

Step-by-Step Solution

1
Map conceptual ingestion and stream processing requirements to GCP services.
Cloud Pub/Sub handles high-throughput asynchronous message ingestion, while Cloud Dataflow executes low-latency stream processing.
Serverless managed services provide native scaling without infrastructure maintenance.
2
Select appropriate relational database tier based on regional SQL requirements.
Cloud SQL fits regional relational SQL storage needs optimally.
Cloud Spanner is designed for globally distributed relational workloads requiring multi-region synchronous writes and would be an over-provisioned architecture choice.
3
Identify perimeter security controls for exfiltration prevention.
VPC Service Controls form a security perimeter around GCP service APIs.
IAM controls identity access, but VPC Service Controls are required to restrict network-level data transfers and prevent data exfiltration.

Key Concept

Translating Conceptual Business Requirements to GCP Physical Architecture Components
Estimated Time:1m 30s
Rate this question

Topics

Creating Conceptual, Logical, and Physical Architectures