Occasionally a job that executes an existing SQL Server Integration Services (SSIS) package does not
complete and nothing is processed. You need to ensure that package logging occurs. Your solution must
minimize deployment and development efforts. What should you do?
A.
Create a reusable custom logging component.
B.
Use the gacutil command.
C.
Use the Integration Services Deployment Wizard.
D.
Run the package by using the dtexec /rep /conn command.
E.
Add a data tap on the output of a component in the package data flow.
F.
Create an OnError event handler.
G.
Use the dtutil /copy command.
H.
Deploy the package by using an msi file.
I.
Run the package by using the dtexec /dumperror /conn command.
J.
Run the package by using the dtexecui.exe utilityand the SQL Log provider.
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.
References:
http://msdn.microsoft.com/en-us/library/ms140246.aspx
http://msdn.microsoft.com/en-us/library/hh231187.aspx
For me a correct response is by modifing the job or the package itself.
So all “run” (assuming one execution) aswers (d, i, j) are to drop off.
gacutil, dtutil and deployments tools can’t modify the package (b, c, g h, k)
now we have to choose between a, e, f
data tap are used in debug mode -> no
between a and f, i bet F.
0
0
hmm if one chooses the Project Deployment Model then it is easy to configure some logging. So I would vote for C
0
0
J
0
0