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.

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

1 → B

2 → C

3 → A

The mappings follow Huawei Cloud's LTS architecture exactly. A log group is the fundamental management unit used by LTS to organize logs. Huawei defines a log group as the basic unit for managing logs; it can contain multiple log streams and is primarily an organizational container rather than the location from which individual log records are read or written.

A log stream is the basic unit for reading and writing log data. Different categories of logs can be stored in separate streams within the same group, which improves log classification, searching, analysis, and O & M management.

ICAgent is the collection component. Huawei explicitly describes ICAgent as a log collection tool for LTS that runs on hosts from which logs need to be collected, including ECSs and physical servers. LTS distributes collection configurations to ICAgent, and ICAgent detects matching log files and reports the records to the specified log stream.

Therefore, the correct relationship is Log stream → read/write; ICAgent → collection; Log group → management .

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

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

Statements B and C are correct . Huawei Cloud Eye supports batch creation of monitoring alarms. Huawei's documented quota specifically states that up to 50 monitored objects can be selected when creating an alarm rule and that up to 1,000 alarm rules can be created at one time . Huawei even provides the exact example used here: 50 monitored objects multiplied by 20 metrics produces 1,000 alarm rules. Therefore, B is directly supported.

Statement C is also valid. Cloud Eye alarm rules can provide monitoring triggers used with Auto Scaling. An alarm-based AS policy references a Cloud Eye alarm rule; when monitored metrics meet the configured threshold condition, the corresponding scaling action can be initiated.

Statement A is false because Cloud Eye server monitoring is not limited to OS-level resource metrics. With the Agent installed, Huawei Cloud Eye also provides process monitoring , including process CPU usage, memory usage, opened files, and customized process-monitoring tasks.

Statement D is false because alarm templates and batch alarm creation eliminate the requirement to create every alarm rule individually.

Reference topics: Cloud Eye Server Monitoring; Process Monitoring; Alarm Rules; Alarm Templates; Auto Scaling Integration.

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

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 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.

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

For the HCIA-Cloud Service V3.5 curriculum version , statements A, B, and C are correct . An ECS must be associated with a security group so that inbound and outbound network access can be controlled. If an account has no custom group, Huawei Cloud provides a default security group, and users can either use that default group or create and select another security group that matches the workload's security requirements.

The V3.5-era Huawei Cloud VPC documentation distinguishes security groups from network ACLs by stating that security groups provide allow rules , whereas network ACLs provide both allow and deny rules. This distinction is important because it appears repeatedly in the HCIA V3.5 networking curriculum.

Statement D is false. Huawei Cloud specifically permits administrators to modify existing rules or add rules to the default security group . The default group itself cannot normally be deleted, but that restriction does not make its inbound or outbound rules immutable. Huawei's default-security-group documentation explicitly distinguishes group deletion restrictions from rule modification permissions.

Reference topics: VPC Security Groups; ECS Network Configuration; Default Security Group; Security Group Rules.

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

Statements B and D are correct. Huawei Cloud CBR architecture consists fundamentally of backups, vaults, and policies. A vault is the storage container used by CBR for backup data. Huawei documentation explicitly states that CBR stores backups in vaults and that different resource categories are associated with appropriate vault types, such as server backup vaults and disk backup vaults.

Statement B is also directly supported. Huawei categorizes CBR policies into backup policies and replication policies. A backup policy automatically runs backup operations according to configured schedules and retention parameters, while a replication policy periodically replicates eligible backup data to another vault or region.

Statement A is incorrect because CBR is specifically designed to automate protection through policies; regular backups do not normally need to depend on repeated manual execution. Huawei advises using backup policies for scheduled protection.

Statement C is too absolute. CBR substantially improves recoverability against accidental deletion, malware, software failures, and hardware faults, but no backup architecture legitimately guarantees that data can never be lost under every conceivable condition.

Therefore, B and D are the verified statements.

Reference topics: CBR Architecture; Vault Management; Backup Policies; Replication Policies.

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

1 → Bare Metal Server (BMS)

2 → Elastic Cloud Server (ECS)

3 → Physical server

The first scenario maps to BMS because Bare Metal Servers combine exclusive access to physical resources with cloud-oriented provisioning and management. Huawei Cloud recommends BMS for key or mission-critical applications and services requiring high performance. BMS retains direct physical CPU and memory access while supporting capabilities such as automatic provisioning, VPC networking, image deployment, monitoring, and cloud storage. It therefore provides both resource exclusivity and cloud flexibility .

The second scenario maps to ECS . ECS instances operate on virtualized infrastructure, so physical server resources can be shared among virtual machines. This model is appropriate for general-purpose and specialized cloud workloads where virtualization, rapid deployment, elasticity, and efficient resource utilization are priorities.

The third scenario maps to a traditional physical server . A physical server also provides exclusive resources, but Huawei's comparison shows that traditional servers do not inherently provide cloud capabilities such as automatic provisioning, VPC integration, image-based deployment, and standardized cloud monitoring. This makes them characteristic of traditional dedicated-service environments.

Huawei's comparison explicitly records exclusive resources for BMS and physical servers, but not ECS.

Reference topics: BMS, Physical Server, and ECS Comparison; Resource Exclusivity; Automatic Provisioning; Compute Architecture.

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

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.

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