An online gaming studio is defining the cloud architecture for a global multiplayer leaderboard and user session state service. The conceptual architecture specifies three functional tiers: 1) a high-throughput event ingestion tier for real-time match telemetry, 2) a stateless microservices container execution tier for game session management, and 3) a relational database tier for persistent player profiles restricted to a single geographic region. Additionally, security governance requires network-level data exfiltration prevention around cloud storage endpoints holding game assets. Which combination of Google Cloud services correctly maps this logical design to a physical GCP architecture while adhering to operational cost and security best practices?
- Use Cloud Pub/Sub for telemetry ingestion, Cloud Run for microservices execution, Cloud SQL for PostgreSQL for relational player profiles, and VPC Service Controls around storage resources.Cevap
- BUse Cloud Pub/Sub for telemetry ingestion, a dedicated Google Kubernetes Engine (GKE) Standard cluster for microservices execution, Cloud SQL for PostgreSQL for relational player profiles, and VPC Service Controls around storage resources.
- CUse Cloud Pub/Sub for telemetry ingestion, Cloud Run for microservices execution, Cloud Spanner for relational player profiles, and VPC Service Controls around storage resources.
- DUse Cloud Pub/Sub for telemetry ingestion, Cloud Run for microservices execution, Cloud SQL for PostgreSQL for relational player profiles, and IAM role bindings alone without VPC Service Controls.