Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 49 of 98
Free Preview · 98 of 324 · questions 1–98 of 324 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
The question doesn't specify whether the instance type is predefined or custom. If it's predefined, the answer is C, and if it's custom, the answer is D. In my opinion, since it's not specified, the answer is C because Google Cloud creates instances linked to a machine type. This type specifies the CPUs and memory.
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.