H13-527_V5.0 HCIP-Cloud Computing V5.0 Questions and Answers

The correct answer is B. Querying VM memory usage every 10 minutes . OpenStack Telemetry documentation states that the Telemetry service polls service APIs every 10 minutes by default , and that this interval can be changed in polling.yaml. That is exactly the behavior of a polling agent: it periodically queries metrics rather than waiting for events.

Ceilometer measurement documentation also includes metrics such as memory.usage, which shows that VM memory usage is one of the kinds of resource data that polling-based telemetry can collect, depending on configuration and hypervisor support.

The other options describe different telemetry-related functions. Reporting alarms is associated more with alarming services such as Aodh, listening to VM deletion events corresponds to event-driven notification collection rather than polling, and storing event logs is a storage or event-backend function rather than the polling agent’s role. Therefore, the typical example of a polling agent’s work is periodic metric collection, making B the fully verified answer. This also aligns with Huawei Cloud Stack monitoring and O & M concepts built on OpenStack telemetry principles.

The correct answer is C. Tenant application response time . Huawei’s comprehensive monitoring documentation states that service monitoring tests the health of the current application and locates application exceptions based on monitoring metrics such as response time and availability . That directly matches the scenario of monitoring tenant application response time .

The other options belong to different monitoring domains. Health status of the physical server power supply is hardware or infrastructure monitoring, not service monitoring. Virtual network congestion is a network-layer performance issue rather than an application service-monitoring scenario. Latency of the distributed tracing system is closer to tracing or APM platform internals than to the application service-monitoring scenario explicitly described in Huawei’s cited service-monitoring definition. Huawei’s wording focuses on the monitored application’s health, response time, and availability, not hardware power modules or tracing-platform latency.

Therefore, based on Huawei’s official description of comprehensive service monitoring , the scenario clearly covered is tenant application response time , making the verified answer C .

The correct answer is C. Quick and elastic adjustment of CPUs and memory . Huawei’s official HUAWEI CLOUD Stack materials describe Bare Metal Server (BMS) as dedicated physical servers that provide excellent or remarkable computing performance and direct access to physical resources. Huawei also explains that Ironic works with Nova and Neutron to manage BMS resources, highlighting the physical-server nature of the service. These characteristics support advantages such as physical isolation , no hypervisor performance overhead , and direct access to specialized hardware .

By contrast, Huawei’s ECS Advantages documentation explicitly says that with ECS, administrators can modify an ECS flavor, including the number of CPUs and memory size . That kind of quick and elastic CPU/memory adjustment is therefore an ECS advantage , not a BMS-over-ECS advantage.

So after correcting the option formatting, A , B , and D are all real BMS strengths, while C belongs more to virtualized ECS elasticity. Therefore, the verified answer is C .

========

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 correct answer is D. Resource pool and basic cloud service management . Huawei’s official License Guide includes a dedicated section called “Resource Pool & Basic Cloud Services” and explicitly instructs administrators to enter Service OM to perform management actions there. This directly ties Service OM to the management plane for resource pools and basic cloud services , rather than positioning it primarily as a hardware-monitoring tool or a deployment platform.

Huawei Cloud Stack O & M materials also show Service OM being used for operational management tasks such as viewing VMs, host groups, cloud services, and system resource status. In contrast, deployment and upgrade are associated with dedicated installation and upgrade tools, not Service OM as the main function. Similarly, centralized monitoring across products is broader than Service OM’s core purpose and is covered by other monitoring and O & M capabilities in the Huawei Cloud Stack architecture.

Therefore, among the available choices, the description that best matches Huawei’s official positioning of Service OM is resource pool and basic cloud service management . That makes D the most accurate and fully verified answer.

========

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 statement is TRUE according to the official HOT specification. OpenStack Heat documentation shows the overall HOT structure and explains that heat_template_version identifies the YAML document as a HOT template of a specific version. This key is fundamental because it tells Heat which template format and feature set to validate.

The same HOT specification states that the resources section contains the declaration of the resources in the template and that this section with at least one resource should be defined in any HOT template , otherwise the template would not really do anything when instantiated. In other words, a valid HOT template intended to deploy a stack needs both the version declaration and a resource definition.

