Exam Associate Cloud Engineer topic 1 question 49 discussion

coldpar, why are you getting the people confused? you need to stop teh VM and modify the RAM, that's all

D is correct. If you pay attention to the question, option C mentions n1-standard-8. That instance type has 8vCPUs and 30 GB RAM, and we only need 8GB. On top of that, it is possible to use custom machine type to adjust current VM RAM to the value we need. Got the answer from this course I did to prepare the exam: https://www.udemy.com/course/google-cloud-associate-engineer-exam-practice-tests/?couponCode=21CDE6A4C2B95F79BD97 good luck!

In Google Cloud, you cannot directly modify the memory allocation for an existing VM. Instead, you must change the VM's machine type to one with the desired memory and vCPU configuration (e.g., n1-standard-8, which has 8 GB of memory). The VM needs to be stopped before making this change, and then it can be restarted. Why not other options? A (Live migration): Live migration moves workloads during maintenance but does not change the VM's memory allocation. B (Metadata change): Adding metadata does not affect memory allocation. D (Directly increasing memory): You cannot manually increase only the memory of a VM; you must select a predefined machine type.

C. Esto implica detener la máquina virtual, cambiar el tipo de máquina a uno que tenga 8 GB de memoria (como n1-standard-8), y luego reiniciarla.

D is the correct answer

You can add extended memory only to custom machine types. Predefined machine types are not supported.

D is correct. C.n1 standard8 has 30GB RAM. A&B- No vm instance stop, Hence can't be updated.

ANSWER D is correct because it is the correct process to follow to increase the memory of a virtual machine in the Google Cloud Platform. To increase the memory of a virtual machine, you need to first stop the VM, since it is not possible to modify the memory of a running VM. Then, you can increase the memory of the VM by editing the machine type and selecting a machine type with more memory. Once you have made the change, you can start the VM again. ANSWER A is not the best approach as it relies on live migration which can be a risky operation. ANSWER B is incorrect because adding metadata to the VM will not change the amount of memory allocated to the VM. ANSWER C is incorrect because changing the machine type to n1-standard-8 would also increase the number of vCPUs to 8, which may not be necessary and could result in overprovisioning of resources. In addition, changing the machine type would also affect the cost of the VM instance, which may not be desired. Since the primary concern in this scenario is to increase memory.

Option D

C is incorrect because the 8 in "n1-standard-8" means 8 cpus instead of 8 gb of ram

D is right one

Go for D

The reason A is not correct is because live migration simply moves an existing VM between hosts, no attributes or properties are changed otherwise. Hence, you cannot live migrate from 1 VM type to another. https://cloud.google.com/compute/docs/instances/live-migration

To be exact... There is no "n1" option that has 2vCPU and 4GB. The closest would be n1-standard-2 with 2vCPU and 7.50GB RAM. This machine is already custom. So, option D.

D. Stop the VM, increase the memory to 8 GB, and start the VM.

Ans - D

We do not have the option to increase memory in GCP VM directly. Instead, machine type needs to be changed. However, given the choices, D is the best answer here.