Verification warning: The supplied answer B directs host boot-volume activation after placing the guest in Configured state. F5 vCMP upgrade guidance requires checking host/guest compatibility, backups and controlled guest shutdown; the study guide predates TMOS 14.1. Source: F5 K14088 vCMP host/guest compatibility guidance.
Exact Extract — Source Status
Study Guide Exact Extract (vCMP architecture): “The vCMP host is the system-wide hypervisor that makes it possible for you to create, view, and manage all vCMP guests on the system.” F5 301a study guide, page 137. Specific BIG-IP 14.1 upgrade prerequisites require the official F5 host/guest compatibility reference.
Technical Deep Dive
A vCMP host maintains the physical BIG-IP software boot volumes, while the guest runs a separate virtualized BIG-IP instance. HD1.2 is already installed and has completed installation, but HD1.1 remains the active host boot location. The selected host boot volume is activated on the host—not inside the guest. The guest should be removed from service through the supported state transition before the host software activation; changing the guest to Configured stops guest execution and deallocates CPU/memory without removing existing virtual disks. This explains the intended B workflow. Check the BIG-IP host/guest version compatibility matrix before any upgrade: some version transitions require guest upgrades first. Back up the host and guest, verify a standby peer where available, activate HD1.2 from the host, and confirm that the guest returns to a supported state after the host restarts. Verification commands: tmsh list vcmp guest; tmsh show sys software status; tmsh list sys software image.
Relevant verification command: tmsh show sys software status
Technical verification note: A vCMP host upgrade and activation are controlled through the host boot-volume workflow; verify host and guest image/configuration selection before reboot.