What are two benefits that can be achieved by creating these images as templates (Choose Two)?

An administrator wants to use standard images for virtual machine deployment. What are two benefits that can be achieved by creating these images as templates (Choose Two)?

A.
easier to upgrade and manage multiple VMs

B.
templates deploy faster than cloning

C.
base images cannot be directly modified

D.
less disk space used for base images

Explanation:
VirtualCenter Templates Usage and Best Practices, page 3.

Overview of VirtualCenter Templates
Templates have been redesigned to fit into the new VMware Infrastructure inventory model and have been updated to address the need to keep virtual machines updated with the most recent operating systems and application patches. Instead of saving virtual machine templates in a completely separate inventory, VirtualCenter 2 stores templates into the main inventory with other virtual machines. However, templates are identified by a different icon and by the ability to prevent them from powering on. As such, templates can now be:
+ Viewed from the "Virtual Machines and Templates" or the "Hosts and Clusters" inventory views. + Quickly converted back and forth between virtual machines that can be powered on and receive updates and templates that cannot powered on, but can be used as the source images from which to deploy new virtual machines.
+ Stored in monolithic (runnable) virtual disk format for quick templatet- virtual machine conversions or stored in sparse (non-runnable) virtual disk format to conserve storage space.

9 Comments on “What are two benefits that can be achieved by creating these images as templates (Choose Two)?

  1. Anup Kumar says:

    I think option B and D are the correct answer for this question. it is not compulsory to powerdown the VM while making clone.

  2. Anitha says:

    Yes C and D are incorrect

    Working with Templates and Clones in the vSphere Client
    A clone is a copy of a virtual machine. A template is a master copy of a virtual machine that can be used to create many clones.

    When you clone a virtual machine, you create a copy of the entire virtual machine, including its settings, any configured virtual devices, installed software, and other contents of the virtual machine’s disks. You also have the option to use guest operating system customization to change some of the properties of the clone, such as the computer name and networking settings.

    Cloning a virtual machine can save time if you are deploying many similar virtual machines. You can create, configure, and install software on a single virtual machine, and then clone it multiple times, rather than creating and configuring each virtual machine individually.

    If you create a virtual machine that you want to clone frequently, make that virtual machine a template. A template is a master copy of a virtual machine that can be used to create and provision virtual machines. Templates cannot be powered on or edited, and are more difficult to alter than ordinary virtual machine. A template offers a more secure way of preserving a virtual machine configuration that you want to deploy many times.

    When you clone a virtual machine or deploy a virtual machine from a template, the resulting cloned virtual machine is independent of the original virtual machine or template. Changes to the original virtual machine or template are not reflected in the cloned virtual machine, and changes to the cloned virtual machine are not reflected in the original virtual machine or template.

  3. Abs says:

    I think D is definitely incorrect.
    A is correct.
    A because permissions can be configured for template deployment, ref: http://www.vmware.com/pdf/vsphere4/r40/vsp_40_admin_guide.pdf page 223

    B can be correct. Less disk space is used for templates (it just renames the vmx file without creating a new vm). However disk space will still be consumed for the template.

    C is true too http://www.vmware.com/pdf/vsphere4/r40/vsp_40_admin_guide.pdf page 170 where it states that the vm should be off to clone. When administrator is cloning a vm, s/he can clone using the template rather than the source as the source will require always powering down to clone.

    So best answer I think is A and C.

  4. Scott says:

    The answer should be B and C. and the reason is the question itself…

    An administrator wants to use standard images for virtual machine deployment. What are two benefits that can be achieved by creating these images as templates (Choose Two)?

    B. they want to deploy VMs using templates.. vs? cloning or manual deployment. so in this case, templates WOULD be quicker than cloning or manually installing each OS and configuring them.

    C. You cannot modify templates directly. they must first be converted to VMs, then turned on and/or edited, and converted back into templates.

  5. Scott says:

    some more info..

    http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc_50%2FGUID-F40130B0-0194-4A41-91FA-1A967721924B.html

    Working with Templates and Clones in the vSphere Client
    A clone is a copy of a virtual machine. A template is a master copy of a virtual machine that can be used to create many clones.

    When you clone a virtual machine, you create a copy of the entire virtual machine, including its settings, any configured virtual devices, installed software, and other contents of the virtual machine’s disks. You also have the option to use guest operating system customization to change some of the properties of the clone, such as the computer name and networking settings.

    Cloning a virtual machine can save time if you are deploying many similar virtual machines. You can create, configure, and install software on a single virtual machine, and then clone it multiple times, rather than creating and configuring each virtual machine individually.

    If you create a virtual machine that you want to clone frequently, make that virtual machine a template. A template is a master copy of a virtual machine that can be used to create and provision virtual machines. Templates cannot be powered on or edited, and are more difficult to alter than ordinary virtual machine. A template offers a more secure way of preserving a virtual machine configuration that you want to deploy many times.

    When you clone a virtual machine or deploy a virtual machine from a template, the resulting cloned virtual machine is independent of the original virtual machine or template. Changes to the original virtual machine or template are not reflected in the cloned virtual machine, and changes to the cloned virtual machine are not reflected in the original virtual machine or template.


Leave a Reply

Your email address will not be published. Required fields are marked *