H13-527_V5.0 Questions and Answers

The best verified answer is A, B, and C. Huawei’s Managing Network Resources documentation states that on Service OM, administrators can view the number of created physical networks and virtual networks, which supports option C. The same Huawei material also says administrators can collect information for handling VM network faults, and related VPC/API guidance shows Service OM visibility into ports, including VM NIC-related ports, which supports A.

Huawei documentation for Direct Connect further shows that administrators can create Direct Connect access points on Service OM before tenants can use Direct Connect. In training-style wording, this aligns with the idea of creating private line access points, so B is also correct.

Option D is the one that does not fit as a standard Service OM network resource management action in the same way. Huawei documentation emphasizes viewing physical network information and managing related network resources, but creation or low-level configuration of physical networks is generally handled through platform network configuration workflows rather than as a routine Service OM tenant/resource function. Therefore, the correct set is A, B, C.

========

The statement is TRUE. Huawei Cloud Stack separates management responsibilities between operation administrators and VDC administrators. Huawei’s service-management documentation shows that operation administrators work at the platform-wide level and can publish cloud services and associate them with approval processes, which reflects their broader administrative scope. By contrast, VDC administrators work within the boundary of their own VDC and manage service usage and permissions inside that tenant-like scope. This architecture strongly supports the rule that both roles can participate in approval-process customization, but the visibility scope is different.

In practice, this means an approval process created by an operation administrator can be used as a global process across the platform, while a process created by a VDC administrator is limited to the VDC context rather than being exposed to all tenants or all service domains. This aligns with Huawei Cloud Stack’s layered governance model, where global service governance belongs to operation administrators and tenant-level governance belongs to VDC administrators. Therefore, the correct answer is A (TRUE).

========

The statement is TRUE . Huawei’s official HUAWEI CLOUD Stack storage-resource documentation explicitly states that a storage backend can contain one or more storage pools of the same cloud block storage system , and it also clearly states that a storage backend only belongs to one AZ . This matches the wording of the question almost exactly. ( )

Huawei’s more recent resource-provisioning documentation repeats the same architecture principles: a storage pool belongs to only one storage backend , a disk type belongs to only one AZ , and a storage backend device can contain one or more storage pools . This design helps keep storage planning and fault-domain boundaries clear in multi-AZ cloud deployments. ( )

In practical HUAWEI CLOUD Stack operation, this means one backend can aggregate multiple pools from the same storage system for service use, but the backend itself is still scoped to a single availability zone for resource isolation and service planning. Therefore, the verified answer is A (TRUE) . ( )

========

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 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 correct answer is D. Changes of the VM CPU usage over time . OpenStack documentation describes Gnocchi as a time-series storage and resource indexing service . In the Telemetry pipeline documentation, OpenStack explicitly states that when the Gnocchi publisher is enabled, measurement and resource information is pushed to Gnocchi for time-series optimized storage . That makes Gnocchi the right component for storing metrics that change continuously over time, such as CPU utilization, memory usage, disk I/O, and similar performance measurements.

By contrast, the other options describe events, configuration changes, or audit-style records , which are not the primary use case for Gnocchi. OpenStack’s telemetry retrieval guidance recommends storing metric data in Gnocchi, while event data should be stored in an event-oriented service such as Panko. This clearly separates time-series metrics from event or log records.

Therefore, in Huawei Cloud Stack and OpenStack telemetry scenarios, Gnocchi is best suited for historical metric trends , making VM CPU usage over time the most appropriate choice.

========

After correcting the typing error, option A is still the invalid one. The correct Neutron legacy syntax is based on associating a floating IP with a port , not with a volume . Official OpenStack and Red Hat OpenStack command references show the valid legacy pattern as neutron floatingip-associate FLOATINGIP_ID PORT, meaning the floating IP ID is given first and the target must be a port ID or name . A volume ID does not belong in this operation.

OpenStack documentation also shows that the supported modern client approach is to use openstack server add floating ip < server > < ip-address > for server association, while older nova floating-ip-associate commands existed as legacy or deprecated commands. That means option D reflects a historical valid form, and option C reflects a Neutron-style valid form.

