Soru

Zorluk: OrtaDesigning Infrastructure for Business Requirements and Cost Optimization

A global maritime fleet management enterprise is building an infrastructure on Google Cloud to collect position updates and engine metrics from thousands of cargo vessels worldwide. The position ingestion service is a lightweight stateless HTTP microservice experiencing erratic traffic spikes followed by periods of complete inactivity. Additionally, historical vessel route records must be preserved for 7 years to comply with maritime regulations, but these records are rarely queried after the first 30 days. The primary business requirement is to minimize operational management overhead and infrastructure cost while ensuring high availability. Which TWO architectural decisions should the enterprise implement? (Select TWO.)

  1. Deploy the stateless position ingestion HTTP microservice to Cloud Run.Cevap
  2. B
    Deploy the position ingestion microservice to a multi-zone Google Kubernetes Engine (GKE) Standard cluster with cluster autoscaling enabled.
  3. Store historical vessel route records in Cloud Storage and configure Object Lifecycle Management to transition objects to Coldline or Archive storage after 30 days.Cevap
  4. D
    Store historical vessel route records in a multi-region Cloud Spanner instance to ensure global consistency for long-term historical reporting.

Cevap

The enterprise should deploy the position ingestion microservice to Cloud Run and store historical vessel route records in Cloud Storage with Object Lifecycle Management configured to transition objects to Coldline or Archive storage after 30 days.
Deploying to Cloud Run aligns with the business goal of cost optimization because serverless containers automatically scale down to zero compute instances during idle periods, eliminating baseline infrastructure charges. For storage, utilizing Cloud Storage with Object Lifecycle Management allows automated migration of vessel logs to cheaper Coldline or Archive tiers after 30 days, satisfying compliance requirements at minimal cost.

Adım Adım Çözüm

1
Analyze compute requirements and traffic patterns for the position ingestion microservice.
Identified erratic traffic with periods of complete inactivity for a stateless microservice.
Cloud Run scales to zero instances during idle periods, charging only for resources consumed during request processing, which minimizes compute cost and management effort.
2
Analyze storage access patterns and retention compliance rules.
Identified high initial access for 30 days followed by 7 years of low-frequency retention.
Cloud Storage with Object Lifecycle Management transitions data from Standard to Coldline/Archive storage after 30 days, optimizing storage costs while keeping data accessible for compliance.

Anahtar Kavram

Designing Serverless Compute and Tiered Storage Lifecycles for Cost Optimization
Tahmini Süre:1m 30s
Bu soruyu puanla