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

The best verified answer is A and D . Huawei’s official EVS documentation states that the major disk performance metrics include IOPS, throughput, and latency . Among the options given in your question, throughput is therefore definitely one of the major EVS disk metrics. ( ; )

In addition, Huawei EVS usage materials consistently treat capacity as a core disk attribute when defining EVS disks and their sizing. Although capacity is not a performance metric like throughput, exam questions of this type often use “major metrics” more broadly to mean the key measurable characteristics users pay attention to when selecting disks. By contrast, maximum snapshots is a feature limit rather than a primary disk metric, and endurance is not listed by Huawei as one of the standard major EVS disk metrics in the product guidance cited above.

So based on Huawei documentation and the exam-style wording, the most defensible answer is A and D : Throughput and Capacity . ( )

========

The correct fill-in answer is PB level . Huawei’s official HUAWEI CLOUD Stack SFS documentation states that the maximum capacity of a single file is 240 TB , and it further explains that the file system capacity can be scaled to the PB level . This is the exact Huawei wording used to describe the upper expansion capability of SFS.

This reflects the design goal of SFS in Huawei Cloud Stack: to provide managed, shared file storage for applications that require large-scale file-system growth over time. In other words, the size of one individual file and the total expandable capacity of the file system are two different things. A single file has a stated upper limit, but the whole file system can continue to grow far beyond that limit, reaching petabyte-scale capacity

Therefore, after correcting the sentence structure, the blank should be filled with PB level , which is the official Huawei description of the scalable upper capacity for the file system.

========

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.

========

In OpenStack, Keystone is the Identity service responsible for authentication and authorization. A core Keystone concept is that permissions are not usually granted directly to a user; instead, users are assigned one or more roles, and those roles are associated with a project, domain, or system scope. OpenStack’s official Keystone documentation states that the Identity service assigns roles to users, and a user can have different roles in different projects. It also explains that default roles such as admin, member, and reader are used to control what actions a user can perform. This means the statement is correct: Keystone users are assigned roles, and those roles determine their permissions.

This is also consistent with Huawei Cloud’s identity and permission model, where permissions are controlled through assigned authorization policies and identities use tokens containing identity and permission information when accessing services. In practical Huawei Cloud Stack and OpenStack-based environments, role-based access control is the standard method for defining what a user is allowed to do. Therefore, the correct answer is TRUE .

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

========

The correct answer is B (FALSE). Huawei documentation confirms that a dummy external network exists and may appear as an option when creating services such as VPC-related resources. Huawei’s Elastic IP and related network-service guidance gives examples such as selecting the dummy external network in one group and then selecting an actual Internet external network in another group for service use. This shows that the dummy external network is mainly a default placeholder or structural network object, not the real tenant-bound network required for service traffic.

Because of that, the second part of the statement is inaccurate. The proper requirement is not simply to “bind the dummy external network to tenants” so VPCs can be created properly. Instead, tenants and services need the correct actual external network resources and related mappings or selections. The Huawei examples make it clear that the dummy external network is not the operational external network used for normal connectivity. Therefore, although the first part about default creation is consistent with Huawei practice, the conclusion about binding it to tenants is not correct. For that reason, the full statement is FALSE.

========

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 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 fill-in answer is VPN gateway . In Huawei Cloud Stack networking, an EIP can be associated not only with an individual ECS, but also with shared-access components that serve multiple backend resources. Huawei documentation clearly states that when multiple cloud servers in a subnet need outbound Internet access, they can use a NAT gateway and share an EIP . Huawei’s ELB documentation also reflects the model where a load balancer exposes services externally on behalf of multiple backend ECSs.

In the same family of network services, a VPN gateway is another gateway-type object that uses public-facing connectivity to provide secure access for multiple private-side resources. That is why the exam sentence groups it with load balancer and NAT gateway . The logic is that these service gateways allow multiple ECSs or private resources to make use of a single public-facing IP resource instead of requiring one EIP per server. Huawei’s VPN service documentation also shows VPN as the gateway-based service for secure site-to-cloud communication.

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

========