Huawei H13-527_V5.0 HCIP-Cloud Computing V5.0 Exam Practice Test

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) .

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 .

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 D . Huawei’s official HUAWEI CLOUD Stack NAT Gateway documentation explains that DNAT is used to map the private IP address and port of a cloud server in a VPC to a public IP address and port by binding an EIP. In practical terms, DNAT allows requests that arrive at a public IP address to be forwarded to the private IP address of a server inside the cloud network. That matches option D exactly.

Option A describes SNAT , not DNAT. Huawei explicitly states that SNAT translates a private IP address into an extranet/public IP address so cloud servers can access the Internet. Option B is also related to SNAT behavior, because Huawei notes that multiple cloud servers in a VPC can share an EIP for outbound Internet access through SNAT. Option C describes a filtering or firewall-style function rather than NAT translation.

Therefore, in Huawei Cloud Stack networking, DNAT is specifically used for inbound mapping from public addresses to private cloud-server addresses , so the verified answer is D .

========

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.

========

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. ( )

========

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 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 .

The correct answer is C. Unified hardware model. Huawei’s System Integration description states that it provides a unified access mode and drive development standard for connecting cloud platforms to ManageOne. Huawei’s cloud-service architecture materials also explicitly reference items such as Unified Authentication, which is part of the common-component layer used during login and service access.

Within Huawei Cloud Stack’s unified access and integration model, service-facing capabilities such as unified service catalog, unified authentication, and unified metering belong to the logical platform-access specification set. These are cloud-management and service-governance functions. By contrast, unified hardware model does not fit that category, because the “10 Unified Access Specifications” are about access, integration, management, and service consistency, not about forcing all infrastructure hardware into one model. Huawei Cloud Stack supports heterogeneous infrastructure and abstracts it through the platform rather than treating “unified hardware model” as an access specification. Therefore, the item that is not included is C.

========

The correct answers are A, B, and D. Huawei’s official ECS documentation highlights several elasticity-related capabilities. It states that Auto Scaling (AS) can automatically add or remove ECSs based on service demand, which directly supports option B. Huawei also states that ECS flavors can be modified, including changes to CPU and memory, which supports D as an elastic scaling feature. In addition, Huawei’s IMS documentation explains that images can be used to create ECSs in batches and, together with AS, support dynamic scale-out, which makes A a valid reflection of ECS elasticity as well.

Option C is not well supported as stated, because Huawei documentation emphasizes flavor modification and online flavor change mainly in the context of scaling resources, especially increasing CPUs and memory, not “specification downgrade” as a core elasticity feature. Option E refers to physical isolation, which is a BMS characteristic rather than an ECS elasticity feature. Therefore, the best verified answer is A, B, D.

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 answers are B, C, and D. Huawei’s official resource-analysis documentation states that bottleneck resources can be identified and analyzed globally and by VDC, resource pool, and application. This directly matches options B, C, and D in your question.

Although Huawei also has resource-pool analysis views that can monitor resources from multiple dimensions such as region, resource pool, and AZ, the specific wording for bottleneck analysis in the cited Huawei documentation highlights application, VDC, and resource pool as the relevant factors used for bottleneck identification and analysis. That is why AZs should not be selected for this particular question.

So, after correcting the sentence structure, the supported dimensions for bottleneck-related analysis by O & M administrators are applications, VDCs, and resource pools. Therefore, the verified answer is B, C, D.

========

Developers → Users can only log in to the ECS using VNC. They cannot change the ECS specifications.

O & M personnel → An ECS can be restarted, but the system or software version cannot be upgraded.

Financial personnel → Users can only view cost reports. They cannot perform operations on resources.

This matching follows the least-privilege principle used in HUAWEI CLOUD Stack permission design. Huawei documentation emphasizes separating user responsibilities and assigning permissions based on operational roles, so users receive only the minimum capabilities required for their work. Huawei also describes resource grouping and user-group-based authorization as a standard way to control who can apply for or manage resources.

Based on that model, financial personnel should have the narrowest access, limited to viewing cost reports without operating resources. Developers usually need access to instances for testing or development work, but under minimum-permission security they should not be allowed to alter infrastructure specifications, so VNC-only login without ECS specification changes is the best match. O & M personnel need more operational control than developers, such as basic restart capability, but under minimum permissions they still should not perform higher-risk actions like upgrading the system or software version unless explicitly authorized. This division reduces accidental changes, lowers operational risk, and aligns with Huawei Cloud Stack’s role-based access and tenant/resource governance approach.

The correct answer is C. show . Official OpenStack command-line documentation explicitly lists the command openstack server show < 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 < server > . That makes the correct answer C .

========

The correct answer is B. VM performance deteriorates. Huawei’s official Resource Audit Overview for HUAWEI CLOUD Stack explains that Service OM resource audit is designed for high-frequency exception types caused by unplanned system failures, such as host reboot, process restart, or backup recovery. Huawei explicitly states that resource audit is used when problems such as residual resources and unavailable resources occur after those events. This directly matches options C and D. The same audit section also covers scenarios like abnormal VM states, orphan VMs, fake VMs, and image or volume inconsistencies caused by restoration or failed processes.

By contrast, VM performance deterioration is a performance management or capacity tuning issue, not a resource-audit exception type. Huawei’s compute resource management materials discuss performance tuning separately, such as changing VM flavors or adjusting resources, which shows that performance degradation is not handled by the Service OM resource-audit function itself. Therefore, among the four options, the issue that cannot be handled by Service OM’s resource audit is B.

========

The correct answer is B. L3 Agent . Official OpenStack Neutron documentation states that routers provide virtual Layer 3 services such as routing and NAT , and that the Networking service uses a layer-3 agent to manage routers. OpenStack also explicitly says that the neutron-l3-agent uses the Linux IP stack and iptables to perform L3 forwarding and NAT . This directly matches the wording of the question.

The other options do not fit. The L2 agent handles local virtual switch configuration and Layer 2 networking behavior, not routing and NAT. The DHCP agent provides DHCP services to tenant networks. “ NAT Agent ” is not the standard Neutron component name used in official OpenStack architecture. OpenStack documentation consistently identifies the L3 agent as the component responsible for router namespace management, forwarding, floating IP behavior, and source NAT functions.

This is also consistent with Huawei Cloud Stack networking architecture topics, where routing and NAT functions are tied to Neutron Layer 3 services. Therefore, the fully verified answer is B. L3 Agent .

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 correct fill-in answer is FTP. Huawei documentation for image registration on Service OM shows that images can be uploaded using different modes, including local upload, FTP, and NFS. The guidance indicates that for larger image files, administrators should use a network-based upload mode rather than simple local browser upload. In the Huawei document snippet, the upload options explicitly include NFS, and the paired option used in this context is FTP, which matches the exam sentence structure: “select ____ or NFS.”

This makes sense operationally in HUAWEI CLOUD Stack because large image files are more reliably transferred through shared file or server-based methods, especially in enterprise O & M scenarios. Local browser-based uploads are less suitable for very large images due to session stability, browser limits, and transfer reliability. Using FTP or NFS improves image registration efficiency and reduces the chance of interrupted uploads during image onboarding. Therefore, after correcting the sentence, the blank should be filled with FTP.

========