Mapr (HP) HBase Developer Certification Questions and Answers (Dumps and Practice Questions)

Question : In MapR-DB, what is the maximumn size of a Row.


1. 1 GB

2. 2 GB

3. Equal to minimum size of RAM in entire cluster

4. Equal to maximum size of RAM in entire cluster

Correct Answer : 2
Explanation: In MapR-DB, the maximum supported size of a row is 2 GB. However, the recommended practice is to keep the size under 2 MB. In general, MapR-DB performs
better with many small rows, rather than with fewer very large rows.





Question : In MapR-DB, Rows span one or more column families and columns.


1. True
2. False

Correct Answer : 1
Explanation: Row: Rows span one or more column families and columns.
In MapR-DB, the maximum supported size of a row is 2 GB. However, the recommended practice is to keep the size under 2 MB. In general, MapR-DB performs better with many small rows,
rather than with fewer very large rows.






Question :

In HBase data is not updated ?

1. True
2. False

Correct Answer : 1

HBase is Multidimensional
All data is versioned using a timestamp (or configurable integer)
Data is not updated, instead it is added with a new version number

Related Questions

---

Question : In which case Hbase should not be used ?


1. When you only append data to your dataset and read the whole data
2. When you need random read
3. When you need random write
4. When access pattern is well known




Question :

One technical architech designing a solution for storing huge data volume which is everyday generated by stock markets and its purpose
is only storing these data and reading it once for daily analysis and he comes to conclusion that, he will use HBase. So he took a right decision



1. Yes
2. No


Question :

Please select the correct answer for HBase ?


1. In HBase every row has a Row Key
2. All columns in HBase are belongs to a particular column family
3. A table can have one or more column families
4. Table cells are versioned
5. All of the above





Question :

When you are designing a Column Families, so what makes you think for keeping the data in different column families

1. By Default each enity should be kept in different column family
2. Data that is not frequently accessed together should be kept in different Column Family
3. Data which used different compression methods
4. 1,2 and 3 are correct
5. Only 2 and 3 are correct





Question :

Select the correct option for HBase table

1. Physically stored on a per-column family basis.
2. Empty cells are not stored
3. Each cell has a timestamp
4. Multiple version of a cell can exist
5. All of the above




Question :

When HBase is compared with RDBMS then which statement is true.

1. HBase automatically partitions data in regions
2. HBase does not support explicit joins
3. A lookup by row key implicitly joins data from column families if necessary
4. All of the above
Solution : 15