Huawei Cloud Fundamentals and Cloud Service Overview
What this domain tests
This domain checks whether you can reason about Huawei Cloud's global architecture and commercial model before touching a single service. Expect questions on regions and availability zones (AZs), accounts, projects, resource scope, and the shared responsibility model.
Core rules
- A region is a geographic area; an AZ is an isolated data center with independent power and network inside a region. ECS and EVS are region- and AZ-scoped, so an EVS disk can attach only to an ECS in the same AZ.
- A project groups resources for isolation and billing within a region, and IAM permissions are commonly granted per project. A project is not a region.
- Common billing modes are yearly/monthly subscription and pay-per-use. Subscription suits steady long-running workloads; pay-per-use suits spiky or short-lived tests.
- Under shared responsibility, Huawei Cloud secures the physical infrastructure and virtualization layer; the customer secures guest OS patches, accounts, security group rules, and data.
Worked example
A team runs a latency-sensitive order service for users in Shanghai and needs disaster recovery in another city. Choose CN East-Shanghai1 with two AZs for the primary deployment, then a second region such as CN North-Beijing4 for DR. Place the ECS fleet and its EVS disks in the same AZ as the primary database replica, and replicate backups across regions. Reasoning: AZ isolation protects against a single data-center failure, while a second region protects against a city-scale event. Keeping the active region local minimizes latency for Shanghai users.
Traps
Assuming every service is global; treating an AZ as a separate region; placing EVS in one AZ and ECS in another; and forgetting that subscription resources still require capacity planning.