H13-528 HCIP-Cloud Computing Solution Architect Guide

Designing a cloud platform is about much more than deploying virtual machines or connecting servers to a network. A successful cloud solution must balance performance, availability, scalability, security, operational complexity, and business requirements. These are precisely the challenges that make cloud solution architecture an important discipline in enterprise IT.

The HCIP-Cloud Computing Solution Architect (H13-528) certification focuses on the technical knowledge needed to understand and design cloud computing solutions based on technologies such as Huawei Cloud Stack, OpenStack, Kubernetes, databases, and big data platforms.

For networking students, system administrators, and IT professionals moving toward cloud architecture, H13-528 provides a structured way to develop knowledge beyond traditional infrastructure administration.

In this guide, we will examine the certification’s technical scope, explain the architectural concepts behind its major subjects, discuss its potential career value, and outline a practical preparation strategy.

What Is HCIP-Cloud Computing Solution Architect (H13-528)?

HCIP stands for Huawei Certified ICT Professional. Within Huawei’s certification framework, HCIP represents professional-level knowledge in a specific ICT technology domain.

The HCIP-Cloud Computing Solution Architect certification concentrates on enterprise cloud architecture, particularly solutions built around Huawei Cloud Stack and related cloud-native technologies.

Unlike a course that primarily teaches administrators how to operate individual infrastructure components, solution architecture requires a broader perspective. Architects must understand how computing, networking, storage, applications, and management systems interact to deliver a complete solution.

For example, an administrator might be responsible for deploying a virtual machine. A solution architect must also determine which resource pool should host the machine, how its network should be isolated, what availability requirements apply, how its storage should be protected, and whether the application would benefit from containerization.

That distinction is central to understanding the value of the H13-528 learning path.

H13-528 Certification Exam Overview

The following table summarizes commonly published information about the HCIP-Cloud Computing Solution Architect V1.0 examination.

Important: Exam duration, question count, passing score, examination fees, available languages, certification versions, and registration eligibility can change. The figures above are reported by third-party preparation resources and should not be treated as confirmation of current Huawei examination policy. Always verify the latest details through Huawei’s official certification portal before scheduling an examination.

For learners planning their certification journey, reviewing structured H13-528 exam preparation resources can help organize the major topics and identify areas that require additional study.

H13-528 Exam Syllabus and Knowledge Areas

The published H13-528 V1.0 syllabus organizes the examination into seven major domains. Understanding how these subjects connect is more useful than studying each topic in isolation.

These percentages reflect publicly available V1.0 syllabus summaries. Candidates should consult the latest official examination outline for their actual test version.

Two areas deserve particular attention: cloud-native technologies and Huawei Cloud Stack planning and design. Together, they account for 45% of the published syllabus.

However, the remaining subjects should not be underestimated. A sound cloud architecture depends on correctly integrating the infrastructure, networking, application, and data layers.

1. OpenStack: Understanding the Foundation of Cloud Infrastructure

OpenStack is an open-source cloud infrastructure platform that provides services for managing computing, networking, storage, and related cloud resources.

It plays an important role in understanding how infrastructure-as-a-service (IaaS) environments are organized and automated.

Important OpenStack Components

Several core OpenStack projects are particularly useful for H13-528 preparation:

• Nova: Manages the lifecycle of compute instances and coordinates virtual machine provisioning.
• Neutron: Provides networking capabilities, including logical networks, subnets, routers, and connectivity services.
• Cinder: Delivers persistent block storage services for cloud workloads.
• Glance: Manages images used to deploy virtual machine instances.
• Keystone: Provides identity management, authentication, and authorization services.
• Horizon: Offers a web-based interface for interacting with supported OpenStack services.
• Heat: Enables infrastructure orchestration through templates.

How OpenStack Services Work Together

Consider a request to create a new virtual machine.

The cloud platform must authenticate the user, determine whether the requested resources are permitted, locate appropriate compute capacity, select an operating system image, allocate storage, and establish network connectivity.

OpenStack services cooperate to perform these operations. Keystone handles identity-related functions, Nova coordinates compute provisioning, Glance provides image information, and Neutron manages the logical networking requirements. Cinder participates when persistent block volumes are requested.

The actual workflow involves additional services, drivers, and scheduling decisions, but this simplified example demonstrates why architects need to understand component relationships.

Study recommendation: Learn what each major OpenStack service does, then practice explaining how multiple services cooperate during resource provisioning.

2. Huawei Cloud Stack Architecture and Core Components

