H13-527_V5.0 Huawei HCIP-Cloud Computing V5.0 Free Practice Exam Questions (2026 Updated)

Horizon is OpenStack’s web-based dashboard, which means it provides a graphical user interface for managing cloud services such as compute, networking, identity, and storage. OpenStack’s Horizon project documentation describes Horizon as the canonical dashboard implementation and a web-based user interface for OpenStack services. Because of that, using command-line interfaces (CLIs) is separate from Horizon rather than a function performed inside Horizon itself. OpenStack documentation also treats the dashboard and the command-line clients as different ways to interact with the cloud.

The other options describe actions that are consistent with what Horizon is used for. OpenStack materials show that users can start and stop VM instances, and Horizon is commonly used to manage cloud resources including projects, images, and networking-related items such as tenant networks. Modern OpenStack deployments also expose dashboards or panels that surface operational details, including instance console logs or monitoring-related views depending on enabled services. Therefore, the only option that is not something you do using Horizon itself is A, because CLI management is performed outside the Horizon dashboard.

========

The statement is TRUE . OpenStack’s official image creation documentation describes Diskimage Builder (DIB) as an automated disk image creation tool that supports a variety of Linux distributions and architectures. The documentation explicitly states that DIB can build images for Fedora, Red Hat Enterprise Linux, Ubuntu, Debian, CentOS, and openSUSE , which confirms that it can generate images for multiple operating systems from a standardized build framework. It also supports reusable “elements,” allowing operators to define image content in a modular and repeatable way.

Because of this automation and modularity, DIB is well suited for batch creation of standard images in enterprise cloud environments, including OpenStack-based platforms such as Huawei Cloud Stack. Instead of manually creating images one by one, administrators can define consistent build templates and produce multiple images with the same baseline security, packages, and configuration standards. That aligns directly with the role of standardized image management in cloud O & M and service deployment. Therefore, the correct answer is A (TRUE) .

========

The correct fill-in answer is hosts. Huawei documentation explicitly states that memory overcommitment must be enabled on the node where the VM is deployed before the VM can use that capability. In Huawei Cloud Stack usage and O & M materials, the node here is the compute host, and the docs also describe memory overcommitment behavior in terms of host resources and overcommitment ratios.

Huawei O & M guidance further explains that host resource isolation must be enabled before memory overcommitment is enabled, which confirms that this setting is tied to the compute-host layer. Some Huawei documents also refer to enabling or disabling memory overcommitment for a host group, but the actual execution point is still the underlying hosts/nodes in that group. Because your fill-in statement says “enable memory overcommitment on _____,” the most accurate and broadly supported answer is hosts. Therefore, after correcting the sentence, the verified answer is hosts.

========

The correct answers are B and C . Huawei documentation states that a security group is a collection of access control rules used to protect cloud servers or instances added to that group. Huawei also describes a network ACL as a security service for VPCs or subnets , which means it protects traffic at the subnet level rather than directly protecting individual instances. That makes C correct.

Huawei’s comparison guidance also distinguishes the way rules are processed. Security groups are stateful and their rules work together as a combined access-control set, while network ACLs are processed according to rule priority , which makes B correct. The official Huawei comparison page explicitly frames network ACLs as an additional security layer on top of security groups.

Option A is incorrect because network ACLs are not mandatory by default in the same way security-group association is standard for instances. Option D is not supported by the Huawei VPC/network ACL documentation cited here; the docs emphasize instance-vs-subnet scope and rule handling, not that exact 5-tuple versus 3-tuple split for these two features. Therefore, the best verified answer is B, C .

========

The best verified answer is A, B, and C . Huawei ECS documentation explicitly supports upgrading ECS specifications and adjusting capacity-related resources, which makes D the reasonable and appropriate response when access performance is slow. Increasing compute or network capacity is aligned with normal cloud performance tuning practice.

By contrast, A is not a standard Huawei performance-optimization recommendation. Huawei OBS guidance focuses more on choosing proper regions, APIs, and storage access patterns than on “reducing buckets and storing data centrally” as a latency fix. Centralizing data can even create concentration rather than optimization.

