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

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 statement is TRUE . Official OpenStack documentation describes Cinder, the Block Storage service, as providing on-demand, self-service access to block storage resources via abstraction and automation on top of other block storage devices . That wording is important because it shows that Cinder is not itself a physical storage technology . Instead, it presents a unified service layer that works with many different backend storage systems through drivers.

OpenStack storage architecture documentation also explains that Block Storage supports multiple back ends in the form of drivers , and the actual storage implementation depends on the chosen backend technology. In other words, Cinder exposes APIs and management functions for volumes, snapshots, and related features, while the real block storage is delivered by backend platforms such as SAN, distributed storage, or vendor storage arrays.

This matches Huawei Cloud Stack storage concepts as well, where cloud services are typically built on an abstraction layer to unify heterogeneous resources. Therefore, the correct answer is A (TRUE) , because Cinder serves as an abstraction and orchestration layer over underlying block storage systems rather than being the storage technology itself.

========

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

========

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 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 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 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 answer is D. Resource pool and basic cloud service management . Huawei’s official License Guide includes a dedicated section called “Resource Pool & Basic Cloud Services” and explicitly instructs administrators to enter Service OM to perform management actions there. This directly ties Service OM to the management plane for resource pools and basic cloud services , rather than positioning it primarily as a hardware-monitoring tool or a deployment platform.

Huawei Cloud Stack O & M materials also show Service OM being used for operational management tasks such as viewing VMs, host groups, cloud services, and system resource status. In contrast, deployment and upgrade are associated with dedicated installation and upgrade tools, not Service OM as the main function. Similarly, centralized monitoring across products is broader than Service OM’s core purpose and is covered by other monitoring and O & M capabilities in the Huawei Cloud Stack architecture.

Therefore, among the available choices, the description that best matches Huawei’s official positioning of Service OM is resource pool and basic cloud service management . That makes D the most accurate and fully verified answer.

========

The best verified answer is D. Workspace . Huawei’s official health-check documentation for FusionCare shows that FusionCare supports unified health checks for multiple Huawei Cloud Stack components and services. The published health-check item lists explicitly include Service OM , eSight , and CCE and SWR , which confirms that those services are within FusionCare’s supported inspection scope.

By contrast, the Huawei monitoring materials mention Workspace Overview under broader monitoring capabilities, not under the FusionCare-supported health-check list shown in the cited documents. In other words, Workspace appears in Huawei’s overall monitoring ecosystem, but it is not evidenced in the cited FusionCare support list the way Service OM, eSight, and CCE are. That makes Workspace the option that cannot be checked using FusionCare in this question set.

So based on Huawei’s documented FusionCare-supported inspection items, A , B , and C are covered, while D is not shown as a FusionCare check target. Therefore, the verified answer is D .

========

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 best verified answer is A. AutoOps built-in scripts . Huawei’s HUAWEI CLOUD Stack O & M documentation states that Automated Jobs automatically detect faults of each cloud service , and that the automation scripts or jobs of each cloud service are displayed and can be centrally managed . That makes AutoOps built-in scripts the most suitable choice for quick diagnosis when VM migration failures happen repeatedly, because this is exactly the kind of recurrent platform-side fault scenario where automated diagnosis scripts are useful.

The other tools are more specialized for different problem domains. CloudNetDebug is described by Huawei as a network diagnosis tool on virtual networks and is mainly used to detect network traffic interruption, packet loss, and full-link virtual network faults. Call chain is associated with application tracing or APM-style request tracing, not VM migration troubleshooting. ECS storage troubleshooting tools are aimed at storage-related fault analysis rather than general VM migration diagnosis.

Therefore, for fast diagnosis of frequent VM migration failures in Huawei Cloud Stack O & M, the most appropriate tool is AutoOps built-in scripts , so the verified answer is A .

========

Domain → A top-level container that is globally unique in Keystone

Role → Permission set

Endpoint → External access address of a single service

Group → User set

These matches are consistent with official OpenStack Keystone identity concepts. OpenStack documentation defines a group as a collection of users , so “user set” is the correct description for Group . It also explains that a role is used in Keystone’s RBAC model to represent a set of permissions that can be assigned to users or groups, so Role → Permission set is correct.

For Endpoint , OpenStack service configuration documentation describes endpoints as the network-accessible API addresses used to access a service, which matches external access address of a single service .

For Domain , Keystone identity documentation explains that domains are top-level containers used to organize projects, users, and groups. In practice, a domain is a globally unique administrative boundary in Keystone, which matches the description a top-level container that is globally unique in Keystone .

So the final verified mapping is: Domain → top-level container , Role → permission set , Endpoint → service access address , and Group → user set .

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 answers are B and C . Huawei documentation states that a security group is a collection of access control rules used to protect cloud servers or instances added to that group. Huawei also describes a network ACL as a security service for VPCs or subnets , which means it protects traffic at the subnet level rather than directly protecting individual instances. That makes C correct.

Huawei’s comparison guidance also distinguishes the way rules are processed. Security groups are stateful and their rules work together as a combined access-control set, while network ACLs are processed according to rule priority , which makes B correct. The official Huawei comparison page explicitly frames network ACLs as an additional security layer on top of security groups.

Option A is incorrect because network ACLs are not mandatory by default in the same way security-group association is standard for instances. Option D is not supported by the Huawei VPC/network ACL documentation cited here; the docs emphasize instance-vs-subnet scope and rule handling, not that exact 5-tuple versus 3-tuple split for these two features. Therefore, the best verified answer is B, C .

========