Huawei Cloud Stack is Huawei’s cloud platform solution for enterprise and government environments that require cloud capabilities within customer-controlled infrastructure.

Organizations may choose this approach when they need greater control over infrastructure placement, security boundaries, data governance, and integration with existing data center systems.

Understanding the Cloud Architecture Layers

From a solution design perspective, a cloud platform can be understood through several logical layers:

• Physical infrastructure: Servers, storage systems, network devices, and data center facilities.
• Infrastructure resource layer: Virtualization and resource-pooling capabilities that abstract physical resources.
• Cloud service layer: Services that provide compute, storage, networking, and other capabilities to applications and tenants.
• Management and operations layer: Functions supporting resource administration, monitoring, service delivery, and operational governance.
• Application layer: Enterprise workloads, databases, business applications, and containerized services.

This is a conceptual model rather than a product-specific deployment diagram. Actual Huawei Cloud Stack components and their interactions depend on the platform release and selected deployment architecture.

Resource Pools and Multi-Tenant Design

Resource pooling allows cloud infrastructure to allocate shared physical capacity to different workloads according to defined policies.

Multi-tenancy introduces another architectural requirement: workloads belonging to different organizations, departments, or applications may need logical separation.

For example, a university operating an internal cloud platform could provide separate resource allocations for its research, administrative, and teaching departments.

The architecture must define access permissions, network boundaries, resource quotas, and operational responsibilities without unnecessarily duplicating physical infrastructure.

Understanding these design decisions is essential for moving from basic infrastructure knowledge to solution architecture.

3. Huawei Cloud Stack Networking Architecture

Networking is one of the most important areas for students with a traditional routing and switching background.

In a virtualized cloud, connectivity is no longer defined exclusively by physical switches and routers. Virtual networking technologies provide logical connectivity, isolation, and scalable network services across shared infrastructure.

VXLAN and Network Virtualization

Virtual Extensible LAN (VXLAN) is an overlay networking technology that encapsulates Layer 2 Ethernet frames within UDP packets over an IP underlay network.

Its main purpose is to support scalable logical networks across physical infrastructure.

VXLAN uses a 24-bit VXLAN Network Identifier (VNI), providing a much larger logical segmentation space than traditional 12-bit VLAN identifiers.

For a cloud architect, the important distinction is between the underlay, which carries packets through the physical IP network, and the overlay, which creates tenant-facing logical connectivity.

VRF and Tenant Isolation

Virtual Routing and Forwarding (VRF) enables separate routing tables to coexist on shared networking infrastructure.

This is useful when multiple tenants require independent routing domains or overlapping IP address spaces.

However, VRF alone does not provide a complete security architecture. Access control policies, firewall services, and appropriate management-plane isolation are also necessary.

Network Architecture Questions Worth Practicing

• How does traffic travel between two workloads on the same logical network?
• What changes when two workloads are placed on different logical networks?
• How should north-south traffic be controlled at a cloud boundary?
• How can an architect separate tenant networks while sharing physical resources?
• What happens to connectivity when an underlying network component fails?

These questions encourage architectural thinking rather than simple memorization of networking terminology.

4. Cloud-Native Architecture and Kubernetes

Cloud-native technology represents one of the most significant shifts in modern enterprise application design.

Traditional applications were often designed around individual servers or long-lived virtual machines. Cloud-native applications increasingly use containers, automation, service-oriented designs, and orchestration platforms.

The H13-528 syllabus gives substantial attention to this subject, making Kubernetes knowledge particularly valuable.

Containers Versus Virtual Machines

Virtual machines use a hypervisor to run separate guest operating systems on shared hardware. Containers generally share the host operating system kernel while isolating application processes and their dependencies.

Because containers do not normally require a complete guest operating system for each workload, they can provide efficient application packaging and relatively fast startup.

However, containers do not eliminate the need for virtual machines. Many enterprise cloud platforms run Kubernetes worker nodes as virtual machines, combining the operational benefits of both technologies.

Essential Kubernetes Concepts

• Cluster: A collection of control-plane and worker-node resources used to run containerized workloads.
• Pod: The smallest deployable unit in Kubernetes, containing one or more closely related containers.
• Deployment: Manages the desired state and updates of stateless application workloads.
• Service: Provides a stable network abstraction for accessing a group of application endpoints.
• Ingress: Defines HTTP and HTTPS routing rules for accessing services, when supported by an appropriate controller.
• ConfigMap: Stores non-confidential application configuration data.
• Secret: Holds sensitive configuration values, requiring suitable access controls and protection.
• PersistentVolume: Represents storage resources available to containerized workloads.

