Huawei H13-811_V3.5 - HCIA-Cloud Service V3.5

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.

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

The statement is TRUE . Huawei Cloud distinguishes ordinary EVS disks from shared EVS disks . A standard non-shared EVS disk can normally be attached to only one server at a time, whereas a shared disk is specifically designed so that multiple supported servers can access the same block-storage device. Huawei documentation states that a shared EVS disk can be attached to multiple servers simultaneously, with supported implementations allowing attachment to as many as 16 servers.

The deletion requirement is equally explicit. A shared EVS disk cannot remain attached to any server when the disk itself is being deleted. Huawei requires administrators to detach the shared disk from all servers before deletion . If the disk is attached to several servers and is detached from only some of them, it remains in the In-use state. Only after it has been detached from every server does its state return to Available, permitting subsequent deletion operations.

Huawei additionally cautions that shared block storage does not itself provide cluster coordination. Appropriate cluster software or shared-file-system mechanisms must manage simultaneous reads and writes to prevent corruption.

Thus, both parts of the question precisely reflect Huawei Cloud's EVS shared-disk lifecycle requirements.

Reference topics: Shared EVS Disks; Attaching Shared Disks; Detaching EVS Disks; EVS Lifecycle Management.

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

1 → PaaS

2 → IaaS

3 → SaaS

The three mappings correspond directly to Huawei Cloud's definitions of the standard cloud service models. Infrastructure as a Service (IaaS) supplies foundational infrastructure resources such as compute, storage, and networking. Huawei Cloud services such as ECS, VPC, VPN, and OBS are representative infrastructure-level services. Therefore, the description referring to computers, storage devices, and networks maps to IaaS.

Platform as a Service (PaaS) provides managed platform capabilities used to develop, deploy, and operate applications. Huawei Cloud characterizes PaaS as including middleware, database platforms, development environments, microservice capabilities, and related application-platform resources. Consequently, the database/middleware/MySQL/MongoDB/Java-oriented description belongs to PaaS.

Software as a Service (SaaS) delivers complete applications to end users. Customers consume the application rather than maintaining the underlying operating system, middleware, runtime, and infrastructure. Enterprise applications, messaging systems, email services, collaboration applications, and similar ready-to-use software fit this model.

The correct progression is therefore PaaS → IaaS → SaaS for the three descriptions shown in the question.

Reference topics: Cloud Service Models; IaaS; PaaS; SaaS; Huawei Cloud Service Architecture.

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

Option A is the only sequence that respects the essential dependency chain for Huawei Cloud Log Tank Service host-log collection. A log group must exist before its log stream can be created , because a log stream is a subordinate storage and management unit within a log group. Huawei explicitly describes log groups and streams as the basic units used to manage logs and requires creation of the group before creation of its contained stream.

ICAgent is the host-side log collection component. It must be installed on the ECS before LTS can collect host log files according to configured paths and rules. After ICAgent is operational and the destination log stream exists, the administrator configures the relevant collection paths, parsing/collection rules, and ingestion configuration. ICAgent then packages and reports matching log records into the selected log stream.

Only after ingestion has been configured can the administrator reliably access LTS and view the collected logs for searching, analysis, monitoring, troubleshooting, or O & M.

The other alternatives violate basic dependencies by attempting to create a stream before its parent group, configuring collection before the required destination/agent exists, or installing ICAgent after collection configuration.

Reference topics: Log Tank Service; Log Groups; Log Streams; ICAgent; ECS Log Collection.

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

The supported notification methods represented in this question are SMS and email , so the correct selections are A and D .

Huawei Cloud CTS supports key event notification for significant operations. Administrators can identify operations that require immediate awareness and configure notification delivery through Simple Message Notification (SMN). When the configured key event occurs, CTS works with SMN to deliver the corresponding notification to subscribed recipients.

Huawei's official CTS documentation specifically states that SMN can send key-event messages to users' mobile phones or email addresses . A notification sent to a mobile phone in this context corresponds to SMS messaging. Email subscriptions similarly deliver the notification to the registered email endpoint.

This mechanism provides proactive visibility into sensitive cloud operations rather than requiring administrators to continually query CTS records. Typical use cases include monitoring resource deletion, security configuration changes, permission-related operations, or other high-risk administrative actions.

Neither WeChat nor a conventional phone call is identified by Huawei CTS as one of the notification methods in this key-event mechanism. Those options therefore do not satisfy the documented CTS notification workflow.

