70-463 · Question #4
To facilitate the troubleshooting of SQL Server Integration Services (SSIS) packages, a logging methodology is put in place. The methodology has the following requirements: - The deployment process…
The correct answer is J. Configure the SSIS solution to use the Project Deployment Model. This question tests knowledge of the SSIS Project Deployment Model, which provides built-in centralized logging to the SSISDB catalog with minimal additional configuration.
Question
To facilitate the troubleshooting of SQL Server Integration Services (SSIS) packages, a logging methodology is put in place. The methodology has the following requirements:
- The deployment process must be simplified.
- All the logs must be centralized in SQL Server.
- Log data must be available via reports or T-SQL.
- Log archival must be automated.
You need to configure a logging methodology that meets the requirements while minimizing the amount of deployment and development effort. What should you do?
Options
- AOpen a command prompt and run the gacutil command.
- BOpen a command prompt and execute the package by using the SQL Log provider and
- CAdd an OnError event handler to the SSIS project.
- DUse an msi file to deploy the package on the server.
- EConfigure the output of a component in the package data flow to use a data tap.
- FRun the dtutil command to deploy the package to the SSIS catalog and store the
- GOpen a command prompt and run the dtexec/rep/conn command.
- HOpen a command prompt and run the dtutil/copy command.
- IOpen a command prompt and run the dtexec/dumperror/conn command.
- JConfigure the SSIS solution to use the Project Deployment Model.
How the community answered
(44 responses)- A7% (3)
- B14% (6)
- C5% (2)
- D2% (1)
- G2% (1)
- J70% (31)
Why each option
This question tests knowledge of the SSIS Project Deployment Model, which provides built-in centralized logging to the SSISDB catalog with minimal additional configuration.
gacutil registers assemblies in the Global Assembly Cache and is used for custom component deployment, not logging configuration.
Using dtexec with a SQL Log provider requires manual command-line execution and does not simplify deployment or automate archival.
An OnError event handler only captures errors and requires custom development; it does not centralize all logs or automate archival.
Deploying via an MSI file addresses package deployment, not logging centralization or archival automation.
A data tap captures output from a specific data flow component for debugging; it does not provide general centralized logging.
Running dtutil to deploy to the catalog is a deployment step, but without switching to Project Deployment Model the catalog's built-in logging is unavailable.
dtexec /rep writes execution reports to the command line or a file, not to a centralized SQL Server log with automated archival.
dtutil /copy copies package files between locations and does not address logging requirements.
dtexec /dumperror writes error dump files to disk, not to a centralized SQL Server logging store.
The Project Deployment Model deploys packages to the SSIS catalog (SSISDB), which automatically centralizes all log data in SQL Server, exposes it via catalog views and T-SQL, and includes a built-in retention and archival job. This satisfies all four requirements with the least deployment and development effort since no custom logging providers or handlers need to be coded.
Concept tested: SSIS Project Deployment Model catalog logging
Source: https://learn.microsoft.com/en-us/sql/integration-services/service/ssis-catalog
Topics
Community Discussion
No community discussion yet for this question.