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

The correct answer is B. Managing the services or resources of branches across regions . In HUAWEI CLOUD Stack, resource sets are primarily used as an internal organizational and authorization tool within a tenant or VDC . They are well suited for grouping resources by department , project , or environment , such as production versus test resources. This means options A , C , and D are all typical and appropriate use cases because they involve structuring and controlling resources inside the same logical management domain. ( )

By contrast, managing services or resources of branches across regions is broader than the normal scope of a resource set. Cross-region branch management usually involves higher-level multi-region organizational constructs, regional administration, or broader tenant/VDC design rather than simply creating a resource set. Resource sets help refine governance inside an established tenant structure; they are not the main mechanism for organizing geographically distributed branch operations across regions.

So after correcting the wording, the scenario that is not suitable for resource sets is B , because it describes a cross-region management requirement that typically belongs to a higher-level cloud planning and governance model rather than a resource-set grouping function. Therefore, the verified answer is B .

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 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 answers are A and C. Huawei’s cloud-service monitoring documentation shows that administrators can view the cloud service topology and dependencies between the current cloud service and other cloud services. This is exactly the kind of capability enabled by a CMDB’s dynamic dependency model, and it clearly supports application deployment topology display, which corresponds to option C.

Dynamic dependency information is also highly relevant to root cause locating, because dependency graphs help O & M personnel trace failures from one service to dependent services and identify the likely upstream or downstream source of an issue. Huawei troubleshooting materials reference locating faults of dependent services, which aligns with option A.

By contrast, resource capacity planning is a capacity-management scenario rather than a dynamic-dependency scenario, and certificate replacement in batches is an operational maintenance task that does not primarily depend on CMDB dynamic dependencies. Therefore, the supported scenarios are A and C, making the verified answer A, C.

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.

========

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

========

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 .

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 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 B (FALSE) . Huawei documentation supports the first part of the statement: Combined API is described as providing the service backend for services such as ECS, BMS, IMS, and EVS , and Huawei usage materials show console requests being forwarded through the UI to Combined API for backend processing. That means it does function as a backend service layer between the console and underlying cloud services.

However, the statement becomes incorrect when it says Combined API must be deployed in the Global zone . Huawei architecture documentation explains that Huawei Cloud Stack includes both a global zone and regional deployment structure , and not all components belong to the global zone. Huawei snippets describing global-region deployment list typical global-zone components such as ManageOne and the cloud service console , while Combined API is described separately as a service backend in the broader architecture of the region/global deployment model. This supports the conclusion that Combined API is not simply a mandatory global-zone-only component .

So the backend-function part is true, but the deployment claim is not. Therefore, the overall statement is FALSE .

========