VCP-410 Test Questions
o Optimize for performance – Acknowledges changes to the virtual disk immediately, but saves them at a later time.
o VMI currently supports only 32-bit guests.
Additional Resources
Setup for Failover Clustering and Microsoft Cluster Service
o Support for Windows Server 2003 SP2, 2000 SP4, or 2008.
o Only two-node clustering.
Storage Type Cluster in a Box Cluster Across Boxes Standby Host
(n+1)
Virtual disks VCP-410 exam Yes (recommended) No No
Non-pass-through RDM (virtual compatibility mode) Yes Yes No
Pass-through RDM (physical compatibility mode) No Yes (recommended) Yes
o Clusters across physical machines with non-pass-through RDM is supported only for clustering with Windows 2000 Server or Windows Server
2003. It is not supported for clustering with Windows Server 2008.
o Not supported:
o Clustering on iSCSI or NFS disks.
o Clustered virtual machines as part of VMware clusters (DRS or HA).
o MSCS in conjunction with VMware Fault Tolerance.
o Migration with VMotion.
o N-Port ID Virtualization (NPIV)
o With native multipathing (NMP), clustering is not supported when the path policy is set to round robin.
o You must use hardware version 7 with ESX4.
o You can put the boot disk of a virtual machine on a SAN-based VMFS volume.
o Clustered continuous replication (CCR) environment for Microsoft Exchange - Use physical compatibility mode RDMs.
o For boot disks - Select “Support clustering features VCP-410 exam questions such as Fault Tolerance” to create a disk in eagerzeroedthick format.
o SCSI Controller Type:
o Windows 2000 and 2003 - Server LSI Logic Parallel (download from the LSI web site).
o Windows 2008 - LSI Logic SAS
o Cluster across boxes:
o Shared storage must be on an FC SAN.
o RDM in physical compatibility (pass-through) or virtual compatibility (non-pass-through) mode. VMware recommends physical
compatibility mode. The cluster cannot use virtual disks for shared storage.
o Failover clustering with Windows Server 2008 is not supported with virtual compatibility mode
o Standby Host (n+1): Use only a single physical path from the host to the storage arrays.
vSphere Command-Line Interface Installation and Reference Guide
o vSphere CLI commands run on top of the vSphere SDK for Perl.
o You can install a vSphere CLI package on either Linux or Microsoft Windows, or deploy the vSphere Management Assistant (vMA).
o If you establish a vCenter Server system as a target server, you can execute most vSphere CLI commands against all ESX/ESXi systems it
manages without additional authentication.
o You can use vSphere CLI commands interactively or in scripts.
o The installation script for the vSphere CLI is supported on:
o Red Hat Enterprise VCP-410 study guide Linux (RHEL) 5.2 (64 bit)
o Red Hat Enterprise Linux (RHEL) 5.2 (32 bit)
o SUSE Enterprise Server 10 SP1 32 bit
o Ubuntu 8.04 32 bit
o vSphere CLI is supported on:
o Windows XP SP2 32 bit
o Windows XP SP2 64 bit
o Windows Vista Enterprise SP1 32 bit
o Windows Vista Enterprise SP1 64 bit
o If you set up a vCenter Server system as a target server, you can specify any of the ESX/ESXi hosts that vCenter Server system manages using
the –vihost option.
o VMware recommends that you use the vSphere CLI commands with the vicfg prefix. Commands with the esxcfg prefix are available mainly for
compatibility reasons & might become obsolete.