B is also inappropriate as a first-line solution because replacing ECS with BMS changes the compute model but does not directly target the ECS-to-OBS access path. C is similarly inappropriate because CCE is a Kubernetes/container orchestration service, not a direct remedy for object-storage access latency in an ECS+OBS media scenario. Huawei positions CCE for container lifecycle management, not as a general replacement for ECS to solve this kind of OBS delay.

So the inappropriate measures are A, B, and C .

The correct answer is B. ML2 Plugin . In OpenStack Neutron, ML2 stands for Modular Layer 2 and is the main core networking plugin framework used to support different network types and mechanism drivers. Official OpenStack documentation describes ML2 as a plug-in with components for network types and mechanisms, not as a service plugin .

Service plugins in Neutron are different. They add higher-level networking services beyond basic Layer 2 connectivity. OpenStack deployment documentation shows optional service areas such as load balancing and virtual private network services, and Neutron’s router-related functionality is commonly associated with the L3 service plugin . These are examples of service plugins layered on top of the core networking plugin model.

So the key distinction is this: ML2 is the core plugin architecture , while L3, VPN, and load balancing belong to the service-plugin category. In Huawei Cloud Stack networking topic coverage, this separation between the core Neutron plugin and optional service plugins is also fundamental. Therefore, the option that is not a service plugin is B. ML2 Plugin .

========

The statement is FALSE . Official OpenStack documentation clearly distinguishes pause from suspend . When a server is paused , OpenStack states that the state of the VM is stored in RAM , and the instance continues in a frozen state. This means memory is not written to disk during a pause operation. Because RAM is still occupied, a paused VM does not reduce resource usage to a minimal level in the way the question suggests.

By contrast, when a server is suspended , OpenStack documentation says that its state is stored on disk , all memory is written to disk , and the server is stopped. This is the action that is conceptually similar to hibernation. The distinction is important in OpenStack and Huawei Cloud Stack operations because pause is mainly used for temporary freezing of execution, while suspend is used when preserving state on disk is required. Therefore, the statement in the question incorrectly describes suspend , not pause . For that reason, the correct answer is B (FALSE) .

The best verified answer is A, B, and D . Huawei networking documentation shows that Internet access troubleshooting for cloud resources commonly involves checking whether an EIP is bound or whether a NAT gateway is configured , which supports A . Huawei guidance also explicitly refers to selecting or checking an appropriate EIP bandwidth , which supports D as a normal troubleshooting item.

Huawei documentation also shows that network ACL rules are part of VPC access control and can affect connectivity. Because network ACLs are stateless and traffic validation depends on rule direction, checking ACL rules is a reasonable O & M troubleshooting operation. In your option wording, inbound rules are still part of that validation scope, so B is acceptable.

By contrast, checking route configurations on core switches is not the standard first-line troubleshooting action for tenant-side VPC Internet access in Huawei Cloud Stack service O & M. The cloud service boundary is usually diagnosed first through NAT, ACL, and EIP-related configuration. Therefore, the verified answer is A, B, and D .

The best verified answer is D. Workspace . Huawei’s official health-check documentation for FusionCare shows that FusionCare supports unified health checks for multiple Huawei Cloud Stack components and services. The published health-check item lists explicitly include Service OM , eSight , and CCE and SWR , which confirms that those services are within FusionCare’s supported inspection scope.

By contrast, the Huawei monitoring materials mention Workspace Overview under broader monitoring capabilities, not under the FusionCare-supported health-check list shown in the cited documents. In other words, Workspace appears in Huawei’s overall monitoring ecosystem, but it is not evidenced in the cited FusionCare support list the way Service OM, eSight, and CCE are. That makes Workspace the option that cannot be checked using FusionCare in this question set.

So based on Huawei’s documented FusionCare-supported inspection items, A , B , and C are covered, while D is not shown as a FusionCare check target. Therefore, the verified answer is D .

========