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

Answer : B

For the HCIA-Cloud Service V3.5 snapshot model represented by this question, the statement is FALSE. Huawei Cloud's exam-era EVS documentation states that an EVS snapshot captures the state of a disk at a specific point in time and can be used for rollback or creation of another disk. However, the snapshot is dependent on its source EVS disk.

Huawei's earlier official EVS documentation explicitly states that when an EVS disk is deleted, the disk data and snapshots created for that disk are also deleted. The applicable documentation also states that when a snapshot's source disk is deleted, all snapshots of that source disk are deleted.

This distinction matters because Huawei has subsequently introduced standard snapshots stored in OBS, for which newer lifecycle behavior can differ. Current documentation distinguishes legacy snapshots from standard snapshots: legacy snapshots are deleted with the source disk, whereas newer standard snapshots may remain. However, HCIA V3.5 questions were written around the earlier EVS snapshot behavior.

Accordingly, the proposition that deleting an EVS disk does not delete its snapshots contradicts the V3.5-era model.

Reference topics: EVS Snapshots; Snapshot Lifecycle; EVS Disk Deletion; Point-in-Time Recovery.

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

Answer : C

Option C cannot be the cause because the password used to log in to the ECS operating system has no requirement to match the database credential used by an RDS instance. ECS authentication and RDS database authentication are separate security domains. An application running on an ECS connects to RDS using the database endpoint, port, database username, and corresponding database password.

Option A can cause the failure. Huawei's RDS troubleshooting guidance requires appropriate security-group rules so that traffic to the database port is permitted.

Option B can also prevent communication. Huawei Cloud states that when an ECS and RDS DB instance are deployed in different VPCs, network connectivity must be established---for example through an appropriate VPC peering connection---or the resources must be placed in a mutually reachable network.

Option D can likewise cause connection failure. Huawei's official RDS troubleshooting process specifically instructs administrators to validate the connection address and port configuration and test connectivity to the RDS listening port. Examples include port 3306 for RDS for MySQL and 5432 for PostgreSQL.

The ECS's own login password is unrelated to these connectivity requirements; therefore C is correct.

Reference topics: RDS Database Connectivity; ECS-to-RDS Communication; Security Groups; VPC Peering; Database Ports.

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

Answer : A

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.

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

Answer : A, B, C

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.

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

Answer : B

The statement is FALSE. Huawei Cloud explicitly supports using VPN to establish communication between VPCs deployed in different regions. The Huawei Cloud VPC FAQ describes this architecture directly: VPCs in the same region can be connected by VPC peering, while VPCs in different regions can establish connectivity through VPN. In the VPN design, each VPC uses a VPN gateway, and the two gateways establish an encrypted connection over the Internet. The VPC CIDR blocks are configured as the local and remote subnets.

This distinction is central to the HCIA V3.5 networking domain. VPC peering is region-scoped: two VPCs connected through a peering connection must reside in the same region. VPN, by contrast, can establish encrypted connectivity between geographically separated VPC networks. Huawei's VPN documentation specifies creating a VPN gateway for each VPC, creating VPN connections, configuring the peer gateway EIP, defining peer subnets, and applying matching cryptographic parameters.

Consequently, saying that Huawei Cloud VPN ''does not support'' cross-region VPC communications directly contradicts the supported VPN deployment model.

Reference topics: Virtual Private Network; Cross-Region VPC Connectivity; VPC Peering; VPN Gateways.

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

Answer : B

Option B is incorrect. Huawei Cloud explicitly requires subnet CIDR blocks within the same VPC to be unique and not overlap. Allowing overlapping subnets would make local route selection ambiguous and create address conflicts inside the VPC. Huawei's subnet definition therefore states that subnets in a VPC cannot overlap with each other.

Option A is correct for subnet planning: Huawei advises users to plan subnet address ranges carefully because a subnet's CIDR block cannot be changed after creation. This is why future capacity requirements should be considered before allocating subnet prefixes.

Option C is also consistent with Huawei's VPC definition. A subnet represents a unique CIDR block containing an IP address range inside a VPC, and VPC resources requiring private networking are deployed into these subnets. Option D is correct because the subnet CIDR must fall within the VPC's address range. Huawei's network-planning guidance explicitly states that the subnet CIDR block must be within the VPC CIDR block and that subnet CIDR blocks in the VPC must be unique.

Thus, the only incorrect planning statement is B.

Reference topics: VPC and Subnet Planning; CIDR Blocks; Subnet Addressing; VPC Network Design.

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

Answer : B

The statement is FALSE because directly binding an EIP to an ECS is only one of several Huawei Cloud mechanisms for providing Internet access. An ECS with its own EIP can communicate directly with the public network, but ECSs can also access the Internet without having an EIP individually bound to each server.

The principal alternative is a public NAT Gateway using an SNAT rule. Huawei Cloud states that servers in a VPC subnet can share an EIP through a public NAT gateway. The NAT gateway translates their private source addresses into the configured public EIP, enabling outbound Internet connectivity while avoiding the need to expose or allocate an individual public IP address to every ECS.

Huawei's ECS documentation also explicitly describes ''Internet connectivity for an ECS without an EIP bound'' and recommends NAT Gateway as the standard solution. A proxy/SNAT ECS can also provide an Internet access path in suitable architectures.

Therefore, binding an EIP directly to the ECS is a valid method, but it is not the only method, making the statement false.

Reference topics: Elastic IP; Public NAT Gateway; SNAT; ECS Internet Connectivity; VPC Networking.