An enterprise energy grid operator is designing a smart meter telemetry and analytics platform on Google Cloud. The conceptual architecture defines three main tiers: a real-time ingestion tier for 10 million smart meters, a streaming processing tier for time-series anomaly detection, and a secure storage tier for time-series analytics that prevents data exfiltration. Which TWO physical Google Cloud service and security configuration choices correctly translate these logical requirements into an optimal physical architecture? (Select TWO)
- Provision Cloud Pub/Sub for high-throughput event ingestion, Cloud Dataflow for stream processing, and Cloud Bigtable for scalable time-series data storage.Answer
- Configure VPC Service Controls perimeter encompassing the project resources to isolate managed storage and compute services from unauthorized data exfiltration.Answer
- CDeploy Cloud Spanner as the primary raw telemetry database to handle high write volume and relational joins across multiple geographic regions.
- DRely strictly on fine-grained IAM service account roles without network perimeter security to enforce data exfiltration boundaries.
- EDeploy a dedicated GKE cluster running custom Apache Flink pods for micro-batch telemetry processing to reduce operational complexity.
Answer
The optimal physical architecture pairs Cloud Pub/Sub, Cloud Dataflow, and Cloud Bigtable for high-scale time-series telemetry ingestion, processing, and storage, while leveraging VPC Service Controls to prevent data exfiltration beyond the security perimeter.
Combining Cloud Pub/Sub, Cloud Dataflow, and Cloud Bigtable maps the logical streaming architecture directly to GCP native services optimized for heavy time-series workloads. Adding VPC Service Controls establishes an effective physical boundary against data exfiltration across managed services.
Step-by-Step Solution
Key Concept
Translating Conceptual Telemetry and Security Requirements to GCP Managed Physical Resources