H13-811_V3.5 HCIA-Cloud Service V3.5 Questions and Answers

Option D is incorrect . Huawei Cloud's official RDS for PostgreSQL constraints specify that a maximum of five read replicas can be created for one DB instance , not 15. Huawei's current read-replica documentation reiterates the same five-replica limit. The “15 read replicas” characteristic is associated with other Huawei database architectures, such as TaurusDB/GaussDB-related scaling designs, and must not be transferred to standard RDS for PostgreSQL.

Option C is directly supported by Huawei documentation. RDS for PostgreSQL is an object-relational database designed for complex OLTP and supports NoSQL and GIS data types. Huawei explicitly identifies websites, location-based applications, and complex data object processing as representative workloads.

Option B is also valid. Huawei Cloud provides real-time status and performance monitoring for RDS instances, exposing database-related metrics and allowing alarms to be configured for operational monitoring.

Option A reflects the managed-service security architecture: RDS provides controls involving network isolation, security groups, SSL, account authorization, backups, and other mechanisms to protect databases and user data.

The numerical scaling claim in D therefore makes it decisively incorrect.

Reference topics: RDS for PostgreSQL; Read Replicas; Database Monitoring; PostgreSQL Application Scenarios; RDS Security.

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

1 → No configuration is required

2 → Configure a VPC peering connection

3 → Create a VPN

The mappings follow Huawei Cloud's VPC connectivity rules. ECS-C and ECS-D are deployed in the same VPC , so their private network traffic can use the VPC's internal routing directly. Provided the applicable security-group rules allow the traffic, no additional VPC interconnection mechanism is required.

ECS-A and ECS-B are in different VPCs but in the same CN North-Beijing4 region. Huawei Cloud VPC peering is specifically designed to connect two VPCs in the same region using private IP addresses. Huawei documentation states that VPC peering is region-scoped and enables resources in the two peered VPCs to communicate after the required routes are configured.

ECS-A and ECS-C are located in different regions. The HCIA V3.5 networking design uses VPN for this scenario. Huawei's official VPN documentation specifically describes establishing VPN gateways and VPN connections between two VPCs in different regions, providing an encrypted communication channel across the Internet.

Therefore, the required sequence is same VPC → no additional configuration; same-region different VPCs → peering; cross-region VPCs → VPN .

Reference topics: VPC Communication; VPC Peering; VPN; Intra-VPC Networking.

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

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 statement is TRUE because Huawei Cloud NAT Gateway includes both public NAT Gateway and private NAT Gateway functionality. These two service types cover the two network-translation scenarios described.

A public NAT Gateway performs translation between a private VPC network and the Internet. Through SNAT, servers with private IP addresses can share Elastic IP addresses to access public networks. Through DNAT, internal servers can provide externally accessible services using public addresses.

A private NAT Gateway performs address translation between private networks. Huawei Cloud describes private NAT gateways as enabling servers in a VPC to communicate with on-premises data centers or other VPCs while translating private addresses to transit IP addresses. This is particularly valuable during network migration, address-overlap resolution, and hybrid-cloud integration.

Huawei's official NAT Gateway comparison therefore states that a public NAT Gateway connects a private network to the Internet, whereas a private NAT Gateway connects private networks.

The statement deliberately describes the NAT Gateway service family rather than only public NAT. Since Huawei Cloud provides translation in both private-to-private and private-to-public architectures, the proposition is correct.

Reference topics: NAT Gateway; Public NAT Gateway; Private NAT Gateway; SNAT; DNAT.

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

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.

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

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.

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

Option A specifically describes Huawei Cloud's dynamic resource adjustment mode . In Huawei Auto Scaling, dynamic scaling uses an alarm policy that evaluates real-time monitoring metrics such as CPU utilization. When the configured alarm condition is reached, AS automatically performs a scaling action to increase or decrease resources so that capacity follows unpredictable workload changes.

Option B is incorrect because triggering an AS policy does not automatically redefine the configured maximum number of instances . The maximum is an upper boundary for the AS group. A scaling policy changes the expected number of instances, adds or removes instances, or sets the instance count to a configured value while remaining within the minimum and maximum boundaries.

Option C correctly describes planned scaling , but the question specifically asks about dynamic resource scaling. Huawei classifies scheduled and periodic policies as planned adjustment mechanisms suitable for workloads that change predictably according to a schedule.

Option D is incorrect because alarm-triggered scaling is subject to a cooldown period . During that period, Huawei Cloud rejects additional scaling requests generated by alarm policies to prevent repeated unnecessary scaling operations.

