Migrate developer VMs to GCP; environments are started/stopped frequently and need persistent state. Provide cost visibility to finance. Which two steps should you take? (Choose two.)

To maintain persistent state while stopping VMs, configure persistent disks with the --no-auto-delete flag. This ensures the disk remains even when the VM is stopped, allowing data to persist across restarts. Stopping the VM, rather than terminating it, also preserves the disk. For cost visibility, use BigQuery billing export combined with labels. Labels can be applied to resources (like VMs) to categorize costs by project, team, or environment. Exporting billing data to BigQuery enables detailed analysis and reporting, allowing finance to track spending effectively. Incorrect options: -auto-delete with termination would delete the disk, losing state. CPU utilization labels don't directly provide cost association for finance; billing export and resource labels are needed. Local SSDs are ephemeral and lose data on VM termination. Storing state in Cloud Storage is an option for some applications but doesn't directly address the VM's persistent disk requirement for state.