DRAG DROP
A SQL Server Integration Services (SSIS) package named DataFeed interacts with an
external vendor data feed. The package is executed several times a day, either as part of
other packages’ control flow or by itself. The external data feed is unreliable because
network failures and slow response times are frequent. The package is currently deployed
on the file system.
To analyze the reliability of the external data feed, you must collect execution data.
Every time the DataFeed package is executed, the following information must be logged:
Start Time
End Time
Execution Result
Execution Duration
You need to design a logging solution that meets the requirements by using the least
amount of administrative and development effort.
Which three actions should you perform in sequence? (To answer, move the appropriate
actions from the list of actions to the answer area and arrange them in the correct order.)
Answer: 
Create a new project …
Deploy … to SSIS catalog and execute the package …
Query the catalog.executable_statistics
+1
I think that Koala’s answer is right.
agree
Well done Dennis!
Koala is right
Agree with all
At first I would agree.. However what makes me have doubt is the fact that the package is executed as part of other packages.. and that the solution needs to be using the least amount of effort..
If you would create it as project deployment you would need to change all the other packages as well because the have a reference to the file deployed package.. so that would cause a lot of development efforts
creating a custom log solution would be better here imho….
Creating a new project and adding the ‘one’ package that accesses a external vendor data feed to it, isn’t meant to permanently redesign the whole project.
It is mainly to help identify the peculiar issue with this package’s data feed (re: the problem statement: ‘to analyze the reliability of the external data feed, you must collect execution data…’) PLUS, generate some insight from logging info.
create a new project and add the package to the project
Deploy the project that contains the package to the …
Query the catalog.executable_statistics view
i think this apply to the previous version before SQL Server 2012 and you needed to
deploy your packages in MSDB.