Question : To move a table from row based into a BLU columnar format you need to take it offline and do a one time convert into a BLU table. 1. True 2. False
Correct Answer : 2 Explanation: DB2 9.7 introduced the ADMIN_MOVE_TABLE procedure, which is an online utility for moving a table while the data remains online and available for access. This procedure is also known as online_table_move among SAP customers. The ADMIN_MOVE_TABLE procedure can fulfill various business needs. For example, you can use it to move a table to a larger tablespace, perform online table compression, perform online reorganization for a multidimensional clustering (MDC) table, or perform an online migration to an MDC table. Download and try IBM DB2 with BLU Acceleration for Linux, UNIX, and Windows. DB2 10.5 introduced BLU Acceleration. This new support of column-organized tables is ideal for data warehouse and analytic workloads. To fully take advantage of the power of DB2 10.5 with BLU Acceleration, the ADMIN_MOVE_TABLE stored procedure was enhanced to move data from a row-organized table into a column-organized table online. The new db2convert command was also provided. The db2convert command internally calls the ADMIN_MOVE_TABLE procedure but has a simple interface and is easier to use.
Question : Using shadow tables, you can get the performance benefits of BLU Acceleration for analytic queries in an online transaction processing (OLTP) environment.
1. True 2. False
Correct Answer : 1 Explanation: A shadow table is a column-organized copy of a row-organized table that includes all columns or a subset of columns. Shadow tables are implemented as materialized query tables (MQTs) that are maintained by replication. Using shadow tables, you can get the performance benefits of BLU Acceleration for analytic queries in an online transaction processing (OLTP) environment. Analytical queries against row-organized tables are automatically routed to shadow tables if the replication latency falls within a user-defined limit. BLU Acceleration enhances the performance of complex queries through a column-organized architecture. By combining this enhanced performance for complex queries with the efficiency of row-organized tables for OLTP queries, you can use shadow tables to capitalize on the best of both worlds.
Question : Typically, an ApplicationMaster will need to harness the processing power of multiple servers to complete a job. In which of the following order this can be accomplished.
1. ApplicationMaster issues resource requests to the ResourceManager 2. ResourceManager generates a lease for the resource, which is acquired by a subsequent ApplicationMaster heartbeat 3. The ResourceManager will attempt to satisfy the resource requests coming from each application according to availability and scheduling policies. 4. A token-based security mechanism guarantees its authenticity when the ApplicationMaster presents the container lease to the NodeManager
1. 1,2,3,4 2. 1,3,4,2 3. 1,3,2,4 4. 1,4,3,2
Correct Answer : 3
Explanation: YARN makes few assumptions about the ApplicationMaster, although in practice it expects most jobs will use a higher level programming framework. By delegating all these functions to ApplicationMasters, YARN's architecture gains a great deal of scalability, programming model flexibility, and improved user agility. For example, upgrading and testing a new MapReduce framework can be done independently of other running MapReduce frameworks. Typically, an ApplicationMaster will need to harness the processing power of multiple servers to complete a job. To achieve this, the ApplicationMaster issues resource requests to the ResourceManager. The form of these requests includes specification of locality preferences (e.g., to accommodate HDFS use) and properties of the containers. The ResourceManager will attempt to satisfy the resource requests coming from each application according to availability and scheduling policies. When a resource is scheduled on behalf of an ApplicationMaster, the ResourceManager generates a lease for the resource, which is acquired by a subsequent ApplicationMaster heartbeat. A token based security mechanism guarantees its authenticity when the ApplicationMaster presents the container lease to the NodeManager. In MapReduce, the code running in the container can be a map or a reduce task. Commonly, running containers will communicate with the ApplicationMaster through an application-specific protocol to report status and health information and to receive framework-specific commands. In this way, YARN provides a basic infrastructure for monitoring and life-cycle management of containers, while application-specific semantics are managed independently by each framework. This design is in sharp contrast to the original Hadoop version 1 design, in which scheduling was designed and integrated around managing only MapReduce tasks.