A smart manufacturing enterprise is translating its functional solution requirements into a Google Cloud physical architecture. The solution requires real-time telemetry ingestion from IoT edge devices, stateless event-driven microservices to validate payload schemas, a regional relational database for transactional maintenance work order tracking, and isolation controls to prevent data exfiltration beyond IAM permissions. Which combination of GCP services and security controls fulfills these physical architecture requirements while minimizing operational overhead?
- Cloud Pub/Sub for ingestion, Cloud Run for event processing, Cloud SQL for PostgreSQL for work orders, and VPC Service Controls for exfiltration prevention.Cevap
- BCloud Pub/Sub for ingestion, Google Kubernetes Engine (GKE) clusters for event processing, Cloud SQL for PostgreSQL for work orders, and VPC Service Controls for exfiltration prevention.
- CCloud Pub/Sub for ingestion, Cloud Run for event processing, Cloud Spanner for work orders, and VPC Service Controls for exfiltration prevention.
- DCloud Pub/Sub for ingestion, Cloud Run for event processing, Cloud SQL for PostgreSQL for work orders, and fine-grained IAM roles without VPC Service Controls.
Cevap
The optimal architecture combines Cloud Pub/Sub for real-time telemetry ingestion, Cloud Run for fully managed stateless event processing, Cloud SQL for PostgreSQL for regional relational storage, and VPC Service Controls to prevent data exfiltration.
The combination of Cloud Pub/Sub, Cloud Run, Cloud SQL for PostgreSQL, and VPC Service Controls accurately maps each logical tier to its ideal physical service on GCP. It delivers serverless event processing, efficient regional relational storage, and robust perimeter security against exfiltration with minimal operational burden.
Adım Adım Çözüm
Anahtar Kavram
Mapping functional solution requirements across conceptual, logical, and physical architecture tiers on GCP.