jasilina

o On ESXi, it is not possible to rescan a single storage adapter.
o You can modify the Disk.MaxLUN parameter to improve LUN discovery speed.
o You cannot discover LUNs with a LUN ID number that is greater than 255.
o You can disable the default sparse LUN support to decrease the time ESX/ESXi needs to scan for LUNs.
o The sparse LUN support enables the
220 702
VMkernel to perform uninterrupted LUN scanning when a storage system presents LUNs with
nonsequential LUN numbering.
o NPIV enables a single FC HBA port to register several unique WWNs with the fabric, each of which can be assigned to an individual virtual
machine.
o The virtual machine’s configuration file (.vmx) is updated to include a WWN pair (consisting of a World Wide Port Name and a World Wide
Node Name).
o If NPIV is enabled, four WWN pairs (WWPN & WWNN) are specified for each virtual machine at creation time. All physical paths must be
zoned to the virtual machine.
o NPIV can only be used for virtual machines with RDM disks. Physical HBAs, must have access to all LUNs that are to be accessed by virtual
machines running on that host.
o By default, the host performs a periodic path evaluation every 5 minutes causing any unclaimed paths to be claimed by the appropriate MPP.
o Make sure read/write caching is enabled.
o Dynamic load balancing is not currently supported with ESX/ESXi.
o Path thrashing only occurs on active-passive arrays
Appendix A – Multipathing Checklist
Appendix B – Managing Storage Paths and Multipathing Plugins
o Claim rules indicate which multipathing plugin, the NMP (Native MP) or any third-party MPP, manages a given physical path.
o List claim rules esxcli corestorage claimrule list
o To list all multipathing modules: vicfg-mpath –server <server> –list-plugins
o List all VMware SATPs: esxcli nmp satp list
o List all storage devices: esxcli nmp device list
iSCSI SAN Configuration Guide
o There is no mention of requiring a Service Console connection for iSCSI anymore.
o Virtual SCSI controllers - BusLogic Parallel, LSI Logic Parallel, LSI Logic SAS, and VMware Paravirtual.
o iSCSI Name identifies a particular iSCSI element. The iSCSI name can use either IQN or EUI format.
o IQN (iSCSI qualified name) - can be up to 255 characters long and has the following format: iqn.yyyy-mm.naming-authority:unique_name
o EUI (extended unique identifier) - takes the form eui.<16 hex digits>
o iSCSI aliases - not unique, and are intended to be just a friendly name to associate with the node.
o You must enable your software iSCSI initiator so that ESX can use it to access iSCSI storage.
o Dynamic Discovery - Also known as Send Targets discovery responds by supplying a list of available targets to the initiator. The names and IP
addresses of these targets appear on the Static Discovery tab. If you remove a static target added by dynamic discovery, the target might be
returned to the list the next time a rescan happens, the HBA is reset, or the host is rebooted.
o Static Discovery - The initiator does not have to perform any discovery.
o Dynamic dis

9L0-403 covery obtains a list of accessible targets from the iSCSI storage system, while static discovery can only try to access one particular
target by target name.
o You cannot change the IP address, DNS name, or port number of an existing Send Targets server. To make changes, delete the existing server
and add a new one.
o To protect the integrity of iSCSI headers and data, the iSCSI protocol defines error correction methods known as header digests and data
digests. Both parameters are disabled by default, but you can enable them.
o Check the end-to-end, noncryptographic data integrity beyond the integrity checks that other networking layers provide.
o Enabling header and data digests does require additional processing for both the initiator and the target. Intel Nehalem processors offload
the iSCSI digest calculations.
o Use the esxcli command to connect the VMkernel ports to the software iSCSI initiator.
o Jumbo Frames up to 9kB (9000 Bytes) are supported.
o You cannot change the IP address, DNS name, iSCSI target name, or port number of an existing target. To make changes, remove the existing
target and add a new one.
o iSCSI requires that all devices on the network implement Challenge Handshake Authentication Protocol (CHAP), which verifies the legitimacy
of initiators that access targets on the network. (EDIT - I don’t think its “required”)
o ESX/ESXi supports one-way CHAP for both hardware and software iSCSI, and mutual CHAP for software iSCSI only.
o For software iSCSI only, you can set one-way CHAP and mutual CH
9L0-510 AP for each initiator or at the target level.
o Hardware iSCSI supports CHAP only at the initiator level.
o For software iSCSI, the CHAP name should not exceed 511 and the CHAP secret 255 alphanumeric characters.
o For hardware iSCSI, the CHAP name should not exceed 255 and the CHAP secret 100 alphanumeric characters.
o Boot from a SAN - ensure that the LUN is presented to the ESX system as LUN 0. The host can also boot from LUN 255

