The statement that RAID 0 supports reconstruction is incorrect. RAID 0, known as striping, improves performance by distributing data across multiple disks but provides no data redundancy. If a single disk in a RAID 0 array fails, all data on the array is lost and cannot be rebuilt or reconstructed. In contrast, RAID levels 1, 3, 5, 6, and 10 all include redundancy mechanisms (mirroring or parity) that allow the array to be reconstructed onto a new disk after a drive failure, ensuring data availability.

B. A hot spare disk is a standby disk that can automatically replace a failed disk, but reconstruction can also be initiated manually after an administrator physically replaces the failed drive.

C. The reconstruction process involves intensive read operations on the surviving disks and write operations on the new disk, which competes for I/O resources and degrades the overall performance of the RAID group.

D. Redundant RAID levels are designed for high availability. During reconstruction, the array operates in a degraded state but remains online and continues to serve I/O requests, thus not interrupting business operations.

1. Huawei

"HCIA-Storage V5.0 Training Material

" Document Version 1.00

2021.

Section 2.2.2 RAID Levels: This section details the characteristics of different RAID levels. For RAID 0

it explicitly states

"RAID 0 does not provide data redundancy. If a member disk is damaged

data on the RAID group is lost." (Page 39).

Section 2.2.4 RAID Hot Spare: This section explains

"A hot spare disk is a spare disk in a storage system. When a member disk in a RAID group fails

the hot spare disk can automatically replace the faulty disk... If no hot spare disk is available

the faulty disk must be replaced manually." (Page 51).

Section 2.2.5 Data Reconstruction: This section notes

"During data reconstruction

the RAID group can still carry services

but its performance deteriorates." (Page 52).

2. Patterson

D. A.

Gibson

G.

& Katz

R. H. (1988). A case for redundant arrays of inexpensive disks (RAID). SIGMOD '88: Proceedings of the 1988 ACM SIGMOD international conference on Management of data

109–116.

Section 3

"The Five Levels of RAIDs": The foundational paper on RAID defines Level 0 as non-redundant striping

stating it has the "worst reliability" as the mean time to failure is the sum of the failure rates of all disks. This inherently means it cannot be reconstructed. (Page 112).

Recovery Time Objective (RTO) is the duration of time within which a business process must be restored after a disaster to avoid unacceptable consequences. In this scenario, the system went down at 16:00 and resumed operation at 23:00. The total downtime, or actual recovery time, is 7 hours (23:00 - 16:00).

Recovery Point Objective (RPO) is the maximum tolerable period of data loss. It measures the time from the last recoverable data point to the point of failure. Here, the failure occurred at 16:00, and the data was restored to its state at 12:00. Therefore, the amount of data lost corresponds to a 4-hour period (16:00 - 12:00).

A. This option incorrectly swaps the calculated values for RTO and RPO. RTO measures time to recover, while RPO measures the period of data loss.

C. This option incorrectly calculates the RTO. The downtime was 7 hours, not 2 hours.

D. This option incorrectly calculates the RPO. The data loss period was 4 hours, not 3 hours.

1. Huawei HCIA-Storage V5.0 Training Material. In the "Backup and Disaster Recovery Technologies" chapter

RTO is defined as the maximum tolerable service interruption time

and RPO is defined as the maximum tolerable data loss. The calculations in this question directly apply these official definitions. (Reference: Huawei Certified ICT Associate - Storage V5.0

Training Material

Chapter 7: Backup and Disaster Recovery Technologies

Section 7.1.2: Basic Concepts of Disaster Recovery).

2. Huawei Cloud Disaster Recovery Solution White Paper. This document defines key disaster recovery (DR) indicators. It specifies RTO as the target time for restoring a service after a disaster and RPO as the target time point to which data needs to be restored

representing the amount of data that can be lost. (Reference: Huawei Cloud Disaster Recovery Solution White Paper

Section 2.1: Key DR Indicators).

3. Academic Publication. In academic literature on business continuity