Option B is not the modern official syntax shown in current docs, but A is unquestionably invalid because it uses the wrong object type and wrong argument structure. For a single-answer exam question, the best verified answer is A .

========

The correct answer is A (TRUE) . Huawei Cloud Stack compute resource management documentation explicitly describes the behavior of soft-affinity , which is the practical equivalent of weak affinity in scheduling policy terms. Huawei states that if host resources are sufficient, VMs in the same soft-affinity group will be scheduled to the same host . It further states that if resources are insufficient or the current host is faulty, the VMs can be scheduled to different hosts . This matches the wording of the question almost exactly.

Huawei ECS group documentation also explains that an ECS group can be configured with affinity, anti-affinity, weak affinity, or weak anti-affinity policies, which confirms that weak affinity is an officially recognized scheduling policy in Huawei Cloud Stack. The “weak” part means the scheduler prefers a placement rule but is allowed to violate it when necessary to ensure successful deployment or continuity.

Therefore, the statement accurately reflects Huawei’s documented scheduling behavior: under normal conditions, VMs tend to be placed together, but if resources are inadequate, the rule may be broken. So the verified answer is TRUE .

Domain → A top-level container that is globally unique in Keystone

Role → Permission set

Endpoint → External access address of a single service

Group → User set

These matches are consistent with official OpenStack Keystone identity concepts. OpenStack documentation defines a group as a collection of users , so “user set” is the correct description for Group . It also explains that a role is used in Keystone’s RBAC model to represent a set of permissions that can be assigned to users or groups, so Role → Permission set is correct.

For Endpoint , OpenStack service configuration documentation describes endpoints as the network-accessible API addresses used to access a service, which matches external access address of a single service .

For Domain , Keystone identity documentation explains that domains are top-level containers used to organize projects, users, and groups. In practice, a domain is a globally unique administrative boundary in Keystone, which matches the description a top-level container that is globally unique in Keystone .

So the final verified mapping is: Domain → top-level container , Role → permission set , Endpoint → service access address , and Group → user set .

AS group → A set of instances with the same application scenario

AS policy → Specify the conditions for triggering an AS action

AS configuration → Define the specifications of the instance to be added

AS action → Its purpose is to keep the number of instances in the application system the same as expected

Comprehensive and Detailed 150 to 200 words of Explanation From HUAWEI CLOUD Computing Topics:

This matching is consistent with Huawei’s official Auto Scaling concept definitions. Huawei states that an AS group consists of a collection of instances that apply to the same application scenario , so that description belongs to AS group . Huawei also explains that an AS policy specifies the conditions for triggering a scaling action , which makes the second match straightforward.

Huawei’s Auto Scaling documentation further distinguishes AS configuration from policy and action. The configuration defines the template or specifications for the instances that will be added during scaling, so define the specifications of the instance to be added correctly matches AS configuration . Finally, Huawei defines a scaling action as adding or removing ECS instances from an AS group, and states that its purpose is to keep the number of instances in the application system at the expected level. That directly matches the final description.

So the verified drag-and-drop mapping is: group = instance set , policy = trigger condition , configuration = instance specification , and action = maintain expected instance count .

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.

========

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 FALSE . Official OpenStack Heat documentation says that when the Orchestration service was originally introduced, it worked with AWS CloudFormation templates , which are in JSON format. It then states that Heat also runs HOT templates written in YAML . This directly disproves the claim that both HOT and CFN templates support YAML in the same native sense.

OpenStack Heat documentation also explains that HOT was introduced to replace the Heat CloudFormation-compatible format (CFN) as the native format supported by Heat over time. That means HOT, not CFN, is the format more suitable for OpenStack-native deployments. The documentation further notes that YAML is easier to write, parse, and maintain, which is one reason HOT became the preferred OpenStack format.

Although internal parsing code shows the API can accept a JSON- or YAML-formatted document in some contexts, the OpenStack-native orchestration model clearly favors HOT and identifies CFN as the older CloudFormation-compatible format. So the combined statement is incorrect, and the correct answer is B (FALSE) .

========