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

The correct answer is D. Virtual Private Network (VPN) . Huawei’s official HUAWEI CLOUD Stack VPN documentation states that a VPN connection is an encrypted communications channel established between the VPN gateway in a VPC and the gateway in an external or local data center. Huawei also describes VPN as a way to connect a local data center to cloud resources through a secure and reliable encrypted tunnel over the Internet . This directly matches the requirement in the question for encrypting connections between cloud resources and local data centers.

By contrast, Direct Connect provides a dedicated, high-speed, low-latency connection, but the cited Huawei description emphasizes dedicated connectivity and stability rather than the VPN-style encrypted tunnel itself. EIP is only a public IP addressing service, and VPCEP is used for private access to services, not site-to-cloud encrypted interconnection. For small- and medium-sized enterprises that want a practical, secure, and relatively simple hybrid-cloud connection, Huawei documentation supports VPN as the best fit. Therefore, the verified answer is D .

The correct answer is B. BMS . For a typical web application architecture on HUAWEI CLOUD Stack, ECS provides the compute instances, IMS provides reusable images for quick deployment, AS enables elastic scale-out and scale-in based on demand, and ELB distributes traffic and improves availability. Huawei’s ECS and IMS documentation explicitly notes that ECS images can be used with Auto Scaling for dynamic expansion to meet peak demand, which directly supports quick deployment and elasticity.

BMS is a dedicated bare-metal service intended for scenarios needing direct physical hardware access, stronger isolation, or reduced virtualization overhead. It is useful for special workloads, but it is not required for the classic goals listed in the question, especially high cost-effectiveness and fast elastic web scaling. Those goals are more naturally achieved with ECS-based architectures plus ELB and AS. Huawei’s BMS positioning emphasizes physical-server management and performance advantages, not being a necessary part of a standard web application elasticity stack. Therefore, among the listed services, the one that is not required is BMS , making B the verified answer.

========

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

========

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

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 .

OpenStack is widely recognized for its openness, flexibility, and scalability . Official OpenStack documentation describes OpenStack as an open-source cloud platform that allows organizations to integrate different technologies and build clouds with a high degree of flexibility. It also explicitly highlights horizontal scalability , meaning compute, storage, and network resources can be expanded as demand grows. In addition, OpenStack and related OpenInfra materials consistently emphasize openness as a defining characteristic of the platform.

By contrast, efficiency is certainly a benefit that cloud platforms may deliver, but it is not typically presented as one of the foundational core concepts of OpenStack in the same way as openness, flexibility, and scalability. Huawei-authored OpenStack content also discusses OpenStack in terms of openness and scalability, which aligns with the standard industry description rather than listing efficiency as a core concept. Therefore, among the options given, Efficiency is the one that is not considered a core concept of OpenStack.

========

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 .

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