RTO is consistently defined as the time it takes to recover from a disaster

while RPO is the acceptable data loss measured in time before the disaster. (Reference: Wibowo

W. T.

et al. "A survey on disaster recovery for cloud data centers." International Journal of Communication Systems

vol. 31

no. 17

2018

e3808. Section 2: Background and Related Works. DOI: https://doi.org/10.1002/dac.3808).

The Small Computer System Interface (SCSI) protocol defines a clear communication model between two types of devices: an Initiator and a Target. The Initiator (e.g., a host server) acts as the client, sending commands to request operations like reading or writing data. The Target (e.g., a storage disk array) acts as the server, receiving and executing these commands, then returning the requested data or a status message. This distinct request-response relationship, where one entity initiates a service request and the other fulfills it, is the fundamental principle of the Client/Server architecture.

A. Serverless Architecture: This is a cloud-native application deployment model, unrelated to the low-level communication protocol between a host and a storage device.

B. Peer to Peer Architecture: This model involves nodes with equal roles that can both initiate and respond to requests, which contradicts the fixed Initiator/Target roles in SCSI.

C. Browser/Client Architecture: This is a specific, high-level application of the client/server model, not the general architectural principle that describes the SCSI protocol.

1. Huawei Certified ICT Associate - Storage V5.0 Training Material. In the module covering storage network protocols

the SCSI protocol is described with the Initiator sending commands and the Target executing them. This interaction is presented as a foundational example of a client-server relationship in storage networking. (Specifically

refer to the section on "SCSI Protocol Principles").

2. Patterson

D. A.

& Hennessy

J. L. (2017). Computer Organization and Design: The Hardware/Software Interface (5th ed.). Morgan Kaufmann. Chapter 6

"Storage and Other I/O Topics

" describes the I/O protocol structure where a host (initiator) issues commands to a device controller (target)

which is a direct parallel to the client-server model. This text is standard in university computer science curricula.

3. T10 Technical Committee

"SCSI Architecture Model - 5 (SAM-5)"

ANSI INCITS 515-2016. Section 5.2

"SCSI domains

" and Section 5.3

"SCSI devices

" formally define the roles. An initiator port sends commands via a service delivery subsystem to a target port

which manages a logical unit to execute the command. This formalizes the client (initiator) and server (target) roles.

Both statements are technically incorrect. FCoE (Fibre Channel over Ethernet) and iSCSI are storage protocols that operate over Ethernet networks. The choice of physical cabling—whether copper or long-distance fiber optics—is a function of the underlying Ethernet standard (e.g., 10GBASE-SR, 10GBASE-LR), not the storage protocol itself. Both FCoE and iSCSI can leverage the same physical Ethernet infrastructure.

Furthermore, FCoE does not eliminate the need for Ethernet switches. On the contrary, it requires a specialized, lossless Ethernet network, often called Data Center Bridging (DCB) or Converged Enhanced Ethernet (CEE). This necessitates the use of advanced Ethernet switches that support protocols like Priority-based Flow Control (PFC) to ensure the reliable delivery of storage traffic.

A. Statements 1 and 2 are both true.

This is incorrect as both statements are false for the reasons explained above.

B. Statement 1 is true and statement 2 is false.

This is incorrect because Statement 1 is false; the physical media type and length are determined by the Ethernet standard, not the storage protocol.

C. Statement 1 is false and statement 2 is true.

This is incorrect because Statement 2 is false; FCoE is fundamentally dependent on the presence of capable Ethernet switches.

1. Huawei HCIA-Storage V5.0 Training Material.

Reference: Chapter 2

"Storage Network Technology and Evolution

" Section "FCoE Protocol."

Content: The documentation states

"FCoE encapsulates FC frames into Ethernet frames for transmission on a lossless Ethernet network." This confirms that FCoE runs on an Ethernet network

which is built with Ethernet switches

directly contradicting Statement 2. The same chapter describes iSCSI as a protocol running over TCP/IP

which also uses the Ethernet infrastructure

making the physical media distinction in Statement 1 invalid.

2. Huawei HCIA-Storage V5.0 Training Material.

Reference: Chapter 2

"Storage Network Technology and Evolution

" Section "IP SAN."

Content: This section details how iSCSI operates over standard IP networks

which can be built using various Ethernet physical media

including both copper and fiber optic cables. This demonstrates that the premise of Statement 1

which attempts to differentiate the protocols based on cable type and length

is flawed.

The statement that is incorrect is D. Huawei's RAID 2.0+ technology defines a hard disk domain as a collection of disks of the same type (e.g., all SSDs, all SAS, or all NL-SAS). However, a key feature of RAID 2.0+ is its flexibility in handling heterogeneity within that type. It allows for disks of different capacities and rotational speeds to coexist within the same domain. The technology virtualizes the physical disks by dividing them into fixed-size blocks called Chunks. These Chunks are then used to form Chunk Groups (CKGs), which are the basis for LUNs. This virtualization layer abstracts the physical differences, meaning the size and speed of the hard disks do not have to be consistent.

A. This is the correct definition. A hard disk domain is a logical grouping of physical disks used for resource pooling and management in Huawei storage systems.

B. This is a fundamental principle of storage resource management. A physical disk is an indivisible resource that can only belong to one management domain to ensure data integrity.

C. This is a standard feature. OceanStor V3 systems allow administrators to create multiple disk domains to segregate different disk types (for tiering) or for other management purposes.

1. Huawei OceanStor V3 Series V300R006 Storage System Basic Storage Service Guide for Block

Section 4.2.1 "Disk Domain". The document states

"A disk domain can contain disks of the same type but different capacities and rotational speeds." This directly contradicts option D.

2. Huawei OceanStor RAID 2.0+ Technology White Paper

Section 2.2 "Core Concepts". The paper explains that RAID 2.0+ divides member disks in a disk domain into fixed-size Chunks. It further clarifies

"Disks in a disk domain must be of the same type (such as SAS or NL-SAS) but can be of different capacities." This confirms that capacity and speed do not need to be identical.

3. Huawei OceanStor Dorado V3 Series V300R001 Product Documentation

Section "RAID 2.0+". The documentation describes the architecture: "RAID 2.0+ divides disks in a disk domain into small-granularity data blocks (Chunk

CK) and organizes CKs into Chunk Groups (CKG) based on the RAID policy." This underlying mechanism is what enables the use of disks with varying sizes.