Other sections such as description, parameters, outputs, and conditions are documented as optional. That is why heat_template_version and resources stand out as the core required parts for normal HOT authoring. In Huawei Cloud Stack training contexts based on OpenStack Heat, these are treated as the mandatory structural elements of a HOT template. Therefore, the verified 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 . In OpenStack Neutron, VXLAN uses a VNI (VXLAN Network Identifier) as the segmentation identifier for overlay networks. Official OpenStack Neutron configuration references describe vni_ranges as the range of VXLAN VNI IDs available for tenant network allocation , which confirms that the VNI is the central identifier used for VXLAN-based Neutron networks.

OpenStack networking documentation also explains that Neutron supports project networks and allows different projects to use overlapping IP spaces while remaining logically separated. In VXLAN/GRE tunnel realizations, OpenStack documents refer to a logical switch identifier being used to differentiate tenant traffic on inter-hypervisor tunnels , which is the practical mechanism for tenant isolation.

So, in Huawei Cloud Stack or any OpenStack-based multi-tenant cloud, the VNI functions as the unique overlay-network identifier that keeps one tenant’s VXLAN traffic separate from another tenant’s traffic. That is why the statement is correct and the verified answer is A (TRUE) .

========

The correct answer is B (FALSE) . Huawei documentation confirms that FusionCare is a deployed component used for inspection and troubleshooting , but the statement’s deployment location is not reliably correct as written. In Huawei Cloud Stack maintenance and troubleshooting materials, Huawei explicitly references logging in to FusionCare separately and also notes cases where administrators must obtain the IP address of the node where FusionCare is deployed , which shows it is treated as a specific deployable node/service rather than a fixed default identity tied universally to PUB-SRV-01 .

More importantly, Huawei documentation for certificate replacement states that administrators may need the IP address of the PUB-SRV03 node where FusionCare is deployed , which directly contradicts the claim that FusionCare runs on PUB-SRV-01 by default. Huawei O & M rollback documents also mention checking whether FusionCare is deployed in each secondary region , indicating that its deployment is not always a single fixed-node default in the simplistic way the statement suggests.

So, although FusionCare is indeed part of Huawei Cloud Stack O & M, the statement is inaccurate because the node/location claim is not universally true. Therefore, the verified answer is FALSE .

========

The statement is TRUE . In HUAWEI CLOUD Stack, a resource set is a logical grouping of cloud resources under a tenant or VDC for purposes such as authorization, organization, and management. Huawei documentation describes resource sets as being used to classify and manage resources within a tenant context, which means their scope is tied to the tenant’s own resource domain. This is why resource sets are commonly used to separate production, test, departmental, or project resources inside the same tenant or VDC rather than as a cross-tenant migration mechanism. ( )

Operationally, resources can be reassigned or moved between resource sets when administrators need to reorganize management boundaries, but the resource-set model itself is not designed to move resource sets across tenants . Cross-tenant transfer would break the tenant-based isolation and authorization structure that Huawei Cloud Stack uses for cloud governance. This is consistent with Huawei’s hierarchical cloud management approach, where tenants are major security and administration boundaries, while resource sets are subordinate organizational tools. Therefore, the verified answer is A (TRUE) because resource migration between resource sets is allowed within the management domain, but resource sets themselves are not intended for migration across tenants. ( )

========

The correct answer is C. show . Official OpenStack command-line documentation explicitly lists the command openstack server show <</b> server > and explains that it is used to show server details . The same documentation states that the < server > argument represents the server name or ID , which matches the wording in your question exactly.

The other options are not correct in this context. openstack server list displays a list of servers rather than the details of one specific instance. query and conf are not valid standard subcommands for this OpenStack server-detail operation. Since HUAWEI CLOUD Stack operations in this area follow OpenStack command syntax for instance inspection and lifecycle management, the proper command for viewing one instance’s details is openstack server show < server > .

Therefore, after correcting the sentence format, the blank should be filled with show , and the full verified command is openstack server show <</b> server > . That makes the correct answer C .

========