Huawei Updated H13-527_V5.0 Exam Questions and Answers by arjan

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

========

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 .

Comprehensive and Detailed 150 to 200 words of Explanation From HUAWEI CLOUD Computing Topics:

The correct answer is B. AutoOps . In HUAWEI CLOUD Stack, AutoOps is the automation platform used for standardized O & M task execution. Its core value is that it can take individual atomic operations and organize them into automated workflows, allowing repeated maintenance and troubleshooting procedures to be executed in a consistent, efficient, and less error-prone manner. This makes it highly suitable for routine operational tasks, fault handling, and platform maintenance scenarios where manual execution would be slower and more risky.

The other options have different roles. CMDB is mainly used for configuration and dependency information management. FusionCare is more focused on inspection, health check, and troubleshooting support. CloudNetDebug is designed for network fault diagnosis, especially for virtual network path troubleshooting. None of these primarily serve as the orchestration and automation engine for O & M workflows.

Therefore, when the requirement is to automate standardized operations and execute orchestration-based maintenance tasks in HUAWEI CLOUD Stack, the best answer is AutoOps , so the correct option is B .