On ESXi, it is not possible to rescan a single storage adapter.
o You can modify the Disk.MaxLUN parameter to improve LUN discovery speed.
o You cannot discover LUNs with a LUN ID number that is greater than 255.
o You can disable the default sparse LUN support to decrease the time ESX/ESXi needs to scan for LUNs.
o The sparse LUN support enables th
220 701 VMkernel to perform uninterrupted LUN scanning when a storage system presents LUNs with
nonsequential LUN numbering.
o NPIV enables a single FC HBA port to register several unique WWNs with the fabric, each of which can be assigned to an individual virtual
machine.
o The virtual machine’s configuration file (.vmx) is updated to include a WWN pair (consisting of a World Wide Port Name and a World Wide
Node Name).
o If NPIV is enabled, four WWN pairs (WWPN & WWNN) are specified for each virtual machine at creation time. All physical paths must be
zoned to the virtual machine.
o NPIV can only be used for virtual machines with RDM disks. Physical HBAs, must have access to all LUNs that are to be accessed by virtual
machines running on that host.
o By default, the host performs a periodic path evaluation every 5 minutes causing any unclaimed paths to be claimed by the appropriate MPP.
o Make sure read/write caching is enabled.
o Dynamic load balancing is not currently supported with ESX/ESXi.
o Path thrashing only occurs on active-passive arrays
Appendix A – Multipathing Checklist
Appendix B – Managing Storage Paths and Multipathing Plugins
o Claim rules indicate which multipathing plugin, the NMP (Native MP) or any third-party MPP, manages a given physical path.
o List claim rules esxcli corestorage claimrule list
o To list all multipathing modules: vicfg-mpath –server <server> –list-plugins
o List all VMware SATPs: esxcli nmp satp list
o List all storage devices: esxcli nmp device list
iSCSI SAN Configuration Guide
o There is no mention of requiring a Service Console connection for iSCSI anymore.
o Virtual SCSI controllers - BusLogic Parallel, LSI Logic Parallel, LSI Logic SAS, and VMware Paravirtual.
o iSCSI Name identifies a particular iSCSI element. The iSCSI name can use either IQN or EUI format.
o IQN (iSCSI qualified name) - can be up to 255 characters long and has the following format: iqn.yyyy-mm.naming-authority:unique_name
o EUI (extended unique identifier) - takes the form eui.<16 hex digits>
o iSCSI aliases - not unique, and are intended to be just a friendly name to associate with the node.
o You must enable your software iSCSI initiator so that ESX can use it to access iSCSI storage.
o Dynamic Discovery - Also known as Send Targets discovery responds by supplying a list of available targets to the initiator. The names and IP
addresses of these targets appear on the Static Discovery tab. If you remove a static target added by dynamic discovery, the target might be
returned to the list the next time a rescan happens, the HBA is reset, or the host is rebooted.
o Static Discovery - The initiator does not have to perform any discovery.
o Dynamic discovery obtains a list of accessible targets from the iSCSI storage system, while static discovery can only try to access one particular
target by target name.
220 702
o You cannot change the IP address, DNS name, or port number of an existing Send Targets server. To make changes, delete the existing server
and add a new one.
o To protect the integrity of iSCSI headers and data, the iSCSI protocol defines error correction methods known as header digests and data
digests. Both parameters are disabled by default, but you can enable them.
o Check the end-to-end, noncryptographic data integrity beyond the integrity checks that other networking layers provide.
o Enabling header and data digests does require additional processing for both the initiator and the target. Intel Nehalem processors offload
the iSCSI digest calculations.
o Use the esxcli command to connect the VMkernel ports to the software iSCSI initiator.
o Jumbo Frames up to 9kB (9000 Bytes) are supported.
o You cannot change the IP address, DNS name, iSCSI target name, or port number of an existing target. To make changes, remove the existing
target and add a new one.
o iSCSI requires that all devices on the network implement Challenge Handshake Authentication Protocol (CHAP), which verifies the legitimacy
of initiators that access targets on the network. (EDIT - I don’t think its “required”)
o ESX/ESXi supports one-way CHAP for both hardware and software iSCSI, and mutual CHAP for software iSCSI only.
o For software iSCSI only, you can set one-way CHAP and mutual CHAP for each initiator or at the target level.
o Hardware iSCSI supports CHAP only at the initiator level.
220 701

o For software iSCSI, the CHAP name should not exceed 511 and the CHAP secret 255 alphanumeric characters.
o For hardware iSCSI, the CHAP name should not exceed 255 and the CHAP secret 100 alphanumeric characters.
o Boot from a SAN - ensure that the LUN is presented to the ESX system as LUN 0. The host can also boot from LUN 255.

