Cloudera Certified Administrator for Apache Hadoop CDH4 - CCA-410 Exam Practice Test

A. The datanode runs a block scanner datablock scanner to verify the return blocks.

B. The datanode updates it's log of checkum verification

C. A metadata file is written to the datanode containing the checksums for each block

D. The datanode writes a metadata file with the name of the file the block is associated with

E. A metadata file is return to the datanode containing all the other node locations in the namespace

A. Health status check (heartbeats)

B. Launching tasks

C. MapReduce metric reporting

D. Managing tasks

E. Job scheduling/monitoring

F. Job coordination between the resource manager and the node manager

G. Managing file system metadata

H. Resource management

A. They can use different file system

B. They must all use the same filesystem as the namenode

C. They must all use the same file system but this does not need to be the same filesystem as the filesystem used by the namenode

D. they must all be left as formatted raw disk, hadoop format them automatically

E. They must all be left as unformatted, rawdisk;hadoop uses raw unformatted disk for HDFS

A. Your cluster has lost all HDFS data which had blocks stored on the dead DataNode.

B. One physical host crashed.

C. The HDFS cluster is in the safe mode.

D. The DataNode JVM on one host is not active.

A. Configure the client to mount both namespaces by specifying the appropriate properties in the core-site.xml

B. Configure the client to mount the /data namespace. As long as a single namespace is mounted and the client participates in the cluster, HDFS grants access to all files in the cluster to that client.

C. You cannot configure a client to access both directories in the current implementation of HDFS Federation.

D. You don't need to configure any parameters on the client machine. Access is controlled by the NameNodes managing the namespace.

A. The clients sends the data to the name node, which then writes those blocks to the data nodes

B. the client writes immediately to data nodes at random

C. The client queries the name node, which returns information on which data nodes to use. Then client writes to those data nodes.

D. The client immediately to data nodes based on the clusters rack locality settings

A. Information on the file's location in HDFS.

B. Node location of each block belonging to the same namespace.

C. Checksums for the data in the block, as a separate file.

D. None. Only the block itself is written.

A. Execute hdfs dfsadmin -report on the command line in and look at the Last Checkpoint information.

B. Connect to the web UI of the NameNode (http://mynamenode:50070/) and look at the "Last Checkpoint" information

C. Execute hdfs dfsadmin -saveNameSpace on the command line which returns to you the last checkpoint value in fstime file.

D. Connect to the web UI of the Secondary NameNode (http://mysecondarynamenode:50090) and look at the "Last Checkpoint" information

A. To ensure that all blocks in the cluster are 128MB in size.

B. To ensure that there is capacity in HDFS tor additional data.

C. To help HDFS deliver consistent performance under heavy loads.

D. To improve data locality for MapReduce tasks.

E. To ensure that there is consistent disk utilization across the DataNodes.

A. In this configuration, the Secondary NameNode performs deal-time backups of the NameNode.

B. In this configuration, the Secondary NameNode is standby NameNode, ready to failover and provide high availability.

C. In this configuration, the Secondary NameNode performs a checkpoint operation on the files by the NameNode.

D. In this configuration, the Secondary NameNode servers as alternate data channel for clients to reach HDFS, should the NameNode become too busy.