A DevOps team is preparing a budget model in the Google Cloud Pricing Calculator for a containerized event-processing application running on Cloud Run, backed by Cloud Storage for long-term log archiving. The application runs processing tasks on an event-driven basis with variable execution durations and outputs non-frequent access logs directly to storage. Which of the following parameters must be explicitly configured in the Google Cloud Pricing Calculator to ensure an accurate monthly cost estimate for these services? (Select TWO)
- The average request duration, allocated vCPU/memory per instance, and total monthly request count for the serverless container execution.Cevap
- The expected monthly data storage volume along with estimated retrieval fees and data access operations for the selected Cloud Storage tier.Cevap
- CA 1-year or 3-year Committed Use Discount (CUD) applied directly to the serverless container memory allocations.
- DThe underlying Kubernetes master control plane management fee and worker node instance pool machine types.
Cevap
Accurately estimating costs for Cloud Run and Cloud Storage in the Pricing Calculator requires configuring Cloud Run execution metrics (vCPU, memory, request duration, and request counts) and Cloud Storage operational costs (storage volume, operation counts, and retrieval fees).
Cloud Run pricing in the Google Cloud Pricing Calculator is modeled on container invocation metrics including request duration, CPU/memory allocations, and request volume. Cloud Storage pricing models require capacity, data retrieval amounts, and operation counts (Class A/B) to accurately project total monthly charges.
Adım Adım Çözüm
Anahtar Kavram
Configuring multi-service serverless and storage estimates in the GCP Pricing Calculator