FusionCompute installation has clear host hardware and configuration requirements defined in the HCIA syllabus.
OptionAis true. The boot device must match the installation location of the host operating system to ensure system stability.
OptionCis true.CPU virtualization must be enabledin the BIOS (Intel VT-x or AMD-V). If not enabled, the host cannot run virtual machines, which is a mandatory prerequisite.
OptionDis true. FusionComputecan be installed with a single network interface, although this is not recommended for production environments. Multiple NICs are preferred for traffic separation and high availability.
OptionBis false. The host where theVRM is deployed has higher disk requirementsthan ordinary compute nodes because it runs management services, databases, and logs. Therefore, its disk requirements arenot the sameas other compute nodes.
Thus, the false statement isB.

In the official Huawei HCIA-Cloud Computing curriculum, the OS is described as the bridge between hardware and software, with the kernel serving as its most critical component. The statement is TRUE because the kernel acts as the core manager of all physical resources, including the CPU, memory, and I/O devices. When an upper-layer application needs to perform a task-such as reading a file from a disk or sending data over a network-it cannot access the hardware directly. Instead, it must send a request to the kernel through a System Call Interface.
The kernel operates in a protected "Kernel Mode," while applications run in "User Mode." This separation ensures system stability and security. By managing resource scheduling, the kernel ensures that multiple applications can run concurrently without interfering with each other's memory space or crashing the entire system. In a virtualization context, the role of the kernel becomes even more significant. For instance, in Huawei's KVM-based virtualization, the Linux kernel itself is transformed into a Hypervisor. The kernel's ability to manage CPU and memory is extended to create virtualized versions of these resources for Virtual Machines (VMs).
The Huawei training documentation highlights that the efficiency of the kernel directly impacts the performance of the cloud platform. Because the kernel handles process management, memory allocation, and the file system, any optimization at the kernel level results in better VM density and lower latency for cloud services. Therefore, understanding the kernel's role as both a resource manager and a provider of the system call interface is fundamental for any ICT associate working with Huawei FusionCompute or FusionAccess solutions.

In the "Virtualization Basics" section of the Huawei HCIA-Cloud Computing training material, the taxonomy of virtualization components is strictly defined. Statement C is FALSE because the virtualization software layer is technically called the Hypervisor or Virtual Machine Monitor (VMM), not the "Host OS." While a
"Host OS" exists in Type-2 (hosted) virtualization (where the hypervisor runs as an application on top of an existing OS like Windows or Linux), the software layer that actually performs the resource abstraction and logical partitioning is the Hypervisor itself.
The other definitions are central to Huawei's technical documentation. AGuest OS(Statement A) is indeed the operating system-such as Windows Server or Ubuntu-that is installed inside a Virtual Machine. It is
"unaware" that it is running on virtual hardware. TheHost Machine(Statement B) refers to the underlying physical server (e.g., a Huawei FusionServer Pro) that provides the actual CPU, RAM, and physical NICs.
Finally, aGuest Machine(Statement D) is a synonym for a Virtual Machine (VM), representing the logical container that houses the Guest OS and applications.
In a Type-1 virtualization architecture (like HuaweiFusionCompute), the Hypervisor (CNA) sits directly on the hardware. In this scenario, there is no "Host OS" at all, further proving why statement C is incorrect. The Hypervisor is responsible for trapping "privileged instructions" from the Guest OS and translating them into actions on the physical hardware. Correctly identifying these roles-Host Machine, Hypervisor, and Guest VM-is a prerequisite for understanding more advanced cloud features like Resource Clusters and Distributed Resource Scheduling (DRS).

Quick provisioning using alinked clone templateis designed to rapidly deploy desktops while ensuring standardization and automation.
According to HCIA-Cloud Computing FusionAccess service provisioning procedures, the quick provision workflow includes:
* Creating the VMbased on the linked clone template and snapshot.
* Renaming the VMto meet enterprise naming rules.
* Adding the VM to the domain, enabling centralized authentication and policy control.
* Associating the VM with a user or user group, which determines desktop assignment and access permissions.
All listed operations are integral steps in the linked clone quick provisioning process. Therefore,all options are correct.

In the official Huawei HCIA-Cloud Computing curriculum, specifically within the "Huawei Virtualization Platform Management" module, the lifecycle and resource adjustment of Virtual Machines (VMs) are covered in detail. While virtualization provides significant elasticity, certain physical-to-logical mappings have technical constraints. According to the training materials, while you can add disks or increase the capacity of an existing virtual disk (expansion), disk capacity cannot be reduced once it has been allocated and formatted by the Guest Operating System.
The reason for this limitation is rooted in data integrity. Reducing a disk's size at the virtualization layer (CNA
/VIMS) would involve "chopping off" the end of the logical block range. Since the Guest OS manages the file system and may have placed metadata or data at the end of that range, shrinking the disk from the outside would almost certainly result in file system corruption and data loss. Therefore, Huawei FusionCompute does not provide a "shrink" function for virtual disks. If a user needs a smaller disk, they must create a new, smaller disk and migrate the data at the application level.
In contrast, other resources offer more flexibility. NIC quantities (A) can be reduced by deleting a virtual network adapter from the VM configuration. CPU resources (C) and Memory resources (D) can be adjusted in the VM settings; while increasing them is common, they can also be reduced (typically requiring a VM restart to allow the Guest OS to re-initialize the hardware map). This distinction is a key exam point: compute resources are elastic in both directions (with reboot), but storage capacity in FusionCompute is strictly
"expand-only" to protect user data.