Reference topics: CTS Key Event Notification; Simple Message Notification; Operation Auditing; O & M Notifications.

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

Huawei Cloud establishes a clear parent-child relationship between a Huawei Cloud account and the IAM users created under that account. The account owns the cloud resources and is the billing entity , whereas IAM users consume or manage resources according to permissions assigned by the account administrator.

Therefore, option C is correct: IAM users do not independently pay for the resources they use. Charges generated through their authorized operations are billed to the parent account. Options B and D are also correct because the account administrator retains authorization control and can modify or revoke permissions assigned to IAM users.

Option A is incorrect because it incorrectly treats the IAM user as a payment entity. Authorization determines what an IAM user is permitted to access or operate , not who is responsible for payment. Huawei Cloud explicitly distinguishes resource ownership and billing from delegated resource access. An IAM user does not receive an independent bill merely because access to a resource has been authorized.

Accordingly, the correct relationship is: account owns and pays; IAM users operate resources according to delegated permissions; the account controls those permissions .

Reference topics: IAM Users; Huawei Cloud Accounts; IAM Authorization; Billing Responsibility.

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

Options B, C, and D identify problems that CDN architecture is designed to mitigate. Huawei defines CDN as an intelligent virtual network built on Internet infrastructure that caches origin content on geographically distributed points of presence close to users. This substantially shortens the network path between users and frequently requested resources.

Consequently, CDN improves download speed because users can retrieve cached files from a nearby edge PoP rather than repeatedly crossing long-distance networks to the origin server. It also addresses slow website access by accelerating static content delivery, reducing latency, and improving site response and availability. Huawei specifically states that CDN breaks through bottlenecks associated with limited bandwidth, high access traffic, and uneven network-node distribution.

Caching popular content at edge nodes also reduces repeated traffic flowing through core and backbone networks. This alleviates bandwidth pressure on both the origin infrastructure and long-distance network paths.

Option A is not a CDN problem statement. CDN commonly reduces origin-server load , meaning utilization of origin resources may decrease rather than fixing a problem described as “low server utilization.” Its purpose is acceleration and traffic offloading, not increasing server utilization.

Therefore, B, C, and D are correct.

Reference topics: Content Delivery Network; Edge Caching; Website Acceleration; Download Acceleration; Origin Traffic Reduction.

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

Option A is false because deleting historical object versions is not required before versioning can be suspended. Huawei Cloud states that once versioning has been enabled, it cannot revert to the original Disabled state, but it can be suspended. Existing historical versions remain stored in OBS after suspension and may be manually deleted later only if they are no longer required.

Option B is correct. When versioning is enabled, OBS automatically assigns a unique version ID to newly uploaded versions. Objects with identical names are retained as separate object versions distinguished by those IDs.

Option C is also correct. Huawei explicitly supports configuration of OBS versioning through the OBS Console, APIs, and SDKs.

Option D is correct because versioning is disabled by default for newly created buckets. It must be explicitly enabled if the customer wants multiple versions retained instead of allowing a newly uploaded namesake object to replace the current object.

Therefore, A incorrectly adds a prerequisite that Huawei does not impose for suspending versioning.

Reference topics: OBS Versioning; Version IDs; Suspending Versioning; Historical Object Versions.

Statements B and C are false . Huawei Cloud distinguishes alarm-based, scheduled, and periodic Auto Scaling policies. An alarm policy triggers a scaling operation in response to monitored metrics such as CPU utilization. Scaling “every three hours” is time-interval behavior and therefore belongs to a periodic policy , not an alarm policy. This makes B incorrect.

Statement C is also incorrect. The expected number of instances is the desired number of ECS instances that should currently run within an AS group. Huawei specifies that this value must remain between the configured minimum and maximum instance counts. It can be modified manually or changed through scheduled, periodic, or alarm-based policies. It is not synonymous with the minimum instance count during peak hours.

Statement A is valid because an AS configuration can use a Huawei Cloud public image; Huawei's AS configuration parameters explicitly support public, private, and shared images.

Statement D is also valid. Huawei specifies that when an existing ECS is manually added to an AS group, the ECS must not already be a member of another AS group .

Consequently, the two false statements are B and C .

Reference topics: Auto Scaling Configurations; AS Policies; Expected Instances; AS Groups.

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