Therefore, for dynamic resource scaling, A is the correct answer .

Reference topics: Auto Scaling; Dynamic Resource Adjustment; Alarm Policies; Planned Scaling; Cooldown Period.

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.

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

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.

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

The statement is TRUE . Huawei Cloud makes an explicit architectural distinction between Elastic Cloud Servers and Bare Metal Servers regarding the underlying compute resources. An ECS is a virtualized compute instance. Multiple ECS instances can therefore consume resources provided by the same underlying physical host, with virtualization providing logical isolation between tenants and workloads.

A BMS, by contrast, provides exclusive access to physical compute resources. Huawei Cloud states directly that BMS users can exclusively access physical resources, whereas ECS users share those physical resources. This makes BMS particularly suitable for mission-critical systems, big-data clusters, enterprise middleware, high-performance workloads, and applications that require predictable performance or direct access to physical CPU and memory resources.

Huawei's BMS comparison also identifies Exclusive resources = Yes for BMS and traditional physical servers, but No for ECS. BMS additionally provides cloud characteristics such as automatic provisioning, VPC integration, image-based deployment, monitoring, and cloud storage while retaining physical-server performance.

Therefore, the differentiation presented in the question is technically accurate.

Reference topics: Bare Metal Server Fundamentals; BMS versus ECS; ECS Virtualization; Exclusive Physical Resources.

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

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.

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

Option B is incorrect because Huawei Cloud OBS does not allow a bucket that has already had versioning enabled to return to the original Disabled state. Versioning can initially be enabled on a bucket, but once enabled, it can subsequently only be suspended , not disabled.

Option A is correct. With versioning enabled, OBS assigns unique version IDs to uploaded objects, allowing multiple objects with the same key or name to coexist as different versions. This protects against accidental overwrites and provides point-in-time recovery capabilities.

Option C is also correct when a specific historical version is permanently deleted. Each object version is independently identified by its version ID, so deleting one specified version does not inherently remove the other retained versions.

Option D accurately describes the initial state. Huawei states that versioning is disabled by default for newly created OBS buckets. When versioning has never been enabled, uploading a new object with the same name replaces the existing object instead of maintaining multiple historical versions.

The critical distinction is therefore Disabled versus Suspended . Disabled is the initial state; after versioning is enabled, it cannot be restored to Disabled.

Reference topics: OBS Versioning; Version IDs; Suspending Versioning; Object Recovery.

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

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.

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

The correct advantages are B, C, and D. Huawei Cloud EVS provides a range of disk specifications and performance classes so customers can select storage appropriate for different workloads and budgets. Huawei's EVS overview explicitly lists various disk types and high security/reliability among its principal benefits.

EVS is also easier to manage than traditional physical storage. Huawei documentation comparing EVS with traditional hard disks states that EVS disks provide higher reliability and I/O throughput and are easier to use. Cloud-based provisioning eliminates much of the physical installation, replacement, cabling, and capacity-management work associated with conventional disks.

Option A is incorrect. EVS is block storage intended for cloud servers and cannot be used independently. Huawei explicitly states that EVS disks must first be attached to a supported server and then initialized, partitioned, and formatted before applications can persist data on them.

High reliability derives from distributed storage and data-protection mechanisms, while the range of available disk classes enables workload-specific performance selection.

Therefore, various disk types, ease of use, and high reliability are advantages; independent use is not.

Reference topics: EVS Advantages; Block Storage; EVS Reliability; EVS Disk Types.

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

Option D is incorrect because improved response speed and website availability are fundamental objectives of CDN . Huawei's official CDN description explicitly characterizes CDN as a smart virtual network on Internet infrastructure that caches origin content at points of presence closer to users. This reduces transmission distance and accelerates access.

Huawei specifically states that CDN speeds up site response and improves site availability , while overcoming bottlenecks associated with low bandwidth, heavy user traffic, and uneven distribution of network nodes. Therefore, claiming that CDN cannot improve response speed or availability directly contradicts the documented purpose of the service.

Option A is essentially Huawei's own definition of CDN. Option B correctly describes major problems addressed by distributed content caching and request scheduling. Option C is also correct: content is cached or distributed to edge PoPs, and requests are scheduled to suitable nearby nodes. This reduces the requirement for every request to reach the original server.

CDN can additionally reduce origin-server workload and bandwidth consumption, which may improve origin infrastructure efficiency. However, that benefit exists alongside , not instead of, faster response and improved availability.

Accordingly, D is the only incorrect statement.

Reference topics: CDN Fundamentals; CDN PoPs; Website Acceleration; Content Distribution; Site Availability.

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