Answer-first summary for fast verification
Answer: Use the --no-auto-delete flag on all persistent disks and stop the VM, Use Google BigQuery billing export and labels to associate cost to groups
The correct answers are A and D. Using persistent disks to store the state ensures that data is preserved even when the VM is stopped, which aligns with option A. The use of the --no-auto-delete flag on persistent disks makes sure these disks are not deleted when the VM is stopped, allowing developers to maintain state across multiple start/stop events. Option D is also correct as using Google BigQuery billing export along with labels allows the finance department to associate costs with specific groups, providing the necessary cost visibility. Options B, E, and F introduce unnecessary complexity or do not provide the desired persistence and cost visibility as effectively as options A and D.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
No comments yet.
The Director of Engineering requires all developers to move their development infrastructure resources from on-premises virtual machines (VMs) to Google Cloud Platform (GCP) to reduce costs. These development resources often start and stop throughout the day and need to maintain their state across these cycles. Additionally, the finance department needs visibility into the associated costs. You are asked to design a process for running a development environment in GCP that ensures cost visibility while maintaining the state across start/stop cycles. Which two steps should you take? (Choose two.)
A
Use the --no-auto-delete flag on all persistent disks and stop the VM
B
Use the --auto-delete flag on all persistent disks and terminate the VM
C
Apply VM CPU utilization label and include it in the BigQuery billing export
D
Use Google BigQuery billing export and labels to associate cost to groups
E
Store all state in Google Cloud Storage, snapshot the persistent disks, and terminate the VM