Viewing and handling alarms is the most critical daily maintenance task for a storage administrator. Alarms are the primary mechanism for the storage system to report faults, potential risks, and performance degradation. Daily monitoring and prompt handling of these alarms are essential for maintaining system stability, ensuring data integrity, and preventing service disruptions. This proactive and reactive process allows administrators to address issues before they escalate into major outages, making it a fundamental part of daily operations.

B. Inspection storage equipment: A thorough physical inspection of hardware components like indicators, fans, and cables is typically scheduled on a weekly or monthly basis, not daily.

C. Check the computer room environment: While crucial, monitoring the data center's temperature and humidity is usually the daily responsibility of the facilities team, with storage systems generating alarms if thresholds are breached.

D. Check the internal environment of the rack: This is a subset of a physical hardware inspection and is generally performed weekly, not as a standalone daily task unless an alarm indicates a specific rack-level issue.

1. Huawei Enterprise Support Documentation: The OceanStor 5300 V3 Storage System V300R006 Routine Maintenance Guide

in Chapter 2

"Routine Maintenance"

Table 2-1 "Routine maintenance items and period"

explicitly lists "Checking alarms" as a Daily task. It lists "Checking the running status of hardware" and "Checking the storage system environment" as Weekly tasks. This directly supports that alarm management is the designated daily activity over physical or environmental inspections.

