An enterprise architecture team is designing a cost estimation model in the Google Cloud Pricing Calculator for a nightly batch analytics pipeline. The workload requires 50 Compute Engine instances (`n2-standard-16`) operating continuously for 12 hours each night, totaling 365 hours per month per instance. The processing engine is stateless, fault-tolerant, and designed to resume from checkpoints without data loss if an instance is terminated unexpectedly. During the 12-hour operating window, the pipeline processes and updates 20 TB of active data daily, which is continuously read and written to Cloud Storage. Which parameter combination in the Pricing Calculator produces the most accurate configuration for achieving the lowest valid monthly cost estimate?
- Configure Compute Engine instances as Spot VMs running for 365 hours per month, and set the Cloud Storage bucket class to Standard storage.Cevap
- BConfigure standard Compute Engine instances for 730 hours per month with a 3-Year Committed Use Discount (CUD), and set the Cloud Storage bucket class to Coldline storage.
- CConfigure Compute Engine instances as Spot VMs with an added 1-Year Committed Use Discount (CUD) applied in the calculator settings, and set the Cloud Storage bucket class to Archive storage.
- DConfigure standard Compute Engine instances for 365 hours per month relying on Sustained Use Discounts (SUDs) for maximum compute savings, and set the Cloud Storage bucket class to Nearline storage.