An international agricultural technology company is defining the architectural components for an enterprise smart-farming telemetry platform on Google Cloud. The conceptual design requires decoupling high-throughput sensor data streams from downstream analytics services while establishing a strict security boundary to protect proprietary farm yield data against unauthorized exfiltration. When translating these conceptual and logical requirements into a physical architecture on Google Cloud, which TWO architectural decisions should the cloud architect implement? (Select TWO options.)
- Provision Cloud Pub/Sub topics as the physical messaging middleware to asynchronously ingest telemetry streams before triggering Dataflow processing jobs.Answer
- Configure VPC Service Controls around BigQuery and Cloud Storage resource boundaries to prevent authorized users from exfiltrating data to external GCP projects.Answer
- CDeploy a multi-region Cloud Spanner cluster to store standard operational relational metadata that is accessed primarily within a single geographic region.
- DProvision a Google Kubernetes Engine (GKE) Autopilot cluster to run lightweight, stateless HTTP API proxy endpoints.
- ERely exclusively on fine-grained IAM roles to prevent internal users with valid credentials from exporting dataset objects to public Cloud Storage buckets.
Answer
The optimal physical architecture requires provisioning Cloud Pub/Sub as the asynchronous messaging ingestion layer and establishing VPC Service Controls around storage and analytics services to enforce security boundaries.
The correct choices properly translate high-level conceptual requirements into concrete physical GCP services. Cloud Pub/Sub satisfies the logical decoupling requirement for high-throughput stream ingestion. VPC Service Controls satisfy the physical security requirement by preventing data exfiltration across resource perimeters.
Step-by-Step Solution
Key Concept
Mapping Conceptual and Logical Cloud Architectures to Physical GCP Resources