Huawei H13-811_V3.5 Exam Questions

All four categories form part of Huawei Cloud's layered security architecture. Network security includes controls and services designed to protect network boundaries and traffic, such as Anti-DDoS, Advanced Anti-DDoS, VPC security controls, firewalls, and network isolation. Huawei Cloud describes network security as a core component of its full-stack cloud defense model.

Application security protects web applications and application-layer traffic. Representative Huawei Cloud services include Web Application Firewall, which detects and blocks HTTP/HTTPS attacks, and application vulnerability/security capabilities.

Computing security covers server and workload protection. Host Security Service protects ECS and other server workloads through vulnerability management, intrusion detection, account-security controls, malware detection, and web tamper protection. Security-management capabilities such as Cloud Bastion Host and centralized security operations provide access management, authentication, authorization, auditing, and operational control.

Finally, data security encompasses encryption, database protection, identity/access control, sensitive-data protection, and lifecycle safeguards. Huawei's security architecture explicitly identifies protection of confidentiality, integrity, availability, durability, and traceability as data-security objectives.

Therefore, A, B, C, and D are all included.

Reference topics: Huawei Cloud Security Architecture; Network Security; Application Security; Compute Security; Security Management; Data Security.

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

Option A is incorrect because Huawei Cloud Auto Scaling is designed to automatically adjust ECS instances and bandwidth resources, not Bare Metal Server instances. Huawei's AS documentation defines an AS group as a collection of ECS instances and states that scaling actions add or remove ECS instances according to alarm, scheduled, or periodic policies. BMS provides dedicated physical compute and is provisioned through the BMS service rather than being dynamically created and destroyed by an ECS Auto Scaling group.

The other relationships are valid. Cloud Eye supports BMS operating-system monitoring after the Cloud Eye Agent is installed; the BMS reports detailed CPU, memory, disk, and network metrics to Cloud Eye. EVS is integrated with BMS and additional supported EVS data disks can be attached when more storage is required. IMS is likewise an integral BMS service: images can be used to create consistently configured BMSs and to reinstall or change their operating systems, reducing repetitive deployment work. Huawei's BMS architecture explicitly lists VPC, IMS, EVS, Cloud Eye, and backup services as integrations supporting BMS operation.

Reference topics: Bare Metal Server Architecture; BMS and Other Cloud Services; Auto Scaling; Cloud Eye; IMS; EVS.

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

The statement is FALSE because the management tracker used for general cloud-resource auditing does not need to be created manually when CTS is first enabled. Huawei Cloud explicitly states that when CTS is enabled for the first time, a management tracker named system is created automatically.

The management tracker identifies and associates with the cloud services used by the account and records management operations, including resource creation, modification, query, login-related actions, and deletion. Therefore, the portion of the statement saying that the user must manually create the tracker is technically incorrect.

Huawei does allow users to create additional data trackers manually. These trackers are specifically designed to record operations performed on data in OBS buckets, such as uploads and downloads. That is different from the automatically created management tracker.

Huawei's official getting-started workflow is explicit: open CTS, choose Enable CTS, and the system automatically creates the management tracker named system. Configuration such as OBS or LTS trace transfer can then be added if long-term retention is required.

Therefore, enabling CTS is necessary, but manually creating its primary management tracker is not.

Reference topics: Cloud Trace Service; Management Tracker; Data Tracker; Enabling CTS.

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

Option C is incorrect under the HCIA-Cloud Service V3.5 networking model. Huawei Cloud's V3.5-era VPC documentation differentiates the two access-control mechanisms by their scope and rule behavior: security groups protect cloud server instances and use allow rules, whereas network ACLs protect subnets and support both allow and deny rules. Therefore, the statement that both mechanisms support both rule actions is inconsistent with the curriculum version used by this examination.

Option A is correct because a network ACL is associated with one or more subnets and controls traffic entering or leaving those subnets. Option D is also correct because security groups provide instance-level access control for resources such as ECSs. Huawei describes a security group as a collection of traffic-control rules applied to instances sharing common security requirements.

Option B is technically correct because these mechanisms can be layered. A security group provides access control around ECS instances, while a network ACL adds another security-control boundary around the subnet. Huawei specifically recommends using them together where comprehensive or fine-grained network protection is required.

Reference topics: Security Groups; Network ACLs; VPC Access Control; Defense-in-Depth.

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

KooSearch is the Huawei Cloud service specifically designed to provide enterprise-grade search capabilities with an out-of-the-box service model. Huawei Cloud describes KooSearch as a one-stop intelligent enterprise search solution built on Cloud Search Service (CSS). It enables organizations to construct enterprise search, knowledge retrieval, AI search, and document Q&A applications without having to independently build the underlying search infrastructure. The service integrates enterprise knowledge sources, search models, vector search capabilities, and other components required for enterprise information retrieval.

This directly corresponds to the question's description of an out-of-the-box search service designed for enterprise digitalization. Huawei's current KooSearch documentation explicitly emphasizes its ready-to-use enterprise search and RAG capabilities. KooPhone is associated with cloud-phone capabilities, KooMessage concerns enterprise messaging and communication, and KooMap provides map-related services; none is the dedicated enterprise search offering.

Therefore, KooSearch is the only technically valid choice. This aligns with the HCIA-Cloud Service domain covering Huawei Cloud platform and other value-added cloud services.

Reference topics: KooSearch Service Overview; Cloud Search Service; Huawei Cloud PaaS/aPaaS Services.

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