An automotive enterprise is designing a high-availability roadside emergency telemetry ingestion platform on Google Cloud. The workload consists of lightweight, stateless HTTP telemetry pings from connected vehicles. The system requires high availability across multiple GCP regions with minimal operational management overhead. Additionally, the platform must establish secure hybrid connectivity to sync telemetry logs back to an on-premises datacenter at an aggregate bandwidth of . Which TWO architectural decisions should you make to satisfy these technical requirements? (Select TWO.)
- Deploy the stateless telemetry ingestion API on Cloud Run in multiple regions behind a Global External Application Load Balancer.Answer
- BProvision GKE Enterprise clusters across multiple regions with dedicated node pools to host the stateless HTTP ingestion microservices.
- Establish high-availability (HA) Cloud VPN tunnels between the on-premises datacenter and Google Cloud using dynamic routing with Cloud Router.Answer
- DProvision a 10 Gbps Dedicated Interconnect pair between the on-premises location and the nearest Google Cloud Colocation facility.
- EConfigure VPC Network Peering to transitively route on-premises telemetry data through a central transit VPC to backend workload VPCs.
Answer
The optimal architectural approach is to deploy the stateless HTTP API on Cloud Run in multiple regions behind a Global External Application Load Balancer, and establish high-availability (HA) Cloud VPN tunnels with Cloud Router for hybrid connectivity.
Deploying stateless microservices on Cloud Run across regions behind a Global External Application Load Balancer ensures multi-region high availability with zero server management. Pairing this with HA Cloud VPN provides cost-effective, SLA-backed hybrid connectivity capable of handling up to 3 Gbps per tunnel, perfectly matching the 1.2 Gbps requirements.
Step-by-Step Solution
Key Concept
Designing for High Availability and Technical Requirements