EX200 Configure local storage 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.

• ✗

  Setting the partition's UUID

  Why it's wrong here

  Setting the partition's UUID is not a valid action during partition creation because UUIDs are metadata generated by filesystem utilities such as mkfs or tune2fs, not by partition table tools like parted. On MBR disks, partitions have no UUID concept at all; even on GPT disks, the partition unique GUID is automatically assigned and not typically user-specified at creation time. Moreover, most Linux UUIDs (for mounting via fstab) refer to the filesystem UUID, which exists only after formatting, not partitioning.

• ✓

  Setting the partition's bootable flag

  Why this is correct

  Setting the partition's bootable flag is a valid operation when creating a partition with parted, as the 'set' command can toggle flags such as 'boot' on MBR partitions. This flag marks the partition as active, which is required for legacy BIOS booting to find the boot loader. It is purely a partition table attribute and does not affect the filesystem, so it can be done during or after partition creation without any formatting implications.

• ✓

  Setting the partition's name (GPT only)

  Why this is correct

  Setting the partition's name is valid only on GPT-partitioned disks because the GPT header includes a partition name field (often a UTF-16LE string) that MBR lacks. In parted, you can assign this name using the 'name' command right after creating the partition, and it is stored as metadata for human readability. Unlike a filesystem label, this name has no effect on mounting or device operation, but it is a legitimate option when creating a new GPT partition.

• ✗

  Mounting the partition to a directory

  Why it's wrong here

  Mounting the partition to a directory is not a partition creation step because mounting requires an existing block device with a valid filesystem on it. Partition tools like parted only define the partition table entries and disk layout; they do not and cannot mount devices. The correct workflow is to create the partition, format it with mkfs to create a filesystem, and then mount it separately using mount(8) or an /etc/fstab entry.

• ✓

  Setting the partition type (e.g., ext4)

  Why this is correct

  Setting the partition type (e.g., ext4) is a valid option when creating a partition with parted because the 'mkpart' command accepts a file system type parameter such as ext4, xfs, or linux-swap. However, note that this only sets the partition type code in the partition table (for MBR) or the 'type GUID' in the GPT; it does not actually format the partition. This is analogous to specifying the partition's intended use, and actual formatting must be done later with mkfs.

Go deeper

Related to this question