Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
Your enterprise runs a diverse set of workloads on Google Cloud Compute Engine, including core business applications and a large-scale, stateless batch data-processing pipeline. A recent FinOps audit reveals significant cloud spend inefficiencies due to overprovisioned VM instances and standard on-demand pricing across all environments.
You are tasked with implementing a comprehensive cost-optimization strategy that accomplishes the following requirements:
Which strategy should you implement?
This option forces all application workloads onto cost-optimized E2 shared-core machine types, provisions Flex-start GPU capacity for the batch pipeline, and utilizes the Carbon Footprint dashboard to track infrastructure costs.
The organization's primary objective was reducing carbon emissions across short-lived ML model pre-training jobs while minimizing compute tier costs on low-throughput internal tools.
This approach relies on arbitrary off-peak downsizing to shared-core machine types, long-term Committed Use Discounts (CUDs) for batch infrastructure, and standard Cloud Billing budget alerts to monitor spending.
The workload required non-interruptible 24/7 steady-state operation over multiple years, where long-term resource commitments are optimal and traffic patterns drop to near-zero predictably each night.
This strategy combines automated machine learning analytics via Google Cloud Recommender, cost-optimized ephemeral compute through Spot VMs, and comprehensive cost modeling tools (Google Cloud Pricing Calculator and Cloud Billing export to BigQuery) to achieve maximum financial efficiency.
This approach directly targets the root causes of cloud waste using native Google Cloud FinOps tools without introducing service disruption or inappropriate commitment locks on ephemeral workloads.
This option uses an arbitrary 50% CPU threshold to identify and delete instances as idle, commits to 1-year spend-based CUDs for the batch processing cluster, and uses the Google Cloud Region Picker for cost forecasting.
The primary task was evaluating a multi-region migration strategy to balance regional pricing against network latency and environmental impact for enterprise databases.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated