Question-37: In Compute Engine, a machine image is a resource that stores all of the configuration, metadata, permissions, and data from multiple discs of a virtual machine (VM) instance. This information can be retrieved quickly and easily. This information may be quickly and readily accessed at your convenience. Machine images have a wide variety of applications, some of the most common of which include performing system maintenance, creating backups and recoveries, and cloning instances. It is necessary for you to create a copy of a Linux virtual machine that is currently being used in production in the US-Central region. In the event that there are changes made to the virtual machine that is used for production, you want to have the ability to swiftly maintain and replace the copy. Your goal is to have this capability. You are going to deploy the copy in the East region of the United States as a new instance in a distinct project altogether. What are the further steps that need to be taken by you?
A. In the US-East region of the virtual machine, create a new instance of the virtual machine by using the Linux dd and netcat commands to copy and stream the contents of the root disc.
B. Make a snapshot of the root disc, and when you start a new instance of a virtual machine in the US-East region, use the snapshot you just made as the root disc.
C. Using the dd programme in Linux, generate an image file from the root disc, and then create a new virtual machine instance in the US-East area.
D. Take a snapshot of the root disc, then use that snapshot as the basis for creating an image file in Google Cloud Storage. Finally, establish a new virtual machine instance in the US-East region by making the image file the root disc of the new instance.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 4 Explanation: Both Option 1 and Option 2 refer to attaching the file system to a new virtual machine (VM), as opposed to putting it at the root of a new set of virtual machines (VMs). Because the image has to be stored on the GCP platform in order to execute the gcloud or Google Console commands that are required to construct a VM with the image, Option C is not available inside the GCP. This makes it very evident that we can generate a VM instance by using a snapshot, and that we will only need a custom image if we need to create a large number of instances. Right now, we are just going to make one. Only if it's in the same zone as the original: Please be aware that the disc has to be located in the same zone as the instance. On the other hand, this is not the case here since we have: Because of the various environments and projects, you will need to make use of a bucket. When utilizing snapshots from one project in another, it is necessary to create a disc using the shared snapshot. Since option B only emphasizes the sharing of snapshots and not the construction of the disc and subsequent attachment of that disc to a new instance in a separate project, option 2 is incorrect since a disc created from a snapshot cannot be used as the root disc. You have the ability to make snapshots in a single area. Create a disc from the snapshot, then use it in a virtual machine once you have shared it with other regions. Option 2 specifies that a snapshot should be used as the root disc.