Huawei H13-527_V5.0 - HCIP-Cloud Computing V5.0

CCS API → Provide the service logic of CCS tagging

CCS Console → Provide administrators with visualized CCS tagging

CCS Client → Provide administrators with cloud service tagging using CCS command lines

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

This drag-and-drop match follows the normal architectural roles of Huawei Cloud Stack CCS components. The CCS API is the backend service interface, so it is responsible for the service logic of CCS tagging . In cloud platforms, APIs handle request processing, tag creation, tag query, and tag-management actions exposed to other components or clients. The CCS Console is the graphical management interface, so its role is to provide administrators with visualized CCS tagging . This means administrators can perform tag-related operations through a web-based UI rather than command lines. The CCS Client is the command-line access component, so it is used to provide administrators with cloud service tagging using CCS command lines .

This mapping is also consistent with standard Huawei Cloud Stack component design principles: API for backend logic , Console for visual management , and Client for CLI-based operations . In practical cloud O & M and resource governance, these three components complement each other by supporting programmatic integration, web-based administration, and command-line automation. Therefore, the verified matching is: CCS API → service logic , CCS Console → visualized tagging , and CCS Client → command-line tagging .

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

The best verified answer is A, B, and D . Huawei networking documentation shows that Internet access troubleshooting for cloud resources commonly involves checking whether an EIP is bound or whether a NAT gateway is configured , which supports A . Huawei guidance also explicitly refers to selecting or checking an appropriate EIP bandwidth , which supports D as a normal troubleshooting item.

Huawei documentation also shows that network ACL rules are part of VPC access control and can affect connectivity. Because network ACLs are stateless and traffic validation depends on rule direction, checking ACL rules is a reasonable O & M troubleshooting operation. In your option wording, inbound rules are still part of that validation scope, so B is acceptable.

By contrast, checking route configurations on core switches is not the standard first-line troubleshooting action for tenant-side VPC Internet access in Huawei Cloud Stack service O & M. The cloud service boundary is usually diagnosed first through NAT, ACL, and EIP-related configuration. Therefore, the verified answer is A, B, and D .

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.

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 answer is A (TRUE) . Huawei Cloud Stack compute resource management documentation explicitly describes the behavior of soft-affinity , which is the practical equivalent of weak affinity in scheduling policy terms. Huawei states that if host resources are sufficient, VMs in the same soft-affinity group will be scheduled to the same host . It further states that if resources are insufficient or the current host is faulty, the VMs can be scheduled to different hosts . This matches the wording of the question almost exactly.

Huawei ECS group documentation also explains that an ECS group can be configured with affinity, anti-affinity, weak affinity, or weak anti-affinity policies, which confirms that weak affinity is an officially recognized scheduling policy in Huawei Cloud Stack. The “weak” part means the scheduler prefers a placement rule but is allowed to violate it when necessary to ensure successful deployment or continuity.

Therefore, the statement accurately reflects Huawei’s documented scheduling behavior: under normal conditions, VMs tend to be placed together, but if resources are inadequate, the rule may be broken. So the verified 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.

========