H13-527_V5.0 Exam Dumps - Huawei HCIP-Cloud Computing Questions and Answers

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 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 PKI. In OpenStack Keystone, PKI (Public Key Infrastructure) tokens are cryptographically signed and specifically rely on a public/private key pair. Official OpenStack Keystone documentation states that PKI tokens are signed documents and that the Identity service uses public/private key pairs and certificates to create and validate them. It also explains that PKI and PKIZ tokens can be verified offline using Keystone’s public signing key, which directly matches the wording in the question about signing and verification.

By contrast, UUID tokens are simple persisted identifiers and do not inherently depend on public/private key signing. Fernet tokens are also a Keystone token format, but they are based on symmetric cryptography and shared key repositories rather than a public/private key pair. OpenStack documentation explicitly distinguishes Fernet and UUID from the deprecated PKI token mechanism. Therefore, among the listed options, the authentication method that uses a pair of private and public keys is clearly PKI. This aligns with standard OpenStack identity-service architecture and is consistent with Huawei Cloud Stack training topics that build on Keystone authentication concepts.

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

========

After correcting the wording, the best verified answer is C . Standard Huawei OBS access methods include the console , RESTful APIs , and SDKs . Huawei OBS documentation and related Huawei service guides consistently describe OBS as being accessed through API-based methods and software-development toolkits, and many Huawei cloud services explicitly reference RESTful and SDK interaction with OBS resources.

Option C is different. Although some Huawei cloud-native scenarios allow OBS buckets to be mounted to workloads in CCE through OBS volumes, that is a specialized container-storage integration scenario, not the standard administrator access method for OBS itself. Huawei’s CCE documentation also warns about constraints and resource overhead when OBS buckets are mounted to workloads, which reinforces that this is not the normal general-purpose way an administrator “accesses OBS.”

So for exam-style classification, A , B , and D are the normal access methods, while C is not the standard answer. Therefore, the correct answer is C .

========

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

========

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 correct answer is C. Format a physical storage device . Official OpenStack Cinder documentation shows that the Block Storage API supports operations such as attaching a volume to an instance , creating snapshots , and resizing/extending volumes . The Cinder CLI and API references explicitly list volume attachment, snapshot-related operations, and extend or resize functions as supported capabilities.

By contrast, formatting a physical storage device is not a standard function of the Cinder API. Cinder provides a cloud block storage service layer and interacts with backend storage through drivers, but low-level formatting of physical disks is a backend storage administration task rather than a tenant-facing or standard Cinder API operation. The Cinder service abstracts backend complexity and exposes logical operations on volumes, not raw hardware provisioning steps such as formatting a physical device.

In Huawei Cloud Stack and OpenStack-based environments, this distinction is essential: cloud users and administrators manage logical block storage resources through Cinder, while backend storage initialization and device formatting are handled outside normal Cinder-API operations. Therefore, the verified answer is C .

========