EX200 Create simple shell scripts 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.

• ✓

  Create snapshot using lvcreate -s, Mount snapshot to a directory, Perform operations on snapshot, Unmount snapshot, Remove snapshot

  Why this is correct

  This is the correct order for using a logical volume snapshot. First create the snapshot, then mount it to access the data, perform operations (like backups), unmount when done, and finally remove the snapshot to free space.

• ✗

  Mount snapshot to a directory, Create snapshot using lvcreate -s, Perform operations on snapshot, Unmount snapshot, Remove snapshot

  Why it's wrong here

  This order fails at the outset because a logical volume snapshot is not an existing device until lvcreate -s has created it; mount only works against a valid block device path such as /dev/vg/origin-snap. Flipping the first two steps means the system cannot resolve the snapshot device, so the mount command returns an error and no subsequent snapshot operation can proceed. The snapshot must be created from the origin volume first, with the snapshot LV appearing as a separate device.

• ✗

  Create snapshot using lvcreate -s, Perform operations on snapshot, Mount snapshot to a directory, Unmount snapshot, Remove snapshot

  Why it's wrong here

  After lvcreate -s creates the snapshot, it exists as a block device, but performing file-level operations directly on that raw device without mounting it is incorrect; tools like tar, rsync, or find expect a mounted filesystem path, not a device node. Without a mount, you cannot traverse the filesystem's directory structure, and any raw write to the device would bypass journaling/filesystem layers and risk corrupting the snapshot data. Therefore mount the snapshot to a directory before attempting operations such as backups.

• ✗

  Create snapshot using lvcreate -s, Mount snapshot to a directory, Remove snapshot, Perform operations on snapshot, Unmount snapshot

  Why it's wrong here

  Removing the snapshot while it is still mounted fails in practice because lvremove detects the active logical volume and refuses to run while the device is in use, returning a volume is busy error. Placing Remove snapshot before Perform operations also contradicts the fact that operations require the snapshot to exist; once lvremove succeeds the snapshot device disappears, making later mounts or operations impossible. The only safe order is to mount, operate, unmount, and only then run lvremove to release the CoW space.

Go deeper

Related to this question