2. Huawei HCIA-Storage Courseware: The official HCIA-Storage curriculum materials consistently emphasize the importance of routine maintenance. In the modules covering storage system operations and maintenance (O&M)

daily tasks are defined to include checking the alarm list on the management interface (e.g.

DeviceManager) as the first and most important step to assess system health. (Reference: HCIA-Storage V5.0 Training Material

Chapter 8: Storage System O&M Management).

The Information and Data Lifecycle describes the progression of data from its creation to its eventual deletion. The process begins with the Generation stage, where data is created or acquired. The second stage is Transmission, where the newly created data is moved from its source to a storage system or another location for processing. Following transmission, the data enters the Usage (processing and storage) and Maintenance (archiving and backup) stages, before finally being destroyed. Therefore, Transmission is the correct second stage in this lifecycle model.

A. Maintenance: This is a later stage in the lifecycle, focused on long-term data preservation, backup, and archiving, occurring after data has been used.

C. Generation: This is the initial, or first, stage of the data lifecycle, where data is created.

D. Usage: This stage follows generation and transmission, where data is actively accessed, processed, and analyzed to derive value.

1. Huawei HCIA-Storage V5.0 Training Material. In the introductory chapters covering storage fundamentals

the data lifecycle is typically outlined. The sequence is consistently presented as: 1. Data Generation

2. Data Transmission

3. Data Storage

4. Data Processing (Usage)

5. Data Archiving (Maintenance)

and 6. Data Destruction. This confirms that Transmission is the second stage. (Reference: HCIA-Storage V5.0 Training Material

Chapter 1: Storage Technology Trends).

2. University Courseware. Computer science and information systems curricula often cover the data lifecycle. For instance

courses on data management confirm the logical sequence where data must be created (generation) and then moved (transmission) before it can be stored and used. (Reference: Based on general principles taught in data management courses

such as those found in MIT OpenCourseWare for Database Systems).

The correct procedure for configuring block storage on a Huawei storage system follows a logical bottom-up workflow. The process begins with accessing the management interface (DeviceManager). Next, physical resources are virtualized by grouping disks into a disk domain, from which a storage pool is created. Then, logical resources (LUNs) are provisioned from the pool and organized into LUN groups. Host objects are created and grouped to represent the application servers. The final step is creating a mapping view, which links the LUN group to the host group, thereby granting the hosts access to the provisioned storage. This sequence ensures that all dependencies are met at each stage of the configuration.

A. A storage pool (2) is created from the resources of a disk domain (3); therefore, the disk domain must be created first.

C. Logging in to DeviceManager (6) is the prerequisite for any configuration task and must be the first step in the sequence.

D. This sequence is entirely out of order. Logging in (6) must be the initial step, and LUNs (4) depend on pre-existing storage pools (2).

1. Huawei OceanStor Dorado 6.1.2 Basic Storage Service Configuration Guide for Block. Section: "Configuration Process". This official guide presents a flowchart that explicitly details the configuration workflow as: Log In to DeviceManager -> Create Disk Domain -> Create Storage Pool -> Create LUN -> Create Host -> Create Mapping View. This directly supports the sequence 6 -> 3 -> 2 -> 4 -> 5 -> 1.

2. Huawei HCIA-Storage V5.0 Training Material (H13-611). Chapter: "Block Storage System Configuration and Management". This courseware

designed for the H13-611 exam

outlines the standard procedure for provisioning block storage

which aligns perfectly with the sequence presented in option B. The material emphasizes creating physical resource pools (disk domain

storage pool) before creating logical units (LUNs) and mapping them to hosts.

The statement is correct. The Huawei OceanStor V3 series of storage systems, spanning from entry-level to high-end models, was designed with a 12 Gb/s SAS backend architecture. This ensures high-speed connectivity between the controller enclosures and the disk expansion enclosures. Official product documentation for all major V3 models, including the 2000, 5000, 6000, and 18000 series, consistently specifies the availability of 12 Gb/s SAS expansion ports as a standard hardware feature.

