A global smart logistics enterprise tracks 500,000 delivery vehicles worldwide. Telemetry data is ingested via an HTTP endpoint that experiences severe traffic bursts during peak morning fleet dispatches but remains virtually idle overnight. The company needs to optimize its Google Cloud architecture to minimize Total Cost of Ownership (TCO) by eliminating idle compute infrastructure costs. Additionally, they must retain raw telemetry logs (over 1 TB per day) for 5 years to meet regulatory compliance requirements at the lowest possible storage cost. Which TWO architectural recommendations should you make to satisfy both business and cost optimization objectives?
- Deploy the stateless HTTP telemetry ingestion endpoint on Cloud Run to enable automatic scaling down to zero instances during idle off-peak hours.Cevap
- Configure an Object Lifecycle Management rule on the Cloud Storage bucket to transition raw telemetry objects to Archive Storage after 30 days.Cevap
- CProvision a Google Kubernetes Engine (GKE) Autopilot cluster running continuous minimal worker nodes to host the HTTP ingestion microservice.
- DStore historical raw telemetry audit logs in Cloud Spanner to guarantee global ACID compliance and low-latency access for compliance reporting.
Cevap
Deploying the HTTP telemetry endpoint on Cloud Run and setting an Object Lifecycle Management policy to transition raw data to Cloud Storage Archive class.
The combination of Cloud Run for stateless HTTP ingestion and Cloud Storage Archive class for long-term log retention directly addresses both business requirements. Cloud Run automatically scales to zero instances when traffic drops overnight, ensuring the enterprise pays strictly per request execution time and incurs zero compute cost during idle periods. Transitioning raw telemetry logs to Cloud Storage Archive tier via Lifecycle Management provides the lowest cost storage option for high-volume, multi-year compliance archiving with low retrieval frequency.
Adım Adım Çözüm
Anahtar Kavram
Serverless scale-to-zero compute paired with automated object storage tiering for TCO optimization.