Appendix A – ESX Technical Support Commands
Command Purpose
esxcfg-advcfg advanced options
esxcfg-auth Configures authentication
esxcfg-boot bootstrap settings

640 802 Dumps
esxcfg-dumppart Configures a diagnostic partition
esxcfg-firewall service console firewall ports
esxcfg-info Information about the state of the service console, VMkernel, various subsystems in the virtual network, and
storage resource hardware.
esxcfg-init Internal initialization routines. Used for the bootstrap process you should not use it under any circumstances.
esxcfg-module Sets driver parameters and modifies which drivers are loaded during startup.
esxcfg-mpath multipath settings for your Fibre Channel or iSCSI disks.
esxcfg-nas Manages NFS mounts
esxcfg-nics physical network adapters
esxcfg-resgrp resource group settings
esxcfg-route default VMkernel gateway route
esxcfg-swiscsi software iSCSI software adapter.
esxcfg-upgrade Upgrades from ESX Server 2.x to ESX.
esxcfg- scsidevs Prints a map of VMkernel storage devices to service console devices.
esxcfg-vmknic VMkernel TCP/IP settings for VMotion, NAS, and iSCSI.
esxcfg-vswif service console network settings.
esxcfg-vswitch virtual machine network settings.
Appendix B – Linux Commands Used with ESX
Appendix C – Using vmkfstools
o vmkfstools utility is used to create and manipulate virtual disks, file systems, logical volumes, and physical storage devices.
Fibre Channel SAN Configuration Guide
o Zones define which HBAs can connect to which SPs.
o Zoning is similar to LUN masking, which is commonly used for permission management. Usually, LUN masking is performed at the SP or server
level.
o WWPN (World Wide Port Name) is a globally unique identifier for a port.
o Port ID (or port address) enables routing. FC switches assign the port ID when the device logs in to the fabric.
o When N-Port ID Virtualization (NPIV) is used, a single FC HBA port (N-port) can register with the fabric by using several WWPNs.
o active-active - access to the LUNs simultaneously through all the storage ports that are available, without significant performance degradation.
o active-passive - one port is actively providing access to a given LUN. The other ports act as backup
o Disk shares are relevant only within a given ESX/ESXi host.
o Virtual machine I/O might be delayed for up to sixty seconds while path failover takes place. I/O delays might be longer on active-passive
arrays.
o On virtual machines running Microsoft Windows, increase the value of the SCSI TimeoutValue parameter to 60.
o Only one VMFS volume per LUN.
o Unless you are using diskless servers, do not set up the diagnostic partition on a SAN LUN.
o ESX/ESXi does not support FC connected tape devices.
o You cannot use

640-802
virtual machine logical-volume manager software to mirror virtual disks. Dynamic disks on a Microsoft Windows virtual
machine are an exception, but require special configuration.
o You should not mix FC HBAs from different vendors in a single server.
o Use a dedicated SCSI adapter for any tape drives that you are connecting to an ESX/ESXi system.
o You should not use boot from SAN in the following situations:
o If you are using Microsoft Cluster Service.
o If I/O contention might occur between the service console and VMkernel.
o Proper LUN masking is critical in boot from SAN mode.
o Runtime Name - the name of the first path to the device. Created by the host. Is not a reliable identifier for the device, and is not persistent.
o vmhba#:C#:T#:L#, where:
o vmhba# is the name of the storage adapter

