VCP-DCV vSphere Security Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  To calculate workload distribution in DRS

  Why it's wrong here

  DRS balances workloads using host CPU and memory metrics and VM resource demand, not the Machine ID. It is tempting because DRS does track machine-level data, but the Machine ID identifies the vCenter Server appliance itself, not cluster workload placement.

• ✗

  To identify an ESXi host to vCenter Server

  Why it's wrong here

  ESXi hosts register with vCenter Server using their host UUID and SSL thumbprint, not the Machine ID. It is tempting because the Machine ID does identify an appliance to vCenter, but that appliance is the vCenter Server itself, not an ESXi host.

• ✓

  To serve as a unique identifier for the vCenter Server instance in SSO

  Why this is correct

  The Machine ID uniquely identifies each vCenter Server instance within the Single Sign-On domain, distinguishing it from other nodes during authentication and replication. This satisfies the requirement of a unique SSO identifier for the vCenter Server instance.

• ✗

  To uniquely identify a virtual machine for vMotion

  Why it's wrong here

  The Machine ID is a vCenter Server appliance identifier, not a virtual machine attribute, so it plays no part in vMotion. It is tempting because vMotion does require unique VM identity, but that identity comes from the VM's MoRef and BIOS UUID.

Go deeper

Related to this question