nerdexam
Microsoft

70-463 · Question #132

You are designing a SQL Server Integration Services (SSIS) solution. The solution will contain an SSIS project that includes several SSIS packages. Each SSIS package will define the same connection…

The correct answer is A. Use a project deployment model. The Project Deployment Model meets all three requirements. (1) It supports project-level and package-level parameters that can be set at execution time, allowing connection string values to be changed without modifying the package - ideal for promoting packages across…

Configure and deploy SSIS solutions

Question

You are designing a SQL Server Integration Services (SSIS) solution. The solution will contain an SSIS project that includes several SSIS packages. Each SSIS package will define the same connection managers and variables. You have the following requirements:

  • The deployment model must support changing the content of connection

strings by using parameters at execution time.

  • The deployment model must automatically log events to the SSISOB

database.

  • Maximize performance at execution time.

You need to design a solution that meets the requirements. What should you do? (More than one answer choice may achieve the goal. Select the BEST answer.)

Options

  • AUse a project deployment model.
  • BUse a package deployment model.
  • CUse a package deployment model.
  • DUse a project deployment model.

How the community answered

(57 responses)
  • A
    84% (48)
  • B
    2% (1)
  • C
    5% (3)
  • D
    9% (5)

Explanation

The Project Deployment Model meets all three requirements. (1) It supports project-level and package-level parameters that can be set at execution time, allowing connection string values to be changed without modifying the package - ideal for promoting packages across environments. (2) It automatically logs all execution events (messages, warnings, errors) to the SSISDB catalog database, requiring no additional configuration. (3) Project-level connection managers and parameters are shared across all packages in the project, avoiding redundant initialization and maximizing execution performance. The Package Deployment Model does not support automatic SSISDB logging or project-level parameters, making it unsuitable here.

Topics

#Project Deployment Model#SSISDB logging#connection string parameters#deployment model selection

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 70-463 Practice