Which of the following statements about Fusioninsight HBase visual modeling is correct? (Multiple choice)

Question

Options

• AVisual modeling helps DBAs to model and design, lowering the threshold for using HBase
• BQualifier HBase column: each column represents a certain attribute of business data
• CRealize the division of labor: DBAs focus on data table modeling, developers focus on user table
• DColumn user table column: each column represents a KeyValue

• A
  79% (42)
• D
  21% (11)

Explanation

Visual modeling in FusionInsight HBase provides a graphical interface that abstracts HBase's complexity, so A is correct - it genuinely lowers the barrier for DBAs who would otherwise need deep HBase expertise to design schemas. B is correct because in the qualifier (HBase column) view, each column maps directly to a specific business attribute (e.g., "age," "city"), which is the purpose of that abstraction layer. C is correct because the tool explicitly enables a division of labor: DBAs own the data table modeling (schema design), while developers interact with the user table (the business-friendly view).

D is wrong because in the user table, each column represents a business attribute - not a raw KeyValue pair. KeyValue is HBase's internal storage format; exposing it at the user table level would defeat the purpose of the abstraction.

Memory tip: Think of two layers - the HBase column (qualifier) layer mirrors business attributes (B), and the user table layer gives developers a relational-like view. Visual modeling bridges them, letting DBAs model without writing HBase APIs (A, C). If an option mixes up "user table columns = KeyValue," it's confusing the internal storage model with the abstraction layer - that's D's mistake.

No community discussion yet for this question.