The statement would be false only if there were an OceanStor V3 model that did not support 12 Gb/s SAS for its backend connectivity. A review of the official hardware specifications across the entire V3 product line confirms that this is not the case; the 12 Gb/s SAS interface is a foundational component of the V3 architecture.

1. Huawei Enterprise Support

"OceanStor 2200 V3 Storage System V300R006 Product Description": This document for the entry-level V3 model explicitly details the hardware specifications.

Reference: Section 2.1 "Hardware Architecture"

Subsection "Backend Port Specifications". It states: "The storage system uses 12 Gbit/s SAS expansion ports to connect to disk enclosures."

2. Huawei Enterprise Support

"OceanStor 5300 V3&5500 V3&5600 V3&5800 V3 Storage System V300R006 Product Description": This document covers the mid-range V3 models.

Reference: Section 2.1 "Hardware Architecture"

Subsection "Backend Port Specifications". It confirms: "The storage system uses 12 Gbit/s SAS expansion ports to connect to disk enclosures."

3. Huawei Enterprise Support

"OceanStor 18500 V3&18800 V3 Storage System V300R006 Product Description": This document describes the high-end enterprise V3 models.

Reference: Section 2.1 "Hardware Architecture"

Subsection "Backend Port Specifications". The specification is consistent: "The storage system uses 12 Gbit/s SAS expansion ports to connect to disk enclosures."

The statement is correct. Serial Attached SCSI (SAS) architecture is fundamentally based on a point-to-point serial connection topology. Unlike its predecessor, parallel SCSI, which utilized a shared bus where multiple devices had to contend for bandwidth, SAS provides a dedicated, full-duplex link between two SAS ports (e.g., between an initiator like a Host Bus Adapter and a target like a disk drive, or between an expander and another device). This design eliminates bus contention, significantly improving performance, scalability, and reliability.

The alternative, "False," is incorrect. If the statement were false, it would imply that SAS uses a shared bus architecture similar to parallel SCSI or another topology like a ring or multi-drop bus. The defining characteristic and primary technological advancement of SAS over parallel SCSI is its adoption of a point-to-point protocol, which is the core concept described in the question.

1. Huawei HCIA-Storage V5.0 Training Material (Course Number H13-611).

Reference: Chapter 2

"Storage Network Technology and Evolution

" Section "SAS Port."

Content: The official training material explicitly states

"SAS uses the serial point-to-point (P2P) connection mode. Each device exclusively occupies a transmission channel

and the bandwidth does not need to be shared. In addition

full-duplex communication is supported." This directly validates the question's assertion that SAS uses a point-to-point design to establish a dedicated link.

2. Patterson

D. A.

& Hennessy

J. L. (2017). Computer Organization and Design RISC-V Edition: The Hardware Software Interface. Morgan Kaufmann.

Reference: Chapter 6

"The Processor: Datapath and Control

" Section 6.8 "Parallelism and Advanced Instruction-Level Parallelism" (in related sections discussing I/O buses).

Content: While not a direct Huawei source

this foundational university-level textbook describes the evolution of storage interfaces. It explains the transition from parallel

shared buses (like parallel SCSI) to serial

point-to-point links (like SAS and SATA) to overcome performance bottlenecks. It clarifies that point-to-point links

such as those in SAS

provide dedicated bandwidth between the controller and the device

which is a core principle of modern I/O architecture.

3. Stallings

W. (2016). Computer Organization and Architecture: Designing for Performance (10th ed.). Pearson.

Reference: Chapter 7

"Input/Output

" Section 7.5 "I/O Channels and Processors."

Content: This standard university textbook on computer architecture details various interconnection structures. It describes Serial Attached SCSI as a key example of a point-to-point interconnect for storage devices

contrasting it with the multi-drop bus configuration of earlier parallel SCSI. The text emphasizes that in a point-to-point link

"a dedicated

unshared path exists between a master and a slave

" which directly supports the statement in the question.