FusionAccess consists of multiple components, each with different roles and data persistence requirements.

WI (Web Interface)stores configuration and user access information and supports backup.

VLB (Virtual Load Balancer)maintains configuration data that can be backed up.

vAG (Virtual Access Gateway)also stores configuration-related data that supports backup and recovery.

TheLicensecomponent, however, isnot backed upas configuration or system data. Licensing information is typically re-imported or reactivated during recovery rather than restored from backup.

Therefore, the component that doesnothave backup data isLicense.

According to the Huawei HCIA-Cloud Computing curriculum, specifically the "FusionAccess Planning and Deployment" section, the statement is TRUE. When an enterprise scales its desktop cloud across multiple regions or deploys separate FusionAccess environments (each with its own ITA/HDC/DB set), there is often a requirement to share a single license pool to optimize costs and management.

In a standard small-scale deployment, the License component is typically co-deployed with theITA (IT Adapter). However, if multiple independent FusionAccess systems (different clusters or management sets) need to draw from the same license file, the License component must be "de-coupled" from any specific ITA anddeployed independentlyas a standalone service. This standalone License Server acts as a centralized repository that tracks the total number of permitted desktop users or VMs. Each FusionAccess system is then configured to point to this central server's IP address.

This independent deployment model ensures that license seats are not "trapped" in one specific system. For example, if System A has 500 licenses but only 200 active users, and System B is at its limit, a centralized license server allows System B to utilize the excess capacity. This flexibility is a core architectural principle in Huawei’s large-scale VDI solutions. During deployment planning, administrators must decide whether to use a local license (co-deployed) or a centralized license (independent). For multi-system environments, the independent deployment is the official Huawei recommendation to ensure proper license reconciliation and to prevent "over-use" or "under-use" of purchased ICT assets across the enterprise.

====================

1-B, 2-A, 3-C, 4-D

According to the Huawei HCIA-Cloud Computing documentation, FusionAccess application policies are critical for tailoring the virtual desktop experience to specific security and performance requirements. The Huawei Desktop Protocol (HDP) management interface allows administrators to configure granular controls over data flow, display quality, and session behavior.

For Scenario 1, setting Clipboard Redirection to "Client to Server" ensures a one-way data flow. This allows users to copy text or files from their local physical client into the virtual machine (VM) while preventing the extraction of data from the VM back to the local device, thus protecting sensitive corporate information. In Scenario 2, the Display Policy Grade determines the balance between visual fidelity and network consumption. Grade 5 is the highest setting, designed for high-performance networks (25 Mbit/s or higher), and is optimized for server-side video decoding to provide the best possible playback quality.

Scenario 3 addresses security during periods of inactivity. By enabling the "Automatic Screen Lock" under the Session policy, the system monitors user input and automatically secures the desktop if no activity is detected within the specified interval (such as 10 minutes), preventing unauthorized access to an unattended terminal. Finally, Scenario 4 utilizes File Redirection to control external hardware access. By setting this policy to "Read-only" and enabling "Client Removable Driver," users can view and open files stored on their local USB flash drives within the VM environment but are strictly prohibited from saving or modifying any data back onto those physical devices. These configurations demonstrate the robustness of Huawei’s VDI policy engine in balancing user productivity with stringent security protocols.

FusionAccess OA security architecture adoptszone-based isolation(red, yellow, green zones).

Each zone islogically and physically isolated

Each zone has itsown FusionAccess system

Data is not allowed to flow freely between zones

OptionBis false because it incorrectly states that data can be transmitted between zones. The other statements correctly reflect FusionAccess OA security and integration characteristics.

According to the official Huawei FusionAccess installation and configuration guidelines, the process of creating a Windows VM template is highly structured to ensure compatibility with the Huawei Desktop Protocol (HDP). During the template making process—specifically when using the Huawei Desktop Preparation Tool—the system requires the use of a specific temporary account named PrivateAccount.

ThePrivateAccountis a built-in temporary administrative account used by the Huawei automation scripts to perform system-level tasks during the "encapsulation" phase. These tasks include installing the Access Agent, optimizing the operating system for a virtual environment (disabling unnecessary services like Windows Search or Aero effects), and configuring the registry to support remote login. This account is essential because it allows the system to operate independently of any domain-joined credentials or local administrator accounts that might be changed or locked during the preparation process.

In the HCIA-Cloud Computing curriculum, students are taught that the template creation workflow involves several steps: creating a bare VM, installing the Windows OS, installing drivers, and finally running the preparation tool. When the tool prompts for an account, the administrator must ensure thatPrivateAccountis used to maintain the integrity of the template. Once the template is successfully encapsulated and converted into a "Golden Image," this temporary account is typically deactivated or managed by the system to ensure security. Using a different account, such as a manually created "LocalAccount," may lead to errors during the automatic provisioning of desktops, as the FusionAccess management plane (ITA/HDC) specifically looks for the environment variables and permissions associated with the preset PrivateAccount during the initial boot of new clones.

In the official Huawei HCIA-Cloud Computing curriculum, specifically in the module "Huawei Virtualization Platform Management and Usage," the process for connecting hosts to storage is strictly defined. For storage types that rely on an Ethernet network (IP-based storage), such as IP SAN (iSCSI), NAS (NFS), and Huawei Distributed Block Storage (FusionStorage), the system requires the configuration of "Storage Ports" on each host. A storage port is a logical interface created on a physical NIC or a bond of NICs on a CNA (Computing Node Agent) node.

The reason this step is mandatory is that these storage protocols require an IP address to establish a session between the host (Initiator) and the storage device (Target). Without adding a storage port and assigning it a valid IP address within the storage network's segment, the host cannot communicate with the storage controllers. For IP SAN, this port is used to discover LUNs; for NAS, it is used to mount shared folders; and for Distributed Block Storage, it is used by the VNA (Virtual Node Agent) to communicate with the storage pool.

In contrast, forFC SANstorage, "storage ports" in the IP sense are not required because the Fibre Channel protocol uses World Wide Names (WWNs) on the Host Bus Adapters (HBAs) for identification. The Huawei documentation emphasizes that the storage network (Storage Plane) should be logically or physically isolated from the management and service planes to ensure high performance and security. Therefore, configuring storage ports with dedicated IPs is a prerequisite for creating a datastore on any IP-based storage backend in FusionCompute.

====================

Huawei FusionCompute implementsrole-based access control (RBAC)to ensure secure and compliant system management.

Thesecurity auditor roleis designed specifically for compliance and auditing purposes. According to HCIA–Cloud Computing materials, this role hasread-only permissions, allowing the user toview and export system logsbut not modify configurations or perform operational tasks.

This restriction helps ensure the integrity of audit records and prevents unauthorized system changes.

Therefore, the statement isTRUE.