“The newly attached block storage device can be used only after it is formatted.”
[Lab Guide, storage exercise] The lab shows formatting with mkfs -t ext4 /dev/vdb, mounting the filesystem, and setting /etc/fstab for automatic mounting.
[The partition-table distinction is also supported by official EVS documentation. ]
Huawei source: Lab Guide PDF p. 125; Training PDF EVS section; official EVS docs
Technical Deep Dive
A newly attached EVS block device generally needs initialization before it can be used as a new filesystem. Option A is true: MBR and GPT partition styles can be used for smaller disks, while GPT is needed for capacities beyond MBR's practical approximately two-TiB limit. Option B is true: on Linux, an initialized disk can be mounted using the mount command, and persistent mounting is typically configured through /etc/fstab using a stable filesystem UUID.
Option C is false. Windows supports both MBR and GPT partition tables. NTFS, FAT and exFAT are filesystem formats, not replacements for partition-table standards. Treating a filesystem type as a partition style is a fundamental storage-administration error. Option D is true: Linux tools such as fdisk and parted can create partitions, and commands such as mkfs.ext4 create filesystems on the appropriate block device or partition.
The Huawei V3.5 Lab Guide shows formatting and mounting a newly attached disk, including configuring persistent mounting. A safe production workflow is to identify the disk with lsblk, verify it contains no required data, create an appropriate GPT partition if needed, format it and mount it to a chosen directory. Formatting or changing a partition table destroys existing data, so the target device must be checked carefully. For Windows, administrators use Disk Management or appropriate PowerShell commands to initialize a disk with MBR or GPT and format a volume using NTFS or another supported filesystem. Answer C is unambiguously incorrect.
Technical commands / calculations from the reviewed batch
# Destructive: use ONLY for a confirmed new empty disk.
lsblk
sudo parted /dev/vdb --script mklabel gpt
sudo parted /dev/vdb --script mkpart primary 1MiB 100%
sudo mkfs.ext4 /dev/vdb1
sudo mkdir -p /data
sudo mount /dev/vdb1 /data
df -Th