You need to ensure that package logging occurs

You are troubleshooting an existing SQL Server Integration Services (SSIS) package. On several occasions,
the package execution does not finish and no data seems to have been transferred. You need to ensure that
package logging occurs. Your solution must minimizedeployment and development efforts. What should you
do?

A.
Add an OnError event handler to the SSIS project.

B.
Use an msi file to deploy the package on the server.

C.
Open a command prompt and run the gacutil command.

D.
Open a command prompt and run the dtutil /copy command.

E.
Open a command prompt and run the dtexec /rep /conn command.

F.
Open a command prompt and run the dtexec /dumperror /conn command.

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

H.
Create a reusable custom logging component and use it in the SSIS project.

I.
Configure the SSIS solution to use the Project Deployment Model.

J.
Configure the output of a component in the package data flow to use a data tap.
K.
Run the dtutil command to deploy the package to the SSIS catalog and store the configuration in SQL
Server.

Explanation:
According to these references, this answer looks correct.
References:
http://msdn.microsoft.com/en-us/library/ms141212.aspx
http://www.mssqltips.com/sqlservertip/2450/ssis-package-deployment-model-in-sql-server-2012-part-1-of-2/
http://www.mssqltips.com/sqlservertip/2450/ssis-package-deployment-model-in-sql-server-2012-part-2-of-2/