Correct Answer: A

Put the full path to the .zip even if you're in the same directory ex: esxcli software vib install -d /tmp/ESXi600-201504001.zip Also make sure you're in maintenance mode How to perform next/related steps: Check:----https://pubs.vmware.com/vsphere-60/ index.jsp#com.vmware.vsphere.upgrade.doc/GUID-22A4B153-CB21-47B4-974E-2E5BB8AC6874.html? resultof=%2522

Correct Answer: CD

Explanation: You specify the behavior of the Auto Deploy server by using a set of rules written in Power

CLI. The Auto Deploy rule engine checks the rule set for matching host patterns to decide which items (image profile, host profile, or vCenter Server location) to provision each host with. The rule engine maps software and configuration settings to hosts based on the attributes of the host. For example, you can deploy image profiles or host profiles to two clusters of hosts by writing two rules, each matching on the network address of one cluster The rule engine includes rules and rule sets.

Rules Rules can assign image profiles and host profiles to a set of hosts, or specify the location (folder or cluster) of a host on the target vCenter Server system. A rule can identify target hosts by boot MAC address, SMBIOS information, BIOS UUID, Vendor, Model, or fixed DHCP IP address. In most cases, rules apply to multiple hosts. You create rules by using Auto Deploy PowerCLI cmdlets. After you create a rule, you must add it to a rule set. Only two rule sets, the active rule set and the working rule set, are supported. A rule can belong to both sets, the default, or only to the working rule set. After you add a rule to a rule set, you can no longer change the rule. Instead, you copy the rule and replace either items or patterns. By default, Auto Deploy uses the name of the rule for the copy and hides the original rule.

Reference: https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc_50%2FGUIDEB22DCFF-C606-43CB-A7BC-068AC79A6237.html

Correct Answer: BC

das.isolationShutdownTimeout The number of seconds an FDM waits for a virtual machine to power off after initiating a guest shutdown before the FDM issues a power off. If the option is unset, 300s is used.

Reference: https://kb.vmware.com/selfservice/microsites/search.do? language=en_USandcmd=displayKCandexternalId=2033250

Correct Answer: CD

Bandwidth Admission Control in vSphere DRS If you power on a virtual machine that is in a cluster, vSphere DRS places the virtual machine on a host that has the capacity to guarantee the bandwidth reserved for the virtual machine according to the active teaming policy. vSphere DRS migrates a virtual machine to another host to satisfy the bandwidth reservation of the virtual machine in these situations:

1.

The reservation is changed to a value that the initial host can no longer satisfy.

2.

A physical adapter that carries traffic from the virtual machine is offline. To use admission control in vSphere DRS, perform the following tasks:

Reference: https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.networking.doc/GUID7B131191-D989-431A-99F7-BA3C27BD4F64.html

Correct Answer: A

Reference: https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.security.doc/GUID-4D0F8E632961-4B71-B365-BBFA24673FDB.html

Correct Answer: ABC

ESXi Certificate Replacement

For ESXi hosts, you can change certificate provisioning behavior from the vSphere Web Client.

Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUID4469A6D3-048A-471C-9CB4-518A15EA2AC0.html

Correct Answer: BC

root User Privileges By default each ESXi host has a single root user account with the Administrator role. That root user account can be used for local administration and to connect the host to vCenter Server. This common root account can make it easier to break into an ESXi host and make it harder to match actions to a specific administrator. Set a highly complex password for the root account and limit the use of the root account, for example, for use when adding a host to vCenter Server. Do not remove the root account. In vSphere 5.1 and later, only the root user and no other named user with the Administrator role is permitted to add a host to vCenter Server. Best practice is to ensure that any account with the Administrator role on an ESXi host is assigned to a specific user with a named account. Use ESXi Active Directory capabilities, which allow you to manage Active Directory credentials if possible.

Reference: https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.security.doc%2FGUID55F14938-8A2F-4703-8A60-3516F9C3E312.html

Correct Answer: A

Reduce Memory Overhead for Virtual machines with 3D graphics Option

Virtual machines with the 3D graphics option enabled can have higher memory consumption than other

virtual machines. You can reduce the memory overhead by editing the configuration file (.vmx file) of your

virtual machines and disabling certain memory related settings. Reducing the memory overhead of virtual

machines can help you increase the number of virtual machines per host.

Prerequisites

Verify that your virtual machines are using hardware version 10 or later.

Procedure

1 Shut down the virtual machine on which the 3D graphics option is enabled.

2 Disable the Accelerate 3D Graphics option.

3 Upgrade your ESXi host to use the features available in hardware version 10 or later.

4 Set the maximum size of your display to the size you need.

5 Locate the configuration file (.vmx) of your virtual machine.

6 Open the virtual machine configuration file in a text editor and add the line, vga.vgaOnly=TRUE.

This option removes all graphics and SVGA functionality from your SVGA device, but does not remove the

settings that allow BIOS to enter VGA mode.

7 Save the changes and exit the text editor.

8 Power on your virtual machine and check the display console.

9 Verify the memory reservation settings in the vmware.log file.

Reference:

https://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.vm_admin.doc%2FGUIDFAB0E2C3-3474-461D-99BC-549F7E21FE85.html

Correct Answer: A

Correct Answer: A

About the boot.cfg File The boot loader configuration file boot.cfg specifies the kernel, the kernel options, and the boot modules that the mboot.c32 boot loader uses in an ESXi installation. The boot.cfg file is provided in the ESXi installer. You can modify the kernelopt line of the boot.cfg file to specify the location of an installation script or to pass other boot options. The boot.cfg file has the following syntax: # boot.cfg -- mboot configuration file # # Any line preceded with '#' is a comment.

title=STRING kernel=FILEPATH kernelopt=STRING modules=FILEPATH1 --- FILEPATH2... --- FILEPATHn

# Any other line must remain unchanged. The commands in boot.cfg configure the boot loader.

Reference: https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.upgrade.doc %2FGUID-1DE4EC58-8665-4F14-9AB4-1C62297D866B.html