Example: Deploying a Simple Application

A basic Kubernetes Deployment can describe the desired number of application replicas and the container image to run.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-demo
spec:
  replicas: 3
  selector:
    matchLabels:
      app: web-demo
  template:
    metadata:
      labels:
        app: web-demo
    spec:
      containers:
        - name: nginx
          image: nginx:stable
          ports:
            - containerPort: 80

This example requests three replicas of an Nginx application. Kubernetes attempts to maintain the desired replica count through its controllers and scheduling mechanisms.

For a production environment, additional configuration would be necessary, including resource requests and limits, health probes, image security policies, workload access controls, and appropriate network services.

Huawei Cloud Container Engine (CCE)

Huawei Cloud Container Engine (CCE) provides Kubernetes-based capabilities for deploying and managing containerized applications.

CCE-related technologies are relevant because architects must understand how container platforms integrate with cloud computing, networking, storage, monitoring, and application management.

When studying CCE, pay attention to cluster architecture, node and workload management, service exposure, persistent storage, and the operational requirements of running applications at scale.

Capabilities and management procedures can differ between Huawei Cloud public cloud offerings and Huawei Cloud Stack releases. Always use documentation appropriate to the platform covered by your training materials.

5. Database Technologies in Cloud Solution Architecture

Databases are fundamental to enterprise applications, but database selection should never be treated as an isolated product decision.

An architect must consider data structure, query patterns, consistency requirements, recovery objectives, transaction characteristics, and expected workload growth.

Relational and Non-Relational Databases

Relational databases organize information into structured tables and commonly use SQL to query and manipulate data.

They are especially useful for applications requiring structured relationships, transactional integrity, and well-defined consistency controls.

Non-relational databases include document, key-value, column-family, and graph-oriented systems. These models can be useful for workloads with different access patterns, scalability requirements, or data structures.

Neither category is universally superior. The correct decision depends on the application and its operational requirements.

High Availability and Data Protection

Database architecture must account for infrastructure failures, application failures, and data corruption.

Replication can improve availability, but replication alone is not a substitute for recoverable backups. Logical mistakes or corrupted data may also propagate to replicas.

Two useful concepts are:

• Recovery Point Objective (RPO): The maximum acceptable period of data loss measured in time.
• Recovery Time Objective (RTO): The maximum targeted time for restoring a service after disruption.

For instance, an application with an RPO of five minutes requires a protection strategy designed to limit data loss to approximately five minutes or less during applicable failure scenarios.

Architects must translate these requirements into appropriate replication, backup, recovery, and monitoring designs.

6. Big Data Technologies and Enterprise Workloads

Big data technologies help organizations process and analyze datasets that may be too large, diverse, or demanding for conventional data-processing approaches.

In enterprise environments, big data platforms often support operational analytics, log processing, business intelligence, machine learning pipelines, and large-scale data integration.

Understanding Common Big Data Components

Students preparing for H13-528 should become familiar with the roles of several widely used technologies:

• Hadoop: An ecosystem associated with distributed storage and processing of large datasets.
• HDFS: A distributed filesystem designed for storing data across multiple machines.
• Apache Spark: A distributed data-processing engine commonly used for analytics and data engineering.
• Apache Kafka: A distributed event-streaming platform used to publish, store, and process streams of records.
• Data warehouses: Analytical data platforms optimized for reporting and structured queries.

These technologies solve different problems. Kafka is not a direct replacement for a relational database, and Spark is not simply another type of storage system.

Why Big Data Matters to a Cloud Architect

Big data solutions have demanding requirements for compute resources, storage throughput, network bandwidth, security, and operational management.

Consider a retailer collecting transaction records from thousands of stores. Its architecture may need to ingest data continuously, preserve historical records, perform batch analysis, and support near-real-time dashboards.

The system must be designed around data volume, processing latency, reliability, and resource costs.

These are architecture decisions, not merely software installation tasks.

7. Huawei Cloud Stack Planning and Solution Design

Huawei Cloud Stack planning and design is a major part of the H13-528 syllabus. It brings together infrastructure knowledge, networking, cloud services, application requirements, and operational objectives.

Many students find architecture questions challenging because the correct decision depends on multiple constraints rather than a single technical fact.

Requirements Analysis

A good architecture begins with clear requirements.

Before selecting a platform design, architects should identify:

