Question

Difficulty: HardCreating Conceptual, Logical, and Physical Architectures

An international maritime shipping logistics enterprise is designing a modern vessel telemetry and port operations platform on Google Cloud. The architecture team needs to map high-level business goals into conceptual, logical, and physical tiers. The system must ingest high-velocity IoT position and engine diagnostic telemetry from thousands of vessels globally, process stateless tracking pings with minimal infrastructure management overhead, and enforce strict data exfiltration defenses around sensitive manifest records stored in managed storage. Which TWO architectural decisions correctly map these requirements across logical and physical layers? (Select TWO.)

  1. Map the logical real-time telemetry ingestion and analytical storage tiers to Cloud Pub/Sub paired with Cloud Bigtable, using Cloud Run for stateless HTTP tracking pings.Answer
  2. Map the physical data perimeter security tier by configuring VPC Service Controls around Cloud Storage and Cloud Bigtable, restricting exfiltration pathways regardless of IAM authorization.Answer
  3. C
    Map the logical transactional storage tier for standard single-region port maintenance logs by provisioning Cloud Spanner to handle relational database needs.
  4. D
    Map the logical stateless processing tier to a dedicated GKE Autopilot cluster with a custom Istio service mesh to handle simple HTTP vessel position pings.
  5. E
    Map the physical access control tier by granting the primitive Owner role to the automated vessel ingestion service account to guarantee service access across GCP APIs.

Answer

The correct architecture maps real-time telemetry ingestion and high-velocity storage to Cloud Pub/Sub and Cloud Bigtable with Cloud Run for stateless processing, and secures sensitive storage resources using VPC Service Controls to prevent data exfiltration.
The correct architectural choices appropriately align logical functions with optimal physical GCP services: Pub/Sub and Bigtable handle high-velocity time-series ingestion and analytical storage, Cloud Run provides low-friction stateless compute, and VPC Service Controls establishes perimeter security around storage resources to mitigate data exfiltration risks.

Step-by-Step Solution

1
Analyze high-velocity IoT telemetry requirements at the logical and physical layers.
Cloud Pub/Sub handles decoupled high-throughput messaging, while Cloud Bigtable provides scalable low-latency storage for time-series telemetry. Serverless Cloud Run handles stateless HTTP pings efficiently without GKE cluster management overhead.
Matching workload patterns to managed cloud services minimizes operational toil and satisfies performance constraints.
2
Evaluate security constraints for protecting sensitive manifest data from exfiltration.
VPC Service Controls creates a logical/physical security perimeter around GCP storage APIs (Cloud Storage and Cloud Bigtable) to prevent data exfiltration beyond defined trust boundaries.
IAM authorization alone does not prevent authorized identities from writing data to external GCP resources outside the organization perimeter.

Key Concept

Mapping business requirements to conceptual, logical, and physical architecture tiers on Google Cloud Platform.
Estimated Time:2m 0s
Rate this question