How to Pass the Cloudera CCA-500 Exam: Comprehensive Cloudera Certified Administrator for Apache Hadoop (CCAH) Guide and Tips

HMaster

ResourceManager

TaskManager

JobTracker

NameNode

DataNode

Because there is a more than a single job on the cluster, the FIFO Scheduler will enforce a limit on the percentage of resources allocated to a particular job at any given time

Tasks are scheduled on the order of their job submission

The order of execution of job may vary

Given job A and submitted in that order, all tasks from job A are guaranteed to finish before all tasks from job B

The FIFO Scheduler will give, on average, and equal share of the cluster resources over the job lifecycle

The FIFO Scheduler will pass an exception back to the client when Job B is submitted, since all slots on the cluster are use

Without creating a dfs.hosts file or making any entries, run the commands hadoop.dfsadmin-refreshModes on the NameNode

Restart the NameNode

Creating a dfs.hosts file on the NameNode, add the worker Node’s name to it, then issue the command hadoop dfsadmin –refresh Nodes = on the Namenode

Nothing; the worker node will automatically join the cluster when NameNode daemon is started

Configure yarn.applicationmaster.resource.memory-mb and yarn.applicationmaster.resource.cpu-vcores so that ApplicationMaster container allocations match the capacity you require.

You don’t need to configure or balance these properties in YARN as YARN dynamically balances resource management capabilities on your cluster

Configure mapred.tasktracker.map.tasks.maximum and mapred.tasktracker.reduce.tasks.maximum ub yarn-site.xml to match your cluster’s capacity set by the yarn-scheduler.minimum-allocation

Configure yarn.nodemanager.resource.memory-mb and yarn.nodemanager.resource.cpu-vcores to match the capacity you require under YARN for each NodeManager

Execute hdfs namenode –report on the command line and look at the Last Checkpoint information

Execute hdfs dfsadmin –saveNamespace on the command line which returns to you the last checkpoint value in fstime file

Connect to the web UI of the Secondary NameNode <a href="(http://mysecondary:50090/)">(http://mysecondary:50090/)</a> and look at the “Last Checkpoint” information

Connect to the web UI of the NameNode <a href="(http://mynamenode:50070)">(http://mynamenode:50070)</a> and look at the “Last Checkpoint” information

Stored as metadata on the NameNode

Stored along with the data in HDFS

Stored in the Metadata

Stored in ZooKeeper

You must modify the configuration files on the NameNode only. DataNodes read their configuration from the master nodes

You must modify the configuration files on each of the DataNodes machines

You don’t need to restart any daemon, as they will pick up changes automatically

You must restart the NameNode daemon to apply the changes to the cluster

You must restart all six DatNode daemon to apply the changes to the cluster

Install the impalad daemon statestored daemon, and daemon on each machine in the cluster, and the impala shell on your gateway machine

Install the impalad daemon, the statestored daemon, the catalogd daemon, and the impala shell on your gateway machine

Install the impalad daemon and the impala shell on your gateway machine, and the statestored daemon and catalogd daemon on one of the nodes in the cluster

Install the impalad daemon on each machine in the cluster, the statestored daemon and catalogd daemon on one machine in the cluster, and the impala shell on your gateway machine

Install the impalad daemon, statestored daemon, and catalogd daemon on each machine in the cluster and on the gateway node