• Expected application workloads and resource consumption
• Performance and latency requirements
• Availability, RTO, and RPO targets
• Network segmentation and connectivity requirements
• Security, data residency, and compliance constraints
• Future expansion and capacity planning assumptions
• Operational ownership and maintenance requirements
• Budgetary and lifecycle considerations

Compute and Storage Resource Planning

Cloud capacity planning should use realistic workload measurements and growth forecasts rather than simple server counts.

For compute resources, architects should consider CPU utilization, memory allocation, performance headroom, redundancy, and resource contention.

For storage, important factors include usable capacity, data protection overhead, performance characteristics, access patterns, and future growth.

An architecture that provides sufficient raw capacity may still fail to meet application performance requirements if its storage or network design introduces bottlenecks.

Network and Deployment Planning

Network planning includes physical connectivity, logical segmentation, IP addressing, routing, security policies, and bandwidth requirements.

Architects also need to evaluate dependencies between infrastructure services. Reliable DNS, time synchronization, identity services, monitoring, and management connectivity are often essential to stable cloud operations.

Deployment planning must account for fault domains and maintenance procedures. Redundant components are valuable only when the surrounding architecture allows them to operate effectively during failures or planned maintenance.

Resource Partitioning and Governance

Resource partitioning defines how infrastructure capacity and administrative responsibilities are divided across tenants, projects, business units, or applications.

Good partitioning policies improve accountability, reduce resource contention, and make access controls easier to manage.

The architectural goal is not maximum isolation at any cost. Instead, it is to establish appropriate boundaries while preserving operational efficiency and scalability.

Practical Architecture Scenario: Designing a Private Cloud for an Enterprise

Imagine a manufacturing company planning to modernize its internal IT infrastructure.

The organization runs an ERP platform, a relational database, internal business applications, and several newer microservices. It also expects to introduce a production analytics platform.

The company wants centralized cloud management while retaining control over infrastructure and sensitive business information.

Step 1: Identify Workload Requirements

The ERP application may require stable performance and predictable maintenance windows. Its database requires carefully designed backup and recovery procedures.

The microservices platform may benefit from Kubernetes-based deployment and automated scaling. The analytics workload may require substantial storage capacity and distributed processing resources.

Step 2: Establish Resource Boundaries

The architecture could define separate logical environments for production applications, development workloads, management services, and analytics.

Appropriate isolation would be implemented through platform resource organization, identity controls, and network security policies.

Step 3: Design the Network

The network would need to support application connectivity without unnecessarily exposing internal services.

Virtual networking technologies could help separate workloads while allowing carefully controlled communication between application tiers.

Bandwidth, routing, firewall placement, and physical redundancy would need to be validated against expected traffic patterns.

Step 4: Select Application Deployment Models

Not every application should automatically be containerized.

Existing ERP and database systems might remain on virtual machines if this provides better compatibility and manageable operational risk.

New microservices could run on a Kubernetes platform, provided the organization has the skills and processes required to operate it securely.

Step 5: Plan Operations and Recovery

The solution should include monitoring, logging, backup procedures, access management, capacity reporting, and documented recovery testing.

It should also define who is responsible for infrastructure management, application operations, and security incident response.

Architectural lesson: The best cloud solution is not necessarily the one using the most modern technology. It is the one that meets technical and business requirements with acceptable risk, complexity, and cost.

Is the HCIP-Cloud Computing Solution Architect Certification Worth It?

The potential value of this certification depends on your current experience, career goals, and the technology platforms used by your target employers.

For professionals working with Huawei enterprise cloud environments, the H13-528 learning path offers a focused opportunity to understand infrastructure architecture and solution design concepts.

Benefits for Networking Professionals

Network engineers already understand important concepts such as IP addressing, routing, switching, VLANs, and network security.

Studying cloud architecture extends that knowledge into virtual networking, tenant isolation, infrastructure automation, and the interaction between applications and cloud resources.

Benefits for System Administrators

System administrators often have practical experience with operating systems, virtualization, storage, and application hosting.

The certification syllabus encourages them to connect those operational skills with broader design decisions, including resource allocation, availability, and application modernization.

Potential Career Directions

The knowledge covered by H13-528 can be relevant to roles such as:

• Cloud Computing Solution Engineer
• Cloud Infrastructure Engineer
• Cloud Solutions Pre-Sales Engineer
• Private Cloud Implementation Engineer
• Cloud Platform Engineer
• Junior Cloud Solution Architect

