OceanProtect ' s architecture explicitly includes a “Ransomware protection solution (encryption/decryption, WORM, ransomware detection, and secure transmission).” The course also states that ransomware protection protects copies and provides anti-tampering through the read-only attribute of WORM.

Therefore, all four mechanisms contribute to the required defense.

WORM provides the immutable-copy foundation. Huawei explains that protected WORM files cannot be rewritten, modified, deleted, or renamed during their protection period. Abnormal behavior monitoring corresponds to ransomware-detection capabilities used to identify suspicious activity against protected copies. Multi-layer antivirus association provides an additional malware-detection barrier around file-oriented protection workflows.

Finally, access control limits who can administer, modify, or operate protection resources. OceanProtect implements role-based access control with predefined and customizable roles, reducing the attack surface for compromised or unauthorized accounts.

Together these controls provide detection, prevention, privilege restriction, and immutable recovery copies.

Study Guide Topics: Data Protection Solution → OceanProtect Backup Storage → High Security Design → Ransomware Protection → WORM → Role-Based Access Control.

The OceanProtect software architecture states: “Infrastructure: Includes GaussDB, Elasticsearch, Kafka, ZooKeeper, and other common components.”

Accordingly, Elasticsearch, Kafka, and GaussDB are valid infrastructure components and the correct selections are A, C, and D.

GaussDB provides relational database services required by the management and data-protection software stack. Elasticsearch supports indexing and search-oriented functions, which are important for metadata processing, global search, and operational data retrieval. Kafka provides distributed messaging capabilities that enable communication and event/data exchange between components in the distributed OceanProtect architecture.

Ceph is not listed as one of the OceanProtect infrastructure components in this architecture. Instead, the storage layer is Huawei ' s integrated storage platform, providing file-system and protocol-access capabilities beneath the data-protection services.

The same architecture separates the platform into the management layer, data-protection layer, storage layer, hardware layer, and common infrastructure. ProtectManager schedules backup, recovery, archive, and replication jobs, while DataMover Engine processes protection data flows.

Study Guide Topics: Data Protection Solution → OceanProtect Backup Storage → Software Architecture → Infrastructure Components → ProtectManager/DataMover Engine.

The mandatory network planes are the backup network and the management network.

Huawei defines the management network plane as the network used for web-console login, service configuration, and alarm reporting. Without it, administrators cannot perform the fundamental control and administration functions required by the appliance. Huawei defines the backup network plane as the network used for backup data and in-band signaling transmission, making it essential for the appliance ' s core data-protection function.

The replication network, by contrast, is needed when backup copies must be replicated to another data-protection appliance. If remote replication is not part of the deployment, this plane is not mandatory. Similarly, an archive network is optional because the backup network can be reused for archiving under supported configurations.

An internal communication network becomes relevant to multi-node architectures where separate nodes must communicate internally. The question explicitly specifies a single-node system, so this separate internal plane is not mandatory.

Therefore, the baseline single-node OceanProtect networking requirement is C and D.

Study Guide Topics: Data Protection Solution → OceanProtect Appliance → Network Planning → Management Network → Backup Network → Replication Network.

Huawei defines To be recovered as the state entered after the fault causing an interruption is rectified when manual recovery is required. The state reminds the administrator that manual synchronization is needed to restore the pair. Therefore, D is correct.

A manually split pair enters Split, meaning replication is suspended; the replication relationship itself is not deleted. An ordinary link or LUN failure causes Interrupted, whereas Invalid is used when the properties of the primary or secondary resource change and the configurations become inconsistent. This makes A and C incorrect.

For file systems, Huawei states that HyperReplication(A) replicates at the file-system object layer and synchronizes all file-system contents and changes to the secondary file system. The WORM section separately documents that file expiration is governed by the WORM regulatory clock.

The retrieved course text documents these two mechanisms separately rather than giving one sentence explicitly naming both WORM fields during replication.

Study Guide Topics: Data Protection Solution → HyperReplication(A) for File Systems → Pair Status → WORM → Recovery and Synchronization.

All four listed capabilities are included in the DME data-management/O & M framework.

Huawei describes DME Storage as an intelligent storage management platform covering the complete storage lifecycle, including planning, deployment, O & M, and optimization. Its architecture includes intelligent diagnosis, intelligent optimization, resource optimization, planning simulation, operation visibility, insight analysis, and multidimensional analysis.

Planning enables administrators to model and organize resources before deployment. Analysis provides performance, capacity, topology, alarm, and workload insight. Optimization uses those analytics to recommend or execute improvements such as capacity balancing, migration, SLA adjustment, and QoS changes. Search is important for unstructured-data environments because files, objects, and other unstructured content must be located and analyzed according to metadata.

Huawei OceanStor Pacific also provides SmartIndexing for unstructured file, object, and HDFS storage. It can return search results from extremely large metadata sets within seconds and provides unified multi-protocol metadata indexing.

Consequently, DME ' s unstructured-data management workflow spans the complete chain of search, analysis, planning, and optimization.

Study Guide Topics: Data Storage Management and O & M → DME → Unstructured Data Management → Search → Analysis → Planning → Optimization.

The only true statement is C, so the false statements are A, B, and D.

Huawei states: “If communication between the storage systems is down, the preferred site continues to provide services while the other site stops providing services.”

The HyperMetro pair therefore transitions to To be synchronized because the two storage systems can no longer maintain synchronous dual-write consistency across the failed inter-site link.

Option A is false because automatic fallback to static priority mode is associated with quorum-server failure, not merely failure of the HyperMetro communication link while the quorum server remains available. Option D is false because permitting both sites to continue independently would create a split-brain risk. Quorum arbitration exists specifically to prevent that condition.

Option B is also false because arbitration does not simply make both sides unavailable. One site wins arbitration and continues providing services, while the losing site stops host access.

This behavior preserves data consistency until the inter-site link is repaired and synchronization resumes.

Study Guide Topics: Data Protection Solution → HyperMetro → Single Quorum Server → Arbitration Mechanism → Link Failure → To-be-Synchronized State.

Huawei states: “LUN information exchange refers to the mapping between LUNs and data volumes. That is, when the LUN IDs of the source LUN and target LUN remain unchanged, the data volume IDs of the source data volume and target data volume are exchanged.”

Therefore, A, B, C, and D are all correct.

Before the exchange, the source LUN ID points to its original source data volume, which validates C. During the information exchange, the logical LUN identifiers remain stable but their associated physical data-volume IDs are exchanged, validating D. Consequently, after the exchange, the source LUN ID—the identity already known by the host—now references the target data volume, validating A.

During synchronization before the swap, SmartMigration uses dual-write and DCL technologies to keep the target LUN consistent while host services continue. Once synchronization is complete, space is exchanged and the migration relationship is interrupted/split. At that stage, normal host writes continue against the migrated target data rather than maintaining the previous dual-write synchronization relationship, which validates B.

Study Guide Topics: Data Migration Solution → SmartMigration → Data Synchronization → LUN Information Exchange → Data Volume ID Exchange → Pair Split.