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

Question : MapR provides volumes as a way to organize data and manage cluster performance, Containers are stored in volumes in MapR-FS. Volumes are used to enforce

A. disk usage limits
B. set replication levels
C. define snapshots and mirrors
D. establish ownership and accountability

1. A,B,C
2. B,C,D
3. Access Mostly Uused Products by 50000+ Subscribers
4. A,B,C,D

Correct Answer : Get Lastest Questions and Answer :
Explanation: MapR provides volumes as a way to organize data and manage cluster performance. A volume is a logical unit that allows you to apply policies to a set
of files, directories, and tables. Volumes are used to enforce disk usage limits, set replication levels, define snapshots and mirrors, and establish ownership and
accountability.





Question : In MapR-DB, You can also isolate work environments for different database users or applications and place MapR-DB tables on specific hardware for better
performance or load isolation


1. True
2. False

Correct Answer : Get Lastest Questions and Answer :
Explanation: There are several advantages to storing table containers in volumes:
Multi-tenancy
You can restrict a volume to a subset of a cluster's nodes. By doing this, you can isolate sensitive data or applications, and even use heterogeneous hardware in the
cluster for specific workloads.
For example, you can use data placement to keep personally identifiable information on nodes that have encrypted drives, or to keep MapR-DB tables on nodes that have SSDs.
You can also isolate work environments for different database users or applications and place MapR-DB tables on specific hardware for better performance or load isolation

Isolation of work environments for different database users or applications lets you set policies, quotas, and access privileges at for specific users and volumes.
You can run multiple jobs with different requirements without conflict.







Question :

While schema design which of the following is valid point to keeping StoreFile indices small..




1. Keep ColumnFamily names as small as possible
2. Avoid long verbose attribute names
3. Access Mostly Uused Products by 50000+ Subscribers
4. All 1,2 and 3 are correct
5. Only 1 and 3 are correct



Correct Answer : Get Lastest Questions and Answer :

While Schema Design Large StoreFile indices
- Every cell always includes row, column name and timestamp
- Indices are kept in HBase StoreFiles to facilitate random access
- Large cell value coordinates increase the size of indices
- May occupy large chunks of RAM
- Compression also increases the size of indices
Increase the block size
- Store file index will happened at a larger interval
Keep names small
- Keep ColumnFamily names as small as possible
- Avoid long verbose attribute names
- Keep RowKey length as short as is reasonable

Related Questions

---

Question : Only Column Families must be created at schema definition time

1. True
2. False



Question : Which of the following is the correct syntex for getting the

data from HBase table t1 and rowkey r1


1. get 't1', 'r1'
2. get 't1', 'r1', {COLUMN => 'fam1:c1'}
3. get 't1', 'r1', {COLUMN => 'fam1:c1', VERSIONS=> 2}
4. All of the above



Question : Which statement is wrong about HBase

1. Tables can have thousands of columns
2. It is not mendatory to have dat data in all the columns
3. It does not support transaction
4. All of the above
5. None of the above




Question : In HBase to lookup of a row by a single key?

1. True
2. False




Question : Hbase supports the transaction for single row ?

1. True
2. False




Question : Which are the supported method to access the data from HBase


1. get
2. put
3. scan
4. 1,2 and 3 are correct
5. It has to be accessed by Query only