To reduce costs, the Director of Engineering has required all developers to move their development infrastructure resources from on-premises virtual machines
(VMs) to Google Cloud Platform. These resources go through multiple start/stop events during the day and require state to persist. You have been asked to design the process of running a development environment in Google Cloud while providing cost visibility to the finance department.
Which two steps should you take? (Choose two.)
To run a development environment in Google Cloud and provide cost visibility, the following steps should be taken: First, use persistent disks with the --no-auto-delete flag. This ensures that the state persists even when VMs are stopped and avoids data loss by not automatically deleting the disks when the instance is stopped. Second, use Google BigQuery billing export and labels to associate costs to groups. This allows the finance department to have visibility into cost allocation and analysis by associating resource consumption with specific labels, enabling better cost management and accountability.
I spent all morning researching this question. I just popped over and took the GCP Practice exam on Google's website and guess what... this question was on it word for word, but it had slightly different answers, but not by much here is what I learned. The correct answer is 100% A / D and here is why. On the sample question, the "F" option is gone. "A" is there but slightly reworked, it now says: "Use persistent disks to store the state. Start and stop the VM as needed" which makes much more sense. The practice exam says A and D are correct. Given the wording of this question, if A and B, where there then both would be correct because of the word "persistent" and not because of the flag. The "no-auto-delete" makes A slightly safer than B, but it is the "persistent disk" that makes them right, not the flag. Hope that helps! F is not right because that is a complex way of solving the issue that by choosing Persistent Disk solves it up front. HTH
Thank you, it really helps!!
Very aptly summarized.
(A) is not sense because the flag is to preserve disk when the istances was deleted, when the istances was stopped the data on persistend disk are not deleted. So good to know that the response was reworked (B) is wrong because only on AWS you can terminate istances. On GCP the "terminate" action do not exist .
A and D looks correct as per https://cloud.google.com/sdk/gcloud/reference/compute/instances/set-disk-auto-delete#--auto-delete ; https://cloud.google.com/billing/docs/how-to/export-data-bigquery
-no-auto-delete flag does not have effect on the state of the application. I believe D and F are correct ANS, https://cloud.google.com/compute/docs/instances/stop-start-instance
A is correct, Use of persistent disk mean the data is preserved even after restart. -np-auto-delete on persistent disk means pesistent disk won't be deleted when VM is deleted. D is correct, becuase second part of question asks for billing report to finanace department and Label and BQ helps in cost analysis.
same question, official option: A. Use persistent disks to store the state. Start and stop the VM as needed. B. Use the "gcloud --auto-delete" flag on all persistent disks before stopping the VM. C. Apply VM CPU utilization label and include it in the BigQuery billing export. D. Use BigQuery billing export and labels to relate cost to groups. E. Store all state in a Local SSD, snapshot the persistent disks, and terminate the VM. This question will not be tested, no need to read
AD Use the flag -no-auto-delete with this flag, the disk won't be delete when the VM is terminated. Billing export to BigQuery enables you to export your daily usage and cost estimates automatically throughout the day to a BigQuery dataset you specify. You can then access your billing data from BigQuery.
From the GCP Practice exam... A and D
A. Use the --no-auto-delete flag on all persistent disks and stop the VM D. Use Google BigQuery billing export and labels to associate cost to groups ITEXAMSLAB.COM
Another confusing question because I took the "these machines go through multiple stop/starts during the day" as a part of the migration, not as a part of daily functionality, so none of the answers other than D made much sense to me. People need to word the questions better on tests and give more than enough context or people like me are going to get confused, second guess our answers, and fail.
F is too complex solution to solve this problem. E local SSD does not persist on termination of vm so this is also a wrong option A, B suggest persistent disk but I think A makes better sense. So my answer is A and D
E wrong: Scenarios where Compute Engine does not persist Local SSD data Data on Local SSD disks does not persist through the following events: If you shut down the guest operating system and force the VM to stop.
Hi all, i am trying to view questions from 135.But i cannot access the page as it is asking for contributer access.Is it same for everyone?
Based on documentation A is correct https://cloud.google.com/sdk/gcloud/reference/compute/instances/set-disk-auto-delete Also the documentation clearly states that this flag will be help retain the state when VM is started/stopped. https://cloud.google.com/blog/products/storage-data-transfer/save-money-by-stopping-and-starting-compute-engine-instances-on-schedule For cost visibility option D is correct.
D. Use Google BigQuery billing export and labels to associate cost to groups: This offers granular cost visibility across various development teams or projects through BigQuery data analysis. Combining labels with billing export allows you to associate resource consumption with specific groups, enabling chargeback mechanisms and fostering cost accountability. E. Store all state into local SSD, snapshot the persistent disks, and terminate the VM: This option minimizes ongoing cost by utilizing low-cost local SSD for active state during runtime and terminating the VM when development isn't ongoing. Snapshots offer quick restoration back to the latest state without incurring persistent disk charges during downtime.
DF. This is the question in google practice test.
D & F for me
How can D ever be right coz it's Bigquery Billing Export and question is about VM billing
This means you can export the billing to the BQ and then do analysis.
B and D. A is wrong because, (--no-auto-delete) would lead to extra storage costs for the disks even when VMs are not running.