You need to establish the best technique to log these invalid rows while minimizing the amount of development effort

You are writing a SQL Server Integration Services (SSIS) package that transfers data from a legacy system.
Data integrity in the legacy system is very poor. Invalid rows are discarded by the package but must be logged
to a CSV file for auditing purposes. You need to establish the best technique to log these invalid rows while
minimizing the amount of development effort. What should you do?

A.
Add a data tap on the output of a component in the package data flow.

B.
Deploy the package by using an msi file.

C.
Run the package by using the dtexecui.exe utilityand the SQL Log provider.

D.
Uses the dtutil /copy command.

E.
Create an OnError event handler.

F.
Use the Integration Services Deployment Wizard.

G.
Use the gacutil command.

H.
Create a reusable custom logging component.

I.
Run the package by using the dtexec /rep /conn command.

J.
Run the package by using the dtexec /dumperror /conn command.
K.
Deploy the package to the Integration Services catalog by using dtutil and use SQL Server to store the
configuration.

Explanation:
According to these references, this answer looks correct.
Reference:
http://www.rafael-salas.com/2012/01/ssis-2012-quick-peek-to-data-taps.html
http://msdn.microsoft.com/en-us/library/hh230989.aspx
http://msdn.microsoft.com/en-us/library/jj655339.aspx