Exam Professional Cloud Architect topic 1 question 7 discussion

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

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

A / B : the option only apply when VM are deleted (terminated ?), or here we are talking about stop/start See https://cloud.google.com/compute/docs/samples/compute-disk-autodelete-change C : Do even know if it is possible D : In order to bring "visibility on the cost" E : local disks does not persist F : complex solution, but it works So D & F

Answer is : A& D A. Use the --no-auto-delete flag on all persistent disks and stop the VM: 1. Cost Savings: When you stop a VM, you only pay for the persistent disks attached to it. The --no-auto-delete flag ensures that the disks remain available even when the VM is stopped, preserving the developers' work and avoiding the cost of recreating the environment from scratch each time. 2. State Persistence: This approach ensures that the development environment's state is saved on the persistent disk, allowing developers to resume their work seamlessly when they restart the VM. D. Use Google BigQuery billing export and labels to associate cost to groups: 1. Cost Visibility: BigQuery billing export allows you to analyze your Google Cloud costs in detail. By applying labels to your resources (e.g., "environment: development", "team: frontend"), you can categorize and track costs associated with different development groups.

Choose A and D

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?

From the GCP Practice exam... A and D

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

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.

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.