640 802 braindumps
o C# is the storage channel number.
o T# is the target number.
o L# is the LUN number
o If a target has only one LUN, the LUN number is always zero (

Set up a separate VLAN or virtual switch for vMotion and network attached storage.
o The iSCSI initiator relies on being able to get MAC address changes from certain types of storage. If you are using ESX iSCSI and have iSCSI
storage, set the MAC Address Changes option to Accept.
o A legitimate nee
vcp 4
d for more than one adapter to have the same MAC address, is if you are using Microsoft Network Load Balancing in unicast
mode. When NLB is used in the standard multicast mode, adapters do not share MAC addresses.
o ESX uses the Pluggable Authentication Modules (PAM) structure for authentication. The PAM configuration in /etc/pam.d/vmware-authd, ESX
uses /etc/passwd authentication, but you can configure ESX to use another distributed authentication mechanism.
o CIM transactions also use ticket-based authentication in connecting with the vmware-hostd process.
o Management functions with username/password > vmware-hostd > Service Console
o VM console with ticket > vmkauthd > vm in VMkernel
o vicfg commands do not perform an access check.
o The vpxuser is used for vCenter Server permissions.
o The root user and vpxuser permissions are the only users not assigned the No Access role by default.
o ESX supports SSL v3 and TLS v1.
o All network traffic is encrypted as long as:
o Did not change the Web proxy service to allow unencrypted traffic for the port.
o Service console firewall is configured for medium or high security.
o The default location for your certificate is /etc/vmware/ssl/ on the ESX host. The certificate consists of two files: the certificate itself (rui.crt)
and the private-key file (rui.key).
o The ESX host generates certificates the first time the system is started.
o Each time you restart the vmware-hostd process, the mgmt-vmware script searches for existing certificate files (rui.crt and rui.key). If it cannot
find them, it generates new certificate files.
o SSL timeout settings are set in /etc/vmware/hostd/config.xml.
o Do not set up certificates using passphrases.
o For certificates in a location other than the def

vmware vcp 4
ault location, set the location in /etc/vmware/hostd/proxy.xml.
o If you are performing activities that require root privileges, log in to the service console as a recognized user and acquire root privileges
through the sudo command, which provides enhanced security compared to the su command.
o The service console firewall is configured to block all incoming and outgoing traffic, except for ports 22, 123, 427, 443, 902, 5989, 5988, pings
(ICMP) and communication with DHCP and DNS (UDP only) clients.
o Medium security - All incoming traffic is blocked, except on the default ports and any ports you specifically open. Outgoing traffic is not
blocked.
o Low security - There are no blocks on either incoming or outgoing traffic. This setting is equivalent to removing the firewall.
o Password aging restrictions are enabled for user logins by default.
o Maximum days - By default, passwords are set to never expire.
o Minimum days - The default is 0, meaning that the users can change their passwords any time.
o Warning time - The default is seven days.
o To change this for hosts use esxcfg-auth. Change for users use the command chage.
o By default, ESX uses the pam_cracklib.so plug-in. There is no restrictions on the root password, but the defaults for non-root users is:
o minimum password length is nine
o password length algorithm allows shorter passwords if the user enters a mix of character classes. M – CC = E where the Character Classes
are upper, lower, digits and other.
o retries is set to three
o The pam_passwdqc.so provides a greater number of options for fine-tuning password strength and performs password strength tests for all
users, including the root user.
o setuid allows an application to temporarily change the permissions of the user running the application.
o setgid changes the permissions of the group running the application.
o Default setuid applications: crontab, pam_timestamp_check, passwd, ping, pwdb_chkpwd, ssh-keysign, su, sudo, unix_chkpwd, vmkload_app,
vmware-authd, vmware-vmx. Default setgid Applications: wall, lockfile.
o Virtual Machine Recommendations:
o Install Antivirus Software
o Disable Copy and Paste Operations Between the Guest Operating System and Remote Console
o Removing Unnecessary Hardware Devices
o Limiting Guest Operating System Writes to Host Memory
o Configuring Logging Levels for the Guest Operating System
o Host profiles eliminates per-host, configuration and maintain configuration consistency and correctness across the datacenter.
o Only supported f
640 802
or VMware vSphere 4.0 hosts.
o Host Profiles are only available when the appropriate licensing is in place.
o You can export a profile to a file that is in the VMware profile format (.vpf).

Key contents of the metadata in the mapping file include the location of the mapped device (name resolution), the locking state of the
mapped device,

vcp-410 permissions, and so on.
o You cannot perform vMotion or Storage vMotion between datastores when NPIV is enabled.
o VMware protects the service console with a firewall. It also mitigates risks using other methods:
o Only services essential to managing its functions.
o By default, installed with a high-security setting. All outbound ports are closed.
o By default, all ports not specifically required for management access to the service console are closed.
o By default, weak ciphers are disabled and all communications from clients are secured by SSL. Default certificates created on ESX use
SHA-1 with RSA encryption as the signature algorithm.
o The Tomcat Web service, has been modified to run only those functions required.
o VMware monitors all security alerts (for the RHEL5 distribution and 3rd party software).
o Insecure services such as FTP and Telnet are not installed.
o The number of applications that use a setuid or setgid flag is minimized.
o ESX can automate whether services start based on the status of firewall ports, but this only applies to service settings configured through the
vSphere Client or applications created with the vSphere Web services SDK. Doesn’t apply to changes made with the esxcfg-firewall utility or
configuration files in /etc/init.d/.
Port Purpose Interface Traffic type
22 SSH Server Service Console Incoming TCP
80 HTTP access and WS-Management Service Console Incoming TCP
123 NTP Client Service Console Outgoing UDP
427 The CIM client SLPv2 to find CIM servers. Service Console Incoming and
outgoing UDP
443 HTTPS access - vmware-hostd
vCenter Server access to ESX hosts
Client access to vCenter Server and ESX hosts
WS-Management

vmware vcp 410
Client access to vSphere Update Manager
Converter access to vCenter Server
Web Access to vCenter Server and ESX hosts
Service Console Incoming TCP
902 Host access to other hosts for migration and provisioning
Authentication traffic for ESX (xinetd/vmware-authd)
Client access to virtual machine consoles (UDP) Status update (heartbeat)
connection from ESX to vCenter Server
Service Console Incoming TCP,
outgoing UDP
903 Remote console traffic from VI client & Web Access (xinetd/vmware-authd-mks) Service Console Incoming TCP
2049 Transactions from NFS storage devices VMkernel Incoming and
outgoing TCP
2050-2250 Between ESX hosts for HA and EMC Autostart Manager Service Console Outgoing TCP,
incoming and
outgoing UDP
3260 Transactions to iSCSI storage devices VMkernel &
Service Console
Outgoing UDP
5900-5964 RFB protocol, which is used by management tools such as VNC Service Console Incoming and
outgoing TCP
5989 CIM XML transactions over HTTPS Service Console Incoming and
outgoing TCP
8000 VMotion requests VMkernel Incoming and
outgoing TCP
8042-8045 Between ESX hosts for HA and EMC Autostart Manager Service Console Outgoing TCP,
incoming and
outgoing UDP
8100, 8200 Between ESX hosts for Fault Tolerance Service Console Outgoing TCP,
incoming and
outgoing UDP
vmware vcp 410

PLUS installed management agents and supported services such as NFS.
o Create a separate VLAN for communication with the service console.
o Configure network access for connections with the service console through a single virtual switch and one or more uplink ports

o You cannot use IDE/ATA drives to store virtual machines.
o Use local SATA storage, internal and external, in unshared mode only.
o Some SAS storage systems can offer shared access
o You can have up to 256 VMFS datastores per system, with a minimum volume size of 1.2GB.
o Grow the existing datastore extent if the storage device where your datastore resides has free space. You can grow the extent up
Passed VCP410 to 2 TB.
o You can connect up to 32 hosts to a single VMFS volume. (EDIT: Maximums document says 64)
o Perform a rescan each time you:
o Create new LUNs on a SAN.
o Change the path masking on a host.
o Reconnect a cable.
o Make a change to a host in a cluster.
o Do not rescan when a path is unavailable.
o To rescan adapters on all hosts managed by vCenter by right-clicking a datacenter, cluster, or folder and selecting Rescan for Datastores.
o ESX does not support the delegate user functionality that enables access to NFS volumes using non-root credentials
o Disk format on a NAS device is dictated by the NFS server, typically a thin format that requires on-demand space allocation.
o When your host accesses a virtual machine disk file on an NFS-based datastore, a .lck-XXX lock file is generated to prevent other hosts from
accessing this file.
o If the underlying NFS volume, is read-only, make sure that the volume is exported as a read-only share by the NFS server, or configure it as a
read-only on the ESX host.
o A diagnostic partition cannot be located on an iSCSI LUN accessed through a software iSCSI initiator.
o You can query and scan the host’s diagnostic partition using the vicfg-dumppart -l command
o You can group datastores into folders.
o You can unmount:
o NFS datastores
o VMFS datastore copies mounted without resignaturing
o You can have up to 32 extents.
o You can grow an extent in an existing VMFS datastore. Only extents with free space immediately after them are expandable.
o If a shared datastore has powered on virtual machines and becomes 100% full, you can increase the datastore’s capacity only from the host,
with which the powered on virtual machines are registered.
o You can mount a VMFS datastore only if it does not collide with an already mounted VMFS datastore that has the same UUID (signature).
o When resignaturing a VMFS copy, ESX assigns a new UUID and a new label to the copy, and mounts the copy as a datastore distinct from the
original.
o The default format of the new label assigned to the datastore is snap-<snapID>-<oldLabel>, where <snapID> is an integer and <oldLabel> is the
label of the original datastore.
o Datastore resignaturing is irreversible.
Passed VCP 4
o A spanned datastore can be resignatured only if all its extents are online.
o Pluggable Storage Architecture (PSA) is an open modular framework that coordinates the simultaneous operation of multiple multipathing
plugins (MPPs). The VMkernel multipathing plugin that ESX provides by default is the VMware Native Multipathing Plugin (NMP). Two types of
NMP subplugins, Storage Array Type Plugins (SATPs), and Path Selection Plugins (PSPs).
o The VMware NMP supports all storage arrays listed on the VMware storage HCL and provides a default path selection algorithm based on the
array type.
o ESX offers an SATP for every type of array that VMware supports.
o By default, the VMware NMP supports the following PSPs:
o Most Recently Used (MRU)
o Fixed - with active-passive arrays that have a Fixed path policy, path thrashing might be a problem.
o Round Robin (RR) - Uses a path selection algorithm that rotates through all available paths enabling load balancing across the paths.
o Claim rules defined in the /etc/vmware/esx.conf file, the host determines which multipathing plugin (MPP) should claim the paths.
o By default, the host performs a periodic path evaluation every 5 minutes.
o Active multiple working paths currently used for transferring data are marked as Active (I/O). In ESX 3.5 or earlier, the term active means the
only path that the host is using to issue I/O to a LUN.
o Standby path is operational and can be used for I/O if active paths fail.
o If you created a virtual disk in the thin format, you can later inflate it to its full size.
o RDM offers several benefits. User-Friendly Persistent Names, Dynamic Name Resolution, Distributed File Locking, File Permissions, File System
Operations, Snapshots, vMotion, SAN Management Agents and N-Port ID Virtualization(NPIV).
o Certai
vcp 410
n limitations exist when you use RDMs:
o Not available for block devices or certain RAID devices.
o Available with VMFS-2 and VMFS-3 volumes only.
o No snapshots in physical compatibility mode.
o No partition mapping. It requires a whole LUN.

Hosts, clusters, and resources pools provide flexible and dynamic ways to organize the aggregated computing and memory resources in the virtual environment and link them back to the underlying physical resources.
A host represents the aggregate computing and memory resources of a physical x86 server. For example, if the physical x86 server has four dual-core CPUs runn
VCP-410 questions
ng at 4GHz each and 32GB of system memory, the host has 32GHz of computing power and 32GB of memory available for running virtual machines that are assigned to it.
A cluster acts and can be managed as a single entity. It represents the aggregate computing and memory resources of a group of physical x86 servers sharing the same network and storage arrays. For example, if the group contains eight servers with four dual-core CPUs each running at 4GHz and 32GB of memory. The cluster then has and aggregate 256GHz of computing power and 256GB of memory available for running virtual machines.
Resource pools are partitions of computing and memory resources from a single host or a cluster. Resource pools can be hierarchical and nested. You can partition any resource pool into smaller resource pools to further divide and assign resources to different groups or for different purposes.
Figure 4 illustrates the use of resource pools. Three x86 servers with 4GHz computing power and 16GB of memory each are aggregated to form a cluster of 12GHz computing power and 48GB of memory. The Finance Department resource pool reserves 8GHz of computing power and 32GB of memory from the cluster, leaving 4GHz computing power and 16GB of memory reserved for the other virtual machine. From the Finance Department resource pool, the smaller Accounting resource pool reserves 4GHz computing power and 16GB of memory for the virtual machines from the accounting department. That leaves 4GHz of computing power and 16GB of memory for the virtual machine called Payroll.

QUESTION NO: 451
If a virtual machine (VM) experiences a monitor panic, where does the ESX Server core
dump file get created?
A. in the core dump partition, if created
B. in the /home partition
C. in the same directory as the VM’s .vmx file
D. in the local VMFS volume

Answer: C

VCP-410 dumps
QUESTION NO: 452
Which three storage solutions are supported for the placement of a VMFS filesystem
during the installation of the ESX Server? (Choose Three.)
A. SCSI
B. SAN
C. ATA RAID
D. SCSI RAID
E. ATA

Answer: A,B,D

QUESTION NO: 453
For what reason would an ESX Server administrator send an end user a remote console
URL?
A. because remote console URLs are used to delegate administrative tasks performed on
the ESX service console
B. to go directly to the state of a specific virtual machine snapshot that can be resumed by
the end user with a Virtual Infrastructure (VI) Client
C. to provide a lightweight user interface to a virtual machine without a Virtual
Infrastructure (VI) Client
D. for quick access to a specific virtual machine from tPassed VCP-410 e Virtual Infrastructure (VI)
Client

Answer: C

VMware vSphere virtualizes the entire IT infrastructure including servers, storage, and networks.
VMware vSphere aggregates these resources and presents a uniform set of elements in the virtual environment. With VMware vSphere, you can manage IT resources like a shared utility and dynamically provision resources to different business units and projects.
Figure 3 shows the key elements in virtual datacenter.
Figure 3. Virtual Datacenter Architectu

VCP-410 exam re
You can use vSphere to view, configure, and manage these key elements. These elements include:
■

Computing and memory resources called hosts, clusters, and resource pools
■

Storage resources called datastores
■

Networking resources called networks
■

Virtual machines
A host is the virtual representation of the computing and memory resources of a physical machine running ESX/ESXi. When one or more physical machines are grouped together to work and be managed as a whole, the aggregate computing and memory resources form a cluster. Machines can be dynamically added or removed from a cluster. Computing and memory resources from hosts and clusters can be finely partitioned into a hierarchy of resource pools.
Datastores are virtual representations of combinations of underlying physical storage resources in the datacenter. These physical storage resources can come from the following:
■

Local SCSI, SAS, or SATA disks of the server
■

Fibre Channe
VCP-410 exam questions l SAN disk arrays
■

iSCSI SAN disk arrays
■

Network Attached Storage (NAS) arrays
Networks in the virtual environment connect virtual machines to one another and to the physical network outside of the virtual datacenter.
Virtual machines are designated to a particular host, cluster or resource pool, and a datastore when they are created. After they are powered-on, virtual machines consume resources dynamically as the workload increases or give back resources dynamically as the workload decreases.
Provisioning of virtual machines is much faster and easier than physical machines. New virtual machines can be created in seconds. When a virtual machine is provisioned, the appropriate operating system and applications can be installed unaltered on the virtual machine to handle a particular workload just as though they were being installed on a physical machine. A virtual machine can even be provisioned with the operating system and applications already installed and configured.
Resources get provisioned to virtual machines based on the policies set by the system administrator who owns the resources. The policies can reserve a set of resources for a particular virtual machine to guarantee its performance. The policies can also prioritize and set a variable portion of the total resou
VCP-410 study guide
rces to each virtual machine. A virtual machine is prevented from being powered-on and consuming resources if doing so violates the resource allocation policies. For more information on resource and power management, see the Resource Management Guide.

A typical VMware vSphere datacenter consists of basic physical building blocks such as x86 virtualization servers, storage networks and arrays, IP networks, a management server, and desktop clients.
This physical topology of the vSphere datacenter is illustrated in Figure 2.
Figure 2. VMware vSphere Datace
VCP-410 dumps
nter Physical Topology
The components that make up the vSphere datacenter topology are:
Computing servers

Industry standard x86 servers that run ESX/ESXi on the bare metal. ESX/ESXi software provides resources for and runs the virtual machines. Each computing server is referred to as a standalone host in the virtual environment. You can group a number of similarly configured x86 servers with connections to the same network and storage subsystems to provide an aggregate set of resources in the virtual environment, called a cluster.
Storage networks and arrays

Fibre Channel SAN arrays, iSCSI SAN arrays, and NAS arrays are widely used storage technologies supported by VMware vSphere to meet different datacenter storage needs. The storage arrays are connected to and shared between groups of servers through storage area networks. This arrangement allows aggregation of the storage resources and provides more flexibility in provisioning them to virtual machines.
IP networks

Each computing server can have multiple Ethernet network interface cards (NICs) to provide high bandwidth and reliable networking to the entire VMware vSphere datacenter.
vCenter Server

vCenter Server provides a single point of control to the datacenter. It provides essential datacenter services such as access control, performance monitoring, and configuration. It unifies the resources from the individual computing servers to be shared among virtual machines in the entire datacenter. It does this by managing the assignment of virtual machines to the computing servers and the assignment of resources to the virtual machines within a given computing server based on the policies that the system administrator sets.
Computing servers continue to function even in the unlikely event that vCenter Server becomes unreachable (for example, if the network is severed). They can be managed separately and continue to run the virtual machines assigned to them based on the resource assignment that was last set. After connection to vCenter Server is restored, it can manage the datacenter as a whole again.
Management clients

VMware vSphere provides several interfaces for datacenter management and virtual machine access. These interfaces include VMware vSphere Client (vSphere Client), web access through a web browser, vSphere Command-Line Interface (vSphere CLI), or vSphere Management Assistant (vMA).

QUESTION NO: 454
What is a requirement for enabling NIC teaming?
A. A physical NI
VCP-410 C is linked to multiple virtual switches
B. All physical NICs must be of the same type.
C. Multiple physical NICs are linked to a single virtual switch
D. All virtual NICs must be of the same type.

Answer: C

QUESTION NO: 455
Which of the following is a key feature of VMware High Availability services?
A. HA can VMotion Virtual Machines to surviving ESX servers.
B. HA can automatically restart Virtual Machines from a failed ESX server
C. HA can take the place of other cluster software, like Microsoft Cluster Services
(MSCS)
D. HA can automatically restart failed ESX Servers.

Answer: B
Explanation:
Only DRS will use VMotion to move Virtual Machines around to adjust to changes in
CPU/Memory performance on ESX servers.

QUESTION NO: 456
Which of the following are valid choices for optimizing performance of Virtual
Machines? (Choose Three.)

VCP-410 braindump
A. Disable unused devices such as COM ports, Floppy drives, and CD ROM drive.
B. Avoid installing vmware-tools on resource intensive virtual machines.
C. Defragment attached VMFS-3 volumes.
D. Tune and size virtual machine operating systems as you would on physical hosts.
E. Keep virtual machines that have similar resource requirements on the same host.

Answer: A,D,E

This topic introduces the components of VMware vSphere.
VMware vSphere includes the following components:
VMware® ESX and VMware® ESXi

VCP-410 exam questions

A virtualization layer run on physical servers that abstracts processor, memory, storage, and resources into multiple virtual machines.
Two versions of ESX are available:
■

VMware ESX 4.0 contains a built-in service console. It is available as an installable CD-ROM boot image.
■

VMware ESXi 4.0 does not contain a service console. It is available in two forms: VMware ESXi 4.0 Embedded and VMware ESXi 4.0 Installable. ESXi 4.0 Embedded is firmware that is built into a server’s physical hardware. ESXi 4.0 Installable is software that is available as an installable CD-ROM boot image. You install the ESXi 4.0 Installable software onto a server’s hard drive.
VMware® vCenter Server

The central point for configuring, provisioning, and managing virtualized IT environments.
VMware® vSphere Client

An interface that allows users to connect remotely to vCenter Server or ESX/ESXi from any Windows PC.
VMware® vSphere Web Access

A Web interface that allows virtual machine management and access to remote consoles.
VMware® Virtual Machine File System (VMFS)

A high performance cluster file system for ESX/ESXi virtual machines.
VMware® Virtual SMP

Feature that enables a single virtual machine to use multiple physical processors simultaneously.
VMware® VMotion and Storage VMotion

VMware VMotion enables the live migration of running virtual machines from one physical server to another with zero down time, continuous service availability, and complete transaction integrity. Storage VMotion enables the migration of virtual machine files from one datastore to another without service interruption. You can choose to place the virtual machine and all its disks in a single location, or select separate locations for the virtual machine configuration file and each virtual disk. The virtual machine remains on the same host during Storage VMotion.
Migration with VMotion - Moving a powered-on virtual machine to a new host. Migration with VMotion allows you to move a virtual machine to a new host without any interruption in the availability of the virtual machine. Migration with VMotion cannot be used to move virtual machines from one datacenter to another.
Migration with Storage VMotion - Moving the virtual disks or configuration file of a powered-on virtual machine to a new datastore. Migration with Storage VMotion allows you to move a virtual machine’s storage without any interruption in the availability of the virtual machine.
VMware® High Availability (HA)

Feature that provides high availability for applications running in virtual machines. If a server fails, affected virtual machines are restarted on other production servers that have spare capacity.
VMware® Distributed Resource Scheduler (DRS)

Feature that allocates and balances computing capacity dynamically across collections of hardware resources for virtual machines. This feature includes distributed power management (DPM) capabilities that enable a datacenter to significantly reduce its power consumption.

VCP-410 study guide

VMware® Consolidated Backup (Consolidated Backup)

Feature that provides a centralized facility for agent-free backup of virtual machines. It simplifies backup administration and reduces the impact of backups on ESX/ESXi performance.
VMware® vSphere SDK

Feature that provides a standard interface for VMware and third-party solutions to access the VMware vSphere.
VMware® Fault Tolerance

When Fault Tolerance is enabled for a virtual machine, a secondary copy of the original (or primary) virtual machine is created. All actions completed on the primary virtual machine are also applied to the secondary virtual machine. If the primary virtual machine becomes unavailable, the secondary machine becomes active, providing continual availability.
vNetwork Distributed Switch (DVS)

Feature that includes a distributed virtual switch (DVS), which spans many ESX/ESXi hosts enabling significant reduction of on-going network maintenance activities and increasing network capacity. This allows virtual machines to maintain consistent network configuration as they migrate across multiple hosts.
Host Profiles

Feature that simplifies host configuration management through user-defined configuration policies. The host profile policies capture the blueprint of a known, validated host configuration and use this to configure networking, storage, security, and other settings across multiple hosts. The host profile policies also monitor compliance to standard host configuration settings across the datacenter. Host profiles reduce manual steps involved in configuring a host and can help maintain consistency and correctness across the datacenter.
Pluggable Storage Array (PSA)

VCP-410 questions

A storage partner plug-in framework that enables greater array certification flexibility and improved array-optimized performance. PSA is a multipath I/O framework allowing storage partners to enable their array asynchronously to ESX release schedules. VMware partners can deliver performance-enhancing multipath load-balancing behaviors that are optimized for each array.