A financial analytics firm processes daily transaction reconciliation jobs that run for only 3 hours every midnight, requiring high CPU for processing but zero compute capacity for the remaining 21 hours of the day. Additionally, their operational relational dataset is approximately in size with standard regional availability requirements. The company wants to minimize baseline compute and database costs while ensuring automated scaling and minimal management overhead. Which TWO architectural decisions should you recommend to meet these business requirements? (Select TWO.)
- Containerize the daily reconciliation workload and execute it using Cloud Run jobs triggered by Cloud Scheduler.Cevap
- Provision a Cloud SQL for PostgreSQL instance with automatic storage increase enabled to store the relational dataset.Cevap
- CDeploy a Google Kubernetes Engine (GKE) Autopilot cluster with a fixed minimum pool of 10 nodes to handle batch execution readiness.
- DMigrate the relational database to a multi-region Cloud Spanner instance to ensure maximum availability and seamless scale.
- EPurchase a 3-year Committed Use Discount (CUD) for Compute Engine instances dedicated to running the midnight batch script.
Cevap
The organization should containerize the batch workload using Cloud Run jobs triggered by Cloud Scheduler, and host the regional relational database on Cloud SQL.
The solution minimizes operational costs by aligning compute usage strictly with execution time using serverless Cloud Run jobs (which incur zero charges when idle) and right-sizing the relational database using Cloud SQL, which meets regional storage needs efficiently without the node overhead of Cloud Spanner.
Adım Adım Çözüm
Anahtar Kavram
Selecting serverless compute for bursty/scheduled batch jobs and cost-effective regional relational storage for moderate data volumes.
Tahmini Süre:1m 30s