H13-624_V5-5 practice question 10 of 25

A financial customer has purchased several Huawei OceanStor Pacific 9550 storage systems. When configuring basic object services on the storage systems, an engineer discovers that the object service cannot be enabled for storage nodes. Which of the following is not a possible cause?

Full set: 106 questions
Answer options
A: The engineer has manually adjusted the time of the cluster nodes. As a result, the conflict handling is different.
B: NTP synchronization is not configured for the cluster, and different NTP time sources are used.
C: Namespaces with the same name have been created under the same account. Correct answer
D: The Network Time Protocol (NTP) clock in the storage cluster is inconsistent with the clock of the client that accesses object services.
Correct Answer:
C. Namespaces with the same name have been created under the same account.
Explanation

Object-service activation checks only cluster-wide prerequisites (time consistency, quorum, role distribution). Duplicate namespace names are validated later, so option C cannot prevent enabling the service.

Why Incorrect

A. Manual clock changes create time drift among nodes, causing the enablement script to abort.
B. Different NTP sources leave nodes unsynchronized, blocking object-service startup.
D. A cluster-client time gap ≥5 s triggers the “Clock Skew” alarm, which prohibits object-service activation.

References

1. Huawei. “OceanStor Pacific 8.3.0 Object Service Feature Guide”, 4.1 “Prerequisites for Enabling Object Service”, p. 62-63.

2. Huawei. “OceanStor Pacific Alarm Reference”, Alarm 0xF00CF03 “Clock Skew Between Nodes”, p. 98.

3. Huawei. “OceanStor Pacific O&M Guide”, 7.2 “Service Enablement Checks”, p. 145 (note about namespace uniqueness being checked only after service starts).

Scroll to Top