How should you change your ETL process to carry out sensor calibration systematically in the future?

You architect a system to analyze seismic data. Your extract, transform, and load (ETL) process runs as a series of MapReduce jobs on an Apache Hadoop cluster. The ETL process takes days to process a data set because some steps are computationally expensive. Then you discover that a sensor calibration step has been omitted. How should you change your ETL process to carry out sensor calibration systematically in the future?
A. Modify the transformMapReduce jobs to apply sensor calibration before they do anything else.
B. Introduce a new MapReduce job to apply sensor calibration to raw data, and ensure all other MapReduce jobs are chained after this.
C. Add sensor calibration data to the output of the ETL process, and document that all users need to apply sensor calibration themselves.
D. Develop an algorithm through simulation to predict variance of data output from the last MapReduce job based on calibration factors, and apply the correction to all data.

Download Printable PDF. VALID exam to help you PASS.

3 thoughts on “How should you change your ETL process to carry out sensor calibration systematically in the future?

  1. C and D make no sense but between A or B…I don’t know. If you ask me I’d say B. Why, if you apply the calibration after the cleaning agregation etc, you might have missed some data.

    Anyone whith clear view on this?

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.