Which of the following protocols does OceanStor Pacific unified metadata indexing function not support?

Question

Options

• AHDFS
• BDocuments
• CBlock
• DObject

• A
  12% (4)
• B
  6% (2)
• C
  79% (27)
• D
  3% (1)

Explanation

Block storage (option C) is correct because block-level data is stored as raw chunks managed entirely by the host operating system or application - the storage system itself has no visibility into file-system metadata, making unified indexing impossible at the storage layer.

Why the distractors are wrong:

• HDFS (A) is supported because Hadoop's metadata (NameNode structure, file paths, block locations) is structured and exposed to the storage layer for indexing.
• Documents (B) is supported because document/file data (NFS/CIFS) carries rich metadata (name, path, timestamps, attributes) that OceanStor Pacific can index and catalog.
• Object (D) is supported because object storage natively embeds metadata (key-value pairs, tags, headers) with every object, making it ideal for unified indexing.

Memory tip: Think of it as "who owns the metadata." With HDFS, Documents, and Object, the storage system sees and manages the metadata. With Block, the host owns everything - the storage just sees opaque sectors, so there's nothing for Pacific to index.

No community discussion yet for this question.