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.

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

All four operations are supported management actions for Huawei Cloud RDS instances, subject to the applicable database engine, instance type, current status, and other service constraints.

Changing the failover priority is supported for primary/standby RDS deployments. Huawei allows administrators to prioritize either Reliability , which emphasizes data consistency, or Availability , which emphasizes service continuity during failover.

Deleting a DB instance is a standard lifecycle-management operation available to appropriately authorized users. Huawei's RDS permission model includes the rds:instance:delete action for this purpose.

Scaling up storage space is likewise an established RDS modification operation. Administrators can increase allocated storage when database capacity requirements grow, and supported database engines can also provide storage autoscaling options.

Finally, rebooting a DB instance is a supported administrative action used when configuration changes, troubleshooting, or other operational circumstances require an instance restart. Huawei's CTS integration explicitly identifies both scaling storage and restarting an instance as auditable RDS operations.

Huawei's RDS API catalog lists deleting, scaling storage, rebooting, and changing failover priority as supported instance-management operations.

Reference topics: RDS Instance Management; Failover Priority; Storage Scaling; DB Instance Reboot; DB Instance Deletion.

The major CTS functions represented by the options are trace recording, trace query, and trace transfer , making A, B, and D correct.

Trace recording captures operations performed through the Huawei Cloud management console, through APIs, and operations initiated by supported cloud services. These records provide an audit trail containing information such as the operator, operation time, resource, operation result, and associated request data.

Trace query allows administrators and auditors to search recent operational records on the CTS console using criteria such as trace source, resource type, operator, trace status, and operation type. This is essential for security auditing, compliance investigation, and troubleshooting.

Trace transfer provides longer-term retention and centralized analysis. CTS can package operation records into trace files and transfer them to supported destinations such as OBS or LTS for preservation and subsequent processing.

Option C, OS monitoring , does not belong to CTS. Operating-system performance monitoring is primarily a Cloud Eye/server-monitoring capability rather than an audit-trace function.

Huawei's official CTS documentation expressly identifies recording, querying, and transfer among its core service functions.

Reference topics: Cloud Trace Service; Trace Recording; Trace Query; Trace Transfer; Cloud Auditing.

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

The correct answer is D. Available. Huawei Cloud uses Cloud Backup and Recovery to create backups of EVS disks, and the source disk must be in an operational state that permits a consistent backup operation. Huawei's official CBR and EVS documentation states that EVS disk backups can be created when disks are in the Available or In-use state.

Of the states listed in this question, only Available qualifies. A disk in the Creating state has not completed provisioning. A disk in the Deleting state is being removed and cannot serve as a stable backup source. “Deletion failed” represents an exception condition requiring remediation rather than a valid backup state. Huawei's disk-status guidance instructs administrators to troubleshoot a disk in the Deletion failed state rather than perform normal storage operations on it.

An Available disk has completed creation, is not currently attached for active I/O, and is accessible for supported management operations. Huawei Cloud can therefore associate it with a disk backup vault and create a CBR backup.

Although In-use would also be supported if included among the options, it is absent here. Consequently, Available is the only valid selection.

Reference topics: EVS Disk States; CBR Cloud Disk Backup; Backup Prerequisites.

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

Options B and C are incorrect because they reverse the isolation characteristics of IAM projects and enterprise projects . Huawei Cloud defines enterprise projects as a mechanism for grouping and managing resources across regions. Resources assigned to different enterprise projects are logically isolated , and a single enterprise project can contain resources residing in multiple regions. Supported resources can also be added to, removed from, or transferred between enterprise projects. Consequently, statements A and D correctly describe Enterprise Project Management.

IAM projects operate differently. Huawei Cloud documentation states that IAM projects are region-oriented and are used to group and physically isolate resources within a region . A project corresponds to a region, and an IAM project does not provide the cross-region logical grouping model associated with enterprise projects.

Therefore, B is wrong because it attributes physical, same-region isolation to enterprise projects, while C is wrong because it attributes logical isolation to IAM projects. The two concepts are intentionally distinguished in Huawei Cloud architecture: IAM project = regional/physical isolation; enterprise project = cross-region/logical resource organization .

Reference topics: IAM Projects; Enterprise Projects; Resource Isolation; Enterprise Management.

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

The statement is FALSE . Although an ECS group does logically organize ECS instances, its placement behavior is the opposite of what the second sentence states. Huawei Cloud ECS groups support the anti-affinity policy , which is designed to place ECS instances belonging to the same group on different physical hosts .

Anti-affinity is an availability and fault-isolation mechanism. If multiple application instances were placed on one physical server, failure of that host could simultaneously disrupt every application instance. Distributing the ECSs across different hosts reduces this correlated-failure risk and improves service reliability, high availability, and disaster tolerance.

Huawei's ECS documentation explicitly states that ECS groups support the anti-affinity policy and that ECSs in an anti-affinity group are deployed on different hosts. When an existing ECS is added to such a group, Huawei Cloud may even reallocate its host so that the placement requirement can be maintained.

Therefore, the first proposition—an ECS group logically groups ECSs—is valid. However, the assertion that ECSs in that group are created on the same physical server by default contradicts the anti-affinity design. Since the overall statement contains this incorrect condition, the correct answer is FALSE .

Reference topics: ECS Groups; Anti-Affinity Policy; Host Placement; High Availability.

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

Statement C is incorrect in the HCIA-Cloud Service V3.5 IMS model. Huawei Cloud does not impose a standalone service charge simply for using the core Image Management Service functions such as creating a standard private image. Huawei's official getting-started documentation explicitly states that creating a private image is free . Charges may nevertheless arise from dependent resources associated with image usage.

This distinction explains option A. Depending on the image and deployment model, costs can be associated with licensed operating systems, storage used for image files, backups, OBS objects, or other dependent cloud resources. These costs do not make IMS itself a separately charged service.

Option B correctly reflects the principal image categories taught in the HCIA course: public images, private images, and shared images . Marketplace images are additionally available as third-party packaged offerings but do not invalidate this fundamental IMS classification.

Option D also correctly describes the role of an image. Images provide standardized operating environments and can include the operating system, pre-installed applications, configuration data, and user applications. They can then serve as templates for rapidly creating ECS instances with consistent software configurations.

Accordingly, the incorrect statement is C .

Reference topics: Image Management Service; IMS Billing; Private Images; Image Classification; ECS Creation from Images.

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

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.

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