Cloudera Certified Administrator for Apache Hadoop (CCAH) CDH5 Upgrade - CCA-505 Exam Practice Test

A. In YARN, resource allocation is a function of virtual cores specified by the ApplicationMaster making requests to the NodeManager where a reduce task is handled by a single container (and this a single virtual core). Thus, the developer needs to specify the number of virtual cores to the NodeManager by executing -p yarn.nodemanager.cpuvcores=2

B. MapReduce version 2 (MRv2) on YARN abstracts resource allocation away from the idea of "tasks" into memory and virtual cores, thus eliminating the need for a developer to specify the number of reduce tasks, and indeed preventing the developer from specifying the number of reduce tasks.

C. In YARN, resource allocation is a function of megabytes of memory in multiple of 1024mb. Thus, they should specify the amount of memory resource they need by executing -D mapreduce.reduce.memory-mp-2040

D. In YARN, the ApplicationMaster is responsible for requesting the resources required for a specific job. Thus, executing -p yarn.applicationmaster.reduce.tasks-2 will specify that the ApplicationMaster launch two task containers on the worker nodes.

E. Developers specify reduce tasks in the exact same way for both MapReduce version 1 (MRv1) and MapReduce version 2 (MRv2) on YARN. Thus, executing -p mapreduce.job.reduce-2 will specify 2 reduce tasks.

A. Configure a default scheduler to run on YARN by setting the following property in
sapred-site.xml:
<name>mapreduce.jobtracker.taskScheduler</name>
<value>org.apache.hadoop.mapred.JobQueueTaskScheduler</value>

B. Configure the ResourceManager hostname and enable node services on YARN by
setting the following property in yarn-site.xml:
<name>yarn.resourcemanager.hostname</name>
<value>your_responseManager_hostname</value>

C. Configure the NodeManager hostname and enable services on YARN by setting the
following property in yarn-site.xml:
<name>yarn.nodemanager.hostname</name>
<value>your_nodeManager_hostname</value>

D. Configure the NodeManager to enable MapReduce services on YARN by adding
following property in yarn-site.xml:
<name>yarn.nodemanager.aux-services</name>
<value>mapreduce_shuffle</value>

E. Configure MapReduce as a framework running on YARN by setting the following
property in mapred-site.xml:
<name>mapreduce.framework.name</name>
<value>yarn</value>

F. Configure the number of map tasks per job on YARN by setting the following property in
mapred-site.xml:
<name>mapreduce.job.maps</name>
<value>2</value>

A. You get an error message telling you that input is not a directory

B. The write silently fails

C. You get a error message telling you that foo.txt already exists. The file is not written to HDFS

D. The write succeeds, overwriting foo.txt in HDFS with no warning

E. You get a warning that foo.txt is being overwritten

F. You get an error message telling you that foo.txt already exists, and asking you if you would like to overwrite

G. The file is uploaded and stored as a plain named input

A. Single point of failure in the NameNode

B. Resource pressures on the JobTracker

C. Ability to run frameworks other than MapReduce, such as MPI

D. Reduce complexity of the MapReduce APIs

E. Standardize on a single MapReduce API

F. HDFS latency

A. nn02 is fenced, and nn01 becomes the active NameNode

B. nn01 is fenced, and nn02 becomes the active NameNode

C. nn01 becomes the standby NamNode and nn02 becomes the active NAmeNode

D. nn02 becomes the standby NameNode and nn01 becomes the active NameNode