However, certification alone does not qualify someone for a senior architecture position. Employers may also expect production experience, troubleshooting ability, documentation skills, customer communication, and familiarity with the technologies deployed in their environments.

The greatest value comes from combining certification study with hands-on projects and practical design experience.

H13-528 vs. H13-527: What Is the Difference?

Students researching Huawei cloud computing certifications may encounter both H13-527 and H13-528.

Although these examinations belong to closely related subject areas, their published learning objectives emphasize different professional skills.

These differences are based on published exam outlines, not a guarantee that the subjects are mutually exclusive.

Students should verify the current certification requirements and determine whether additional examinations are required for their intended certification path.

How to Prepare for the H13-528 Exam

A practical preparation strategy should combine structured reading, technical experimentation, architectural reasoning, and knowledge assessment.

Studying only definitions can produce a misleading sense of confidence. You may know what a Kubernetes Pod is while still struggling to design a reliable application deployment.

Candidates looking for a more organized learning path can explore Huawei H13-528 certification study materials alongside official documentation and hands-on labs.

Phase 1: Strengthen the Fundamentals

Begin with virtualization, Linux, IP networking, and cloud service models.

Make sure you can explain the differences between physical and virtual infrastructure, the purpose of IaaS, and how shared infrastructure resources can be safely allocated to multiple users.

Phase 2: Study OpenStack and Huawei Cloud Stack

Learn the responsibilities of core OpenStack components and understand the architectural role of Huawei Cloud Stack.

Focus on interactions between services, resource pools, management components, and tenant environments.

Phase 3: Practice Kubernetes and Cloud-Native Technologies

If possible, build a small learning environment using Minikube, kind, or another suitable Kubernetes distribution.

Practice creating Deployments, exposing Services, inspecting Pods, modifying replica counts, and reviewing application logs.

These exercises will not reproduce every Huawei Cloud Stack feature, but they establish important Kubernetes fundamentals.

Phase 4: Learn Database and Big Data Architecture

Compare relational and non-relational data models, explore backup and replication concepts, and understand the roles of distributed data-processing technologies.

Use simple application scenarios to identify appropriate technology choices.

Phase 5: Practice Solution Design

Develop a small architectural proposal for an imaginary organization.

Include resource planning, logical networking, application deployment models, data protection, security boundaries, and operational requirements.

Explain why you selected each component. This exercise is particularly effective because it forces you to connect multiple exam domains.

Phase 6: Review and Assess Your Knowledge

Use official training resources, documentation, self-created flashcards, and legitimate practice assessments to identify weak areas.

For every incorrect answer, investigate the underlying principle rather than memorizing the correct option.

Favor materials that explain the reasoning behind technical decisions and avoid relying on unverified claims about real examination questions.

Suggested Six-Week H13-528 Study Plan

The following schedule is an example for learners with basic IT knowledge. Adjust the pace according to your familiarity with networking, virtualization, and Linux.

A six-week plan is not a guarantee of examination readiness. Candidates without cloud infrastructure experience may need additional time, especially for Kubernetes and solution architecture topics.

When reviewing your progress, use the H13-528 Cloud Computing Solution Architect preparation page as an additional study resource to help identify topics for further review.

Common Mistakes to Avoid During H13-528 Preparation

Memorizing Services Without Understanding Their Relationships

Knowing that Nova manages compute instances and Neutron manages networking is useful, but it is more important to understand how these services contribute to a working cloud environment.

Ignoring Network Architecture

Even though the reported networking domain has a smaller weight than the cloud-native domain, networking affects nearly every cloud design.

Weak knowledge of addressing, routing, isolation, and traffic flows can make architecture scenarios difficult to interpret.

Confusing Public Cloud and Private Cloud Services

Huawei Cloud and Huawei Cloud Stack may expose related concepts and service names, but features, supported versions, deployment models, and operational responsibilities can differ.

Always identify which platform and release a technical document describes.

Skipping Hands-On Kubernetes Practice

Kubernetes terminology becomes much easier to understand after deploying real workloads.

Even a small local cluster can help demonstrate scheduling, service discovery, replica management, and application lifecycle behavior.

Using Outdated Exam Materials

Cloud platforms and certification programs evolve. Before relying on a training guide, confirm its examination version and publication context.

Official documentation should remain the primary reference for product-specific behavior.

Frequently Asked Questions About H13-528

What is the H13-528 exam?

H13-528 is the published examination code associated with Huawei HCIP-Cloud Computing Solution Architect. Its V1.0 syllabus focuses on Huawei Cloud Stack, OpenStack, cloud networking, Kubernetes, database technologies, big data, and cloud solution design.

