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

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.

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

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.

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

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.

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

Option A is incorrect because Huawei Cloud Auto Scaling is designed to automatically adjust ECS instances and bandwidth resources , not Bare Metal Server instances. Huawei's AS documentation defines an AS group as a collection of ECS instances and states that scaling actions add or remove ECS instances according to alarm, scheduled, or periodic policies. BMS provides dedicated physical compute and is provisioned through the BMS service rather than being dynamically created and destroyed by an ECS Auto Scaling group.

The other relationships are valid. Cloud Eye supports BMS operating-system monitoring after the Cloud Eye Agent is installed; the BMS reports detailed CPU, memory, disk, and network metrics to Cloud Eye. EVS is integrated with BMS and additional supported EVS data disks can be attached when more storage is required. IMS is likewise an integral BMS service: images can be used to create consistently configured BMSs and to reinstall or change their operating systems, reducing repetitive deployment work. Huawei's BMS architecture explicitly lists VPC, IMS, EVS, Cloud Eye, and backup services as integrations supporting BMS operation.

Reference topics: Bare Metal Server Architecture; BMS and Other Cloud Services; Auto Scaling; Cloud Eye; IMS; EVS.

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

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.

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

The statement is false because its description of infrastructure ownership does not correctly characterize a hybrid cloud. A hybrid cloud combines different cloud environments—most commonly private cloud and public cloud —and enables workloads, applications, or data to be distributed between them according to security, capacity, latency, compliance, or business requirements.

Huawei Cloud describes hybrid cloud as a blend of private and public cloud environments. The private portion may be dedicated to a particular customer and may host confidential or sensitive workloads, while public cloud resources are delivered through infrastructure operated by a cloud service provider. Consequently, the combined infrastructure is not inherently owned and operated by a single organization .

This ownership distinction separates hybrid cloud from a purely private-cloud model. A private cloud can be dedicated to a single organization, whereas hybrid architecture deliberately combines environments that may have different infrastructure ownership and operating responsibility.

The statement correctly recognizes that hybrid cloud is flexible and that workloads can use different cloud environments, but because it makes an absolute and incorrect assertion about single-organization ownership, the entire statement must be evaluated as FALSE .

Reference topics: Cloud Deployment Models; Public Cloud; Private Cloud; Hybrid Cloud; CloudPond Service Overview.

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

Options A, B, and C are consistent with the fundamental characteristics and enabling technologies of cloud computing. Cloud platforms are designed to make resources elastic. Huawei Cloud Auto Scaling, for example, dynamically adds or removes ECS instances and adjusts related resources according to actual workload demand. Dynamic resource scaling is therefore a core practical capability of cloud computing.

On-demand deployment is also fundamental. Huawei Cloud's Cloud Adoption Framework explains that cloud resources can be provisioned, adjusted, and scaled rapidly without the traditional procurement and installation cycle associated with physical infrastructure. This allows organizations to create computing environments when needed and release them when demand decreases.

Virtualization is another important enabling technology. It allows physical computing resources to be abstracted, pooled, isolated, and efficiently shared among multiple workloads. Huawei Cloud specifically identifies virtualization and resource pooling as mechanisms that improve physical-resource utilization.

Option D is incorrect. A defining cloud characteristic is that the provider assumes responsibility for substantial portions of infrastructure construction and maintenance. The exact customer/provider boundary varies between IaaS, PaaS, and SaaS, but customers do not maintain all resources .

Reference topics: Cloud Computing Characteristics; Elasticity; On-Demand Provisioning; Virtualization; Shared Responsibility.

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

A → 2

B → 1

C → 3

The mappings follow Huawei Cloud's system-defined authorization model for Bare Metal Server. BMS CommonOperations provides operational permissions required for routine server administration. Huawei explicitly identifies starting, stopping, restarting, and querying BMS instances as operations permitted under the common-operations permission set. It therefore maps to permission 2.

BMS FullAccess represents administrator-level access to the BMS service. It permits operations that CommonOperations and ReadOnlyAccess cannot perform, including higher-impact lifecycle and configuration operations. Huawei Cloud's BMS permission matrix shows that reinstalling a BMS operating system is supported by FullAccess but not by CommonOperations or ReadOnlyAccess. Consequently, BMS FullAccess maps to permission 1.

BMS ReadOnlyAccess is intended for users who need visibility into BMS resources without authority to modify them. It permits users to query and view BMS information, including server lists and instance details, but does not authorize lifecycle actions such as starting, stopping, restarting, or reinstalling an operating system. It therefore maps to permission 3.

The verified mapping is CommonOperations → routine operations; FullAccess → OS reinstallation; ReadOnlyAccess → viewing BMS information .

Reference topics: Bare Metal Server Permissions; IAM Authorization for BMS; System-Defined BMS Policies.

The statement is TRUE . Huawei Cloud Image Management Service supports creating private images from external image files, with OBS serving as the staging storage location for those files. The documented workflow is to prepare the source image, upload the image file to an appropriate OBS bucket, and then register or import that file through IMS as a private image.

