VCP DCV 6 Exam (Latest Update) Questions and Verified
Answers| 100% Correct| Grade A+
4. vCenter server appliance w/ external platform services controller - ANSWER-install controller on one
vm/host and vcenter on another vm/host. can be shared. great for large environments
4. platform services controller - enhanced link mode - ANSWER-without HA. platform services controller
on seperate vm joined to vcenter servers thru domain. With HA, 2 controllers on 2 vms behind a load
balancer, vcenter joined using shared lb IP address. embedded configurations not generally
recommended.
4. vCenter Appliance limitations - ANSWER-same as windows. 1000 host per vCenter system, 10,000
powered on VMs, 64 hosts per cluster. 8k VM per cluster. oracle/postgresSQL. linked mode = yes
4. License Service - ANSWER-Part of platform services controller. centralized license management
andreport functionality in vsphere. Provides inventory for licnense
4. deploying vCenter considerations - ANSWER-ensure requirements met, prepare vcenter server db,
first deploy platform services controller and then vcenter server. (unless embedded, then happens
auto). provide FQDN or static IP of host machine. make sure all machines in vsphere network are synced.
its an .iso image w/ vcsa folder, client plug-in, command line, UI deployment webpage
4. Vcenter setup - ANSWER-target server, deployment type, single sign-on, appliance size, select
datastore, config db, network settings.
vCenter login - ANSWER-https://applianceIP_or_FQDN/vsphere-client
4. virtual data center - ANSWER-container for all inventory objects required for fully functional
envirironment. can creaet multiple, has own hosts, vms, templates, datastores, networks. objects have
minimal interraction between datacenters. ie. vmotion not allowed across data centers.
4. root object - ANSWER-vCenter Server system. It cannot be removed from inventory.
4. vpxuser - ANSWER-auto created user for vm's,
,4. lockdown mode - ANSWER-disables remote access for the account ensuring host only managed thru
vcenter.
4. tags - ANSWER-label you can apply to objects in vsphere inventory. you create tag and assign to
category.
5. Virtual Switch Types (2) - ANSWER-Virtual Machine port groups - connect vm's to physical network;
vmkernel port - connect services to physical network. i.e. IP storage, vMotion, managment network
5. Management Network port - ANSWER-Vmkernal port, connects servides like vsphere. each vmkernal
port must have own ip, netmask and gateway.
5. port groups - ANSWER-help configure switches. templates that store switch port configs. connect vm's
with common networking properties
5. uplink ports - ANSWER-port groups/vmkernel ports connect to outside world thru physical ethernet
adapters connected to these virtual uplinks.
5. virtual switch connection examples (2) - ANSWER-all networks on one switch with teaming/VLANS or
each port group can its own network (this requires more physical adapters) . All ports/groups defined
for switch share the same hardware.
5. Virtual Switch Types (2) - ANSWER-standard - switch config at host-level. distributed - provide
consistent network config for vms as they migrate hosts.
5. standard switch - ANSWER-provides connections for vm's to communicate w/ each other on same/diff
host. slide 5-10 good.
5. VLAN - ANSWER-allows logical groupings as if all VMs on the same network. improved performance.
cost savings (partition network without new routers)
, 5. trunk port - ANSWER-esxi host must be on trunk port on switch. trunk port accepts vlan ID. VM doesnt
know its on a VLAN.
5. physical adapers - ANSWER-vmnic0, vmnic1, etc... can become bottleneck if speed doesn't match
specs.
5. network/port switch policies - ANSWER-at switch level you can configure security, traffic shaping, NIC
teaming/failover. You can also do this at port group level which supersedes the switch-level
5. Security policy configurations (3) - ANSWER-promiscous - present all traffic regardless of destination.
set to ACCEPT if need to run sniffer on a VM guest. MAC address changes - accept/reject inbound traffic
when MAC address has been altered. Forge transmits - accept/reject outbound traffic when its been
altered by guest. ALL ARE SET TO REJECT BY DEFAULT.
5. traffic shaping - ANSWER-limits VM consumption of available bandwidth. average rate, peak rate and
burst are configurable. only works with outbound traffic. for inbound use load balancer or features on
the router. Off by default.
5. nic teaming and failover - ANSWER-determine how traffic is distributed between adapers
5. Load Balance method: originating virtual port ID - ANSWER-vms outboud traffic is mapped to specific
phsyican NIC
5. Load Balance method: Source MAC Hash - ANSWER-sent to physical nic based on vnics MAC. not even
across physical nics.
5. Load Balance method: Source & Dest IP Hash - ANSWER-required link aggregation. several ethernet
links into one high speed fault tolerant one that can share bandwidth across adapters. vm can send to 2
diff clients from 2 diff nics.
5. failback - ANSWER-Yes, then as soon as adapter is available after failure it comes back. No, it remains
offline.
Answers| 100% Correct| Grade A+
4. vCenter server appliance w/ external platform services controller - ANSWER-install controller on one
vm/host and vcenter on another vm/host. can be shared. great for large environments
4. platform services controller - enhanced link mode - ANSWER-without HA. platform services controller
on seperate vm joined to vcenter servers thru domain. With HA, 2 controllers on 2 vms behind a load
balancer, vcenter joined using shared lb IP address. embedded configurations not generally
recommended.
4. vCenter Appliance limitations - ANSWER-same as windows. 1000 host per vCenter system, 10,000
powered on VMs, 64 hosts per cluster. 8k VM per cluster. oracle/postgresSQL. linked mode = yes
4. License Service - ANSWER-Part of platform services controller. centralized license management
andreport functionality in vsphere. Provides inventory for licnense
4. deploying vCenter considerations - ANSWER-ensure requirements met, prepare vcenter server db,
first deploy platform services controller and then vcenter server. (unless embedded, then happens
auto). provide FQDN or static IP of host machine. make sure all machines in vsphere network are synced.
its an .iso image w/ vcsa folder, client plug-in, command line, UI deployment webpage
4. Vcenter setup - ANSWER-target server, deployment type, single sign-on, appliance size, select
datastore, config db, network settings.
vCenter login - ANSWER-https://applianceIP_or_FQDN/vsphere-client
4. virtual data center - ANSWER-container for all inventory objects required for fully functional
envirironment. can creaet multiple, has own hosts, vms, templates, datastores, networks. objects have
minimal interraction between datacenters. ie. vmotion not allowed across data centers.
4. root object - ANSWER-vCenter Server system. It cannot be removed from inventory.
4. vpxuser - ANSWER-auto created user for vm's,
,4. lockdown mode - ANSWER-disables remote access for the account ensuring host only managed thru
vcenter.
4. tags - ANSWER-label you can apply to objects in vsphere inventory. you create tag and assign to
category.
5. Virtual Switch Types (2) - ANSWER-Virtual Machine port groups - connect vm's to physical network;
vmkernel port - connect services to physical network. i.e. IP storage, vMotion, managment network
5. Management Network port - ANSWER-Vmkernal port, connects servides like vsphere. each vmkernal
port must have own ip, netmask and gateway.
5. port groups - ANSWER-help configure switches. templates that store switch port configs. connect vm's
with common networking properties
5. uplink ports - ANSWER-port groups/vmkernel ports connect to outside world thru physical ethernet
adapters connected to these virtual uplinks.
5. virtual switch connection examples (2) - ANSWER-all networks on one switch with teaming/VLANS or
each port group can its own network (this requires more physical adapters) . All ports/groups defined
for switch share the same hardware.
5. Virtual Switch Types (2) - ANSWER-standard - switch config at host-level. distributed - provide
consistent network config for vms as they migrate hosts.
5. standard switch - ANSWER-provides connections for vm's to communicate w/ each other on same/diff
host. slide 5-10 good.
5. VLAN - ANSWER-allows logical groupings as if all VMs on the same network. improved performance.
cost savings (partition network without new routers)
, 5. trunk port - ANSWER-esxi host must be on trunk port on switch. trunk port accepts vlan ID. VM doesnt
know its on a VLAN.
5. physical adapers - ANSWER-vmnic0, vmnic1, etc... can become bottleneck if speed doesn't match
specs.
5. network/port switch policies - ANSWER-at switch level you can configure security, traffic shaping, NIC
teaming/failover. You can also do this at port group level which supersedes the switch-level
5. Security policy configurations (3) - ANSWER-promiscous - present all traffic regardless of destination.
set to ACCEPT if need to run sniffer on a VM guest. MAC address changes - accept/reject inbound traffic
when MAC address has been altered. Forge transmits - accept/reject outbound traffic when its been
altered by guest. ALL ARE SET TO REJECT BY DEFAULT.
5. traffic shaping - ANSWER-limits VM consumption of available bandwidth. average rate, peak rate and
burst are configurable. only works with outbound traffic. for inbound use load balancer or features on
the router. Off by default.
5. nic teaming and failover - ANSWER-determine how traffic is distributed between adapers
5. Load Balance method: originating virtual port ID - ANSWER-vms outboud traffic is mapped to specific
phsyican NIC
5. Load Balance method: Source MAC Hash - ANSWER-sent to physical nic based on vnics MAC. not even
across physical nics.
5. Load Balance method: Source & Dest IP Hash - ANSWER-required link aggregation. several ethernet
links into one high speed fault tolerant one that can share bandwidth across adapters. vm can send to 2
diff clients from 2 diff nics.
5. failback - ANSWER-Yes, then as soon as adapter is available after failure it comes back. No, it remains
offline.
