nerdexam
Huawei

H13-723_V2.0 · Question #37

A large manufacturing company plans to transform its internal logistics data and sales data into big data. The design department has given an analysis of the data storage plan. Which of the…

The correct answer is A. HBase stores massive data and supports dynamic expansion, which can fulfill the storage B. Hbase supports efficient random reading, and can complete real-time analysis and command of C. Logistics data is very sparse, and HBase can efficiently process sparse data. D. HBase can be built on ordinary commercial servers, and the construction cost is relatively low. All four options correctly describe HBase capabilities, making this an "all of the above" question that tests comprehensive knowledge of HBase's architecture and strengths. A is correct because HBase is built on HDFS and designed for petabyte-scale storage, with horizontal…

Distributed Storage Development (HDFS, HBase)

Question

A large manufacturing company plans to transform its internal logistics data and sales data into big data. The design department has given an analysis of the data storage plan. Which of the following descriptions is correct?

Options

  • AHBase stores massive data and supports dynamic expansion, which can fulfill the storage
  • BHbase supports efficient random reading, and can complete real-time analysis and command of
  • CLogistics data is very sparse, and HBase can efficiently process sparse data.
  • DHBase can be built on ordinary commercial servers, and the construction cost is relatively low.

How the community answered

(13 responses)
  • A
    100% (13)

Explanation

All four options correctly describe HBase capabilities, making this an "all of the above" question that tests comprehensive knowledge of HBase's architecture and strengths.

A is correct because HBase is built on HDFS and designed for petabyte-scale storage, with horizontal scaling achieved simply by adding commodity nodes to the cluster - making it ideal for the company's growing logistics and sales data.

B is correct because HBase uses row-key-based indexing that enables O(1) random read access, making it suitable for real-time query workloads such as tracking shipment status or live inventory lookups.

C is correct because HBase's column-family model only stores cells that contain actual values - null or missing fields consume no space - so sparse datasets like logistics records (where many optional fields are empty) are stored very efficiently.

D is correct because HBase was explicitly designed to run on commodity (off-the-shelf) servers rather than expensive enterprise hardware, which significantly lowers infrastructure cost compared to traditional relational databases at scale.

Since all options are valid, there are no distractors to eliminate - the trap is assuming one or more options must be wrong.

Memory tip: Think of HBase with the acronym SRSC - Scale massively, Random access in real time, Sparse data handled natively, Cheap commodity hardware. If you can confirm all four, the answer is always "all of the above."

Topics

#HBase#Distributed Storage#Sparse Data#Real-time Query

Community Discussion

No community discussion yet for this question.

Full H13-723_V2.0 Practice