HOTSPOT
You are designing a SQL Server Integration Services (SSIS) package configuration strategy.
The package configuration must meet the following requirements:
Include multiple properties in a configuration.
Support several packages with different configuration settings.
You need to select the appropriate configuration. Which configuration type should you use?
To answer, select the appropriate option from the drop-down list in the dialog box.
Which configuration type should you use?
HOTSPOT
You are designing a SQL Server Integration Services (SSIS) package configuration strategy.
The package configuration must meet the following requirements:
Include multiple properties in a configuration.
Support several packages with different configuration settings.
You need to select the appropriate configuration. Which configuration type should you use?
To answer, select the appropriate option from the drop-down list in the dialog box.
XML
why not sql server table?
SQL Server
XML file
How a single XML file would store configuration setting for different packages?
I think it SQL Server
https://msdn.microsoft.com/en-us/library/ms188466.aspx
https://www.simple-talk.com/sql/ssis/xml-configuration-files-in-sql-server-integration-services/
XML configuration file
SQL Server table satisfies both requirements of the question, i.e.:
1. Include multiple properties in a configuration.
2. Support several packages with different configuration settings.
Although you can use XML to save configuration for multiple packages but good practice would be to have separate config files for each package or project. If you want to use a single place to store multiple packages configurations, I would choose SQL Server table.
+1
XML configuration files are not secured; they can be opened and read with any text editor. The answer is SQL Server table… meets all requirements PLUS controlled access to the configuration details.
+5
The answer is “SQL Server”