2.3 - VM images, snapshots and conversions
Cloud+ CV0-004 objective 2.3 covers preparing and moving virtual machines. Converting a running physical server into a virtual machine image is known as P2V (physical-to-virtual), useful when migrating legacy hardware into the cloud. Migrating a VM from one hypervisor platform to a different one is V2V (virtual-to-virtual). A snapshot is a point-in-time copy of a volume you can restore or roll back to, handy before a risky change - though snapshots are not a substitute for backups. A golden image is a preconfigured, hardened base image used to launch consistent new instances, so every server starts from the same known-good state. Expect scenario questions that describe converting hardware, moving between hypervisors, capturing a restore point, or standardising new instances, and ask which technique - P2V, V2V, snapshot or golden image - is being described.
Physical server to VM image = P2V. VM between different hypervisors = V2V. Point-in-time volume copy to roll back = snapshot (not a backup). Hardened base image for consistent instances = golden image.
Practice questions
1. Converting a running physical server into a virtual machine image is known as:
- V2V
- P2V (correct answer)
- V2P
- P2P
P2V (physical-to-virtual) captures a physical machine into a VM. V2V moves between hypervisors; V2P goes back to physical.
2. A point-in-time copy of a volume you can restore or roll back to is a:
- Template
- Snapshot (correct answer)
- Golden image
- Manifest
A snapshot captures a volume's state at a moment for quick rollback. A golden image is a preconfigured base image for new instances; a template describes resources.
3. A preconfigured, hardened base image used to launch consistent new instances is a:
- Snapshot
- Manifest
- Golden image (correct answer)
- Route table
A golden image is a standardized, patched base image cloned to launch identical instances quickly. A snapshot is a point-in-time volume copy used mainly for rollback.
4. Migrating a VM from one hypervisor platform to a different one is known as:
- P2V
- V2V (correct answer)
- V2P
- P2P
V2V (virtual-to-virtual) moves a VM between hypervisors or formats. P2V captures a physical machine into a VM; V2P converts a VM back to physical hardware.
5. A logically isolated private network you define within a public cloud account is a:
- Subnet
- Route table
- VPC (correct answer)
- Peering link
A VPC (virtual private cloud) is your isolated virtual network in the provider, containing subnets, route tables and gateways. A subnet is a slice of the VPC's address range.
6. After a P2V conversion a VM will not boot. The most likely first thing to check is:
- The billing cost tags
- Missing or wrong drivers (correct answer)
- The public DNS records
- The nightly backup schedule
After P2V the guest often lacks the virtual hardware drivers (storage, chipset), causing boot failure; installing the hypervisor's guest tools usually fixes it. Billing tags never affect boot.