Is H13-528 suitable for beginners?

Beginners can study the material, but the technical content is easier to understand with foundational knowledge of networking, Linux, virtualization, and cloud computing. Students without this background should build those skills before attempting advanced architecture scenarios.

Is Kubernetes important for H13-528?

Yes. Cloud-native and container technologies account for 25% of the published V1.0 syllabus. Kubernetes architecture, workloads, orchestration, and Huawei’s container platform capabilities are important preparation areas.

Does H13-528 focus on Huawei Cloud Stack?

Yes. Huawei Cloud Stack architecture, networking, resource planning, and solution design are central themes in the published examination objectives.

How difficult is the HCIP-Cloud Computing Solution Architect exam?

The difficulty depends on previous experience. Candidates familiar with private cloud infrastructure may find the architecture topics approachable, while students new to Kubernetes, OpenStack, and distributed systems may face a steeper learning curve.

How long should I study for H13-528?

A learner with basic infrastructure experience might begin with a structured six-week plan. Someone who is new to cloud computing may require significantly more preparation time. Hands-on proficiency and the ability to reason through architecture scenarios are better measures of readiness than a fixed number of study days.

Can H13-528 help me become a cloud solution architect?

The certification syllabus can help develop architecture-related knowledge, but professional solution architects also need practical project experience, requirements analysis skills, troubleshooting ability, and an understanding of security, resilience, and cost management.

Where can I find H13-528 study resources?

Start with Huawei’s official certification portal for current exam information and use official product documentation for technical reference. For additional learning and revision, visit the HCIP-Cloud Computing Solution Architect H13-528 study resources page.

Final Thoughts: Building Skills Beyond the Certification

The HCIP-Cloud Computing Solution Architect H13-528 learning path introduces an important shift in how infrastructure professionals approach enterprise IT.

Instead of concentrating entirely on individual products or administration procedures, it encourages learners to understand how infrastructure and application technologies support a complete cloud solution.

OpenStack provides valuable insights into infrastructure services. Huawei Cloud Stack introduces private cloud platform design and resource management. Kubernetes extends the discussion into cloud-native application delivery. Database and big data technologies demonstrate how infrastructure decisions affect real business workloads.

For students and junior engineers, the strongest preparation strategy is to connect these technologies through practical scenarios.

Learn the concepts, test them in a lab where possible, review authoritative documentation, and practice explaining your design choices.

Passing a certification examination can be a useful milestone. Developing the ability to design a reliable, secure, and maintainable cloud solution is the longer-term professional achievement.

If you are preparing for the Huawei certification, you can also explore the H13-528 HCIP-Cloud Computing Solution Architect course page for additional exam preparation resources.

Official Documentation and Recommended References

The following resources provide authoritative technical information for studying the technologies associated with H13-528. Product documentation may describe newer releases than those used in a particular certification syllabus.

• Huawei Enterprise – Certification Portal:
  https://e.huawei.com/en/talent/
  Huawei’s enterprise talent and certification resources. Use the certification catalog to confirm current examination availability and requirements.
• Huawei Cloud Stack – Official Information Center:
  https://doc.hcs.huawei.com/hcs/
  Product documentation, deployment information, cloud service guidance, and technical best practices for Huawei Cloud Stack.
• Huawei Cloud – Cloud Container Engine Documentation:
  Huawei Cloud CCE Product Overview
  An introduction to Huawei’s Kubernetes-based container platform and its architecture.
• Huawei Cloud Stack – CCE Technical Documentation:
  Huawei Cloud Stack CCE Basic Concepts
  Technical explanations of container clusters, nodes, workloads, and related platform concepts.
• OpenStack – Official Documentation:
  https://docs.openstack.org/
  OpenStack architecture, service documentation, administration guidance, and implementation references.
• Kubernetes – Official Documentation:
  https://kubernetes.io/docs/
  Kubernetes concepts, workloads, networking, scheduling, configuration, and cluster management.
• Cloud Native Computing Foundation:
  https://www.cncf.io/
  Cloud-native ecosystem projects, educational resources, and community technical information.
• Apache Hadoop – Official Documentation:
  https://hadoop.apache.org/docs/
  Reference documentation for distributed data storage and processing technologies.

Editorial note: This article is an independent educational guide and is not an official Huawei examination publication. Huawei product and certification names belong to their respective owners. Examination objectives and administrative policies should be confirmed with Huawei.