HCIE-Cloud Service study plan

Map every major Huawei Cloud service family (compute, storage, network, database, security, management) to the exam domain it belongs to, building a personal one-page taxonomy

Explain the difference between ECS, BMS, CCE, and serverless offerings and state when each is the correct choice

Configure a VPC with subnets, security groups, and an ELB from scratch in a sandbox account and record each console step

List the IAM concepts (accounts, users, groups, policies, agencies) and write down how an agency enables cross-service access

Compare OBS storage classes and lifecycle rules, and justify a tiering policy for a stated workload

Describe EVS disk types, snapshots, and backup behavior well enough to choose a disk for a database versus a log volume

Diagnose three seeded failure scenarios (security group misconfiguration, ELB backend unhealthy, OBS permission denied) using logs and console metrics

Explain how Cloud Eye metrics and alarms are structured and set one alarm on a lab resource

Translate a written business requirement into a layered architecture (network, compute, data, security) with explicit assumptions

Justify high-availability design choices across availability zones, including ELB, database, and storage redundancy

Select a database (RDS, GaussDB, DDS, or data warehouse) for three contrasting workloads and defend each choice

Produce a cost estimate outline and identify which design decisions drive cost most

Design a migration strategy for a given on-premises estate, choosing between rehost, replatform, and rebuild per workload

Sequence the migration steps for a database workload, covering assessment, replication, cutover, and rollback

Define the network connectivity options for hybrid migration and state the trade-offs of each

Write cutover and rollback runbooks with explicit go/no-go criteria

Automate provisioning of a repeatable environment using templates or IaC tooling rather than console clicks

Configure monitoring, logging, and alerting for the deployed environment and verify alerts fire

Implement a backup and restore routine and actually restore one resource to prove recoverability

Document an operational runbook covering patching, scaling, and incident escalation

Apply a structured troubleshooting method (symptom, scope, hypothesis, test, confirm) to network connectivity failures

Trace and resolve a performance bottleneck using metrics, distinguishing resource saturation from configuration limits

Diagnose an identity and permission failure by reading policy evaluation and access logs

Optimize a deployed workload for cost and performance and quantify the before/after change

Re-derive the weak areas from weeks 1-6 and rebuild notes for the three weakest topics

Redesign the week 3 architecture to fix at least two flaws you can now identify

Practice explaining architecture and troubleshooting decisions aloud in exam-style structured answers

Time-box a set of self-written scenario questions and review every wrong answer to root cause

Consolidate all deliverables into one indexed reference you can review quickly

Rehearse end-to-end scenario answers covering design, deployment, and troubleshooting in a single narrative

Verify recall of key facts (service limits, HA patterns, migration sequencing) without notes

Finalize an exam-day time-allocation and question-triage strategy