Huawei's IMS documentation explicitly describes the scenario as registering an image file that has been uploaded to an OBS bucket as a private image . During image creation, the administrator selects Import Image or Image File as the source, selects the OBS bucket containing the prepared file, and then selects the required file.

Supported formats and detailed constraints depend on the image type and import method. For example, standard system-disk image imports and optimized fast-import workflows have specific requirements concerning image formats, file size, operating system, and bucket storage class. However, these restrictions do not change the fundamental integration represented in the question.

OBS therefore provides object storage for the source image file, while IMS performs image registration and lifecycle management. The resulting private image can subsequently be used to provision identically configured ECS instances.

Reference topics: Image Management Service; Creating Private Images; Importing Image Files; OBS and IMS Integration.

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

The statement is TRUE. Huawei Cloud OBS provides several resource-based authorization mechanisms, including bucket policies and object policies. Their principal distinction is the scope of resources to which they apply.

Huawei's official OBS Permission Configuration Guide explicitly states that an object policy applies to only one object in a bucket, whereas a bucket policy applies to multiple objects or all objects within the bucket. This enables administrators to select the authorization mechanism that best matches the required granularity.

An object policy is useful when permissions must be configured specifically for an individual object, such as granting another principal read or write permissions to one particular resource without broadening access to the rest of the bucket.

A bucket policy supports broader authorization scenarios. Its policy statements can define principals, actions, resources, effects, and conditions to grant or restrict access to selected objects, prefixes, or the entire bucket. Typical uses include allowing another Huawei Cloud account to access specified OBS resources or granting IAM identities access to defined bucket content.

The question therefore correctly distinguishes object-level policy scope from bucket-level multi-object policy scope.

Reference topics: OBS Permission Management; Object Policies; Bucket Policies; Resource-Based Authorization.

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

Statement C is incorrect because container images do not require a private registry. Huawei Cloud container services can consume images from multiple sources, including Huawei Cloud SoftWare Repository for Container (SWR), public repositories, shared repositories, and supported third-party image repositories. Huawei Cloud CCI documentation explicitly states that containers can pull both SWR images and third-party images .

A container image is a standardized, executable package containing the files and configuration required for a containerized application. Huawei describes it as containing the application and required supporting components such as environments, libraries, configuration files, and file systems. This supports option A.

Option B is consistent with the container-image concept because images can contain a base operating-system environment or filesystem together with application dependencies and configuration required by the application.

Option D is also valid. An image acts as an immutable deployment template: once constructed, the same image can be instantiated repeatedly as containers, enabling applications to run with a consistent packaged environment rather than requiring the software stack to be manually reconfigured for every deployment.

A private registry is useful for controlling proprietary enterprise images, but it is an architectural choice—not a mandatory requirement. Therefore, C is the incorrect statement.

Reference topics: Container Images; SWR; Container Registries; CCI Image Sources; Containerized Application Deployment.

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

Option A is correct . Huawei Cloud Elastic Load Balance provides several traffic-distribution algorithms, including weighted round robin, weighted least connections, and source IP hash for shared load balancers. When backend servers have equal weights under weighted round robin, they receive an equal proportion of requests, providing the even traffic distribution described in the question.

Auto Scaling and ELB are explicitly integrated. When an AS group is associated with a load balancer, Huawei Cloud automatically associates newly added ECS instances with the load balancer and removes the association when instances leave the AS group. Therefore, option C is false; administrators do not need to manually register each dynamically created instance one by one.

Option B is incorrect in this context because the load balancer and its AS resources operate within the applicable regional/VPC deployment architecture; a standard shared ELB is not a mechanism for arbitrary cross-region backend distribution. Option D is also false because detecting unhealthy instances depends upon an enabled health-check mechanism. Disabling health checking removes the basis for making that health determination.

Reference topics: Elastic Load Balance; Auto Scaling and ELB Integration; Backend Servers; Load Balancing Algorithms.

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

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.

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

The statement is true in the context of the HCIA cloud-computing architecture model. Cloud computing evolved from developments in computing, distributed systems, virtualization, networking, and Internet technologies. Most importantly, cloud services are consumed remotely, making network connectivity an intrinsic part of service delivery.

Huawei Cloud defines cloud services as IT capabilities delivered by cloud providers through the Internet or dedicated networks . These services include compute, storage, networking, security, database, middleware, O & M, big data, and AI resources. Users obtain and consume those resources remotely rather than requiring the underlying physical infrastructure to reside locally.

This dependence is architectural rather than merely convenient. An ECS, database, object-storage bucket, SaaS application, or cloud management interface has practical value to a remote user only if network connectivity exists between the consumer and the cloud environment. A private connection can replace Internet access in certain enterprise architectures, but that is still network connectivity.

Accordingly, the intended HCIA principle is that cloud computing and networking are inseparable: network access forms the communication foundation through which cloud resources are delivered and consumed .

Reference topics: Cloud Computing Fundamentals; Network Access; Cloud Service Delivery; Internet and Dedicated Networks.

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

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.