Free Microsoft 70-463 Exam Dumps Questions & Answers

You are developing a SQL Server Integration Services (SSIS) package that imports data into a data warehouse hosted on SQL Azure.
The package uses a Foreach container to process text files found in a folder. The package must be deployed to a single server by using the Project Deployment model.
Multiple SQL Server Agent jobs call the package. Each job is executed on a different schedule. Each job passes a different folder path to the package.
You need to configure the package to accept the folder path from each job.
Which package configuration should you use?

• A.Parent Package Variable
• B.Environment Variable
• C..dtsConfig file
• D.XML Configuration File
• E.Registry Entry

You administer a Microsoft SQL Server 2012 server that has SQL Server Integration Services (SSIS) installed.
You plan to deploy new SSIS packages to the server. The SSIS packages use the Project Deployment Model together with parameters and Integration Services environment variables.
You need to configure the SQL Server environment to support these packages.
What should you do?

• A.Create an Integration Services catalog.
• B.Create SSIS configuration files for the packages.
• C.Install Master Data services.
• D.Install Data Quality Services.

You are developing a SQL Server Integration Services (SSIS) project with multiple packages to copy data to a Windows Azure SQL Database database.
An automated process must validate all related Environment references, parameter data types, package references, and referenced assemblies. The automated process must run on a regular schedule.
You need to establish the automated validation process by using the least amount of administrative effort.
What should you do?

• A.Store the System::ServerExecutionID variable in the custom log table.
• B.Use an event handler for OnError for each data flow task.
• C.Store the System::ExecutionInstanceGUID variable in the custom log table.
• D.View the All Messages subsection of the All Executions report for the package.
• E.Create a SQL Server Agent job to execute the
  SSISDB.catalog.create_execution and SSISDB.catalog.start_execution stored procedures.
• F.Create a SQL Server Agent job to execute the SSISDB.catalog.validate_package stored procedure.
• G.Enable the SSIS log provider for SQL Server for OnError in the package control flow.
• H.Store the System::SourceID variable in the custom log table.
• I.Create a table to store error information. Create an error output on each data flow destination that writes OnError event text to the table.
• J.View the job history for the SQL Server Agent job.
• K.Deploy the .ispac file by using the Integration Services Deployment Wizard.
• L.Create a SQL Server Agent job to execute the SSISDB.catalog.validate_project stored procedure.
• M.Create a table to store error information. Create an error output on each data flow destination that writes OnTaskFailed event text to the table.
• N.Deploy the project by using dtutil.exe with the /COPY DTS option.
• O.Use an event handler for OnError for the package.
• P.Deploy the project by using dtutil.exe with the /COPY SQL option.
• Q.Enable the SSIS log provider for SQL Server for OnTaskFailed in the package control flow.
• R.Use an event handler for OnTaskFailed for the package.

You are administering SQL Server Integration Services (SSIS) permissions on a production server that runs SQL Server 2012. All packages are deployed to the SSIS catalog.
Package developers in your company must have permission to perform the following tasks only on their own projects:
*View projects and package
*View Environments
*Validate packages
*Execute packages
You need to grant rights to the developers without assigning unnecessary privileges.
What should you do? (Each correct answer presents part of a solution. Choose all that apply.)

• A.Grant Read permission in the SSIS catalog folder, the projects, and the Environments.
• B.Grant Execute permission in the projects for the developer logins.
• C.Add developer logins to the db_ssisltduser role in the msdb database.
• D.Grant Modify permission in the projects for the developer logins.
• E.Add developer logins to the ssis_admin role in the SSISDB database.
• F.Add developer logins to the db_ssisoperator role in the msdb database.

A SQL Server Integration Services (SSIS) package was deployed two weeks ago with the Project Deployment Model.
Sometimes the package is started as part of a multistep SQL job. At other times, the package is started manually by a database administrator by using the Object Explorer in SQL Server Management Studio.
You need to identify the authenticated user responsible for starting the package each time it executes.
How can you find this information?

• A.In SQL Server Management Studio, view the SQL Agent Error Log.
• B.In the SSISDB.[catalog], query the .[executions] view.
• C.In SQL Server Management Studio, view the SQL Server Log.
• D.In SQL Server Management Studio, view the SQL Agent Job History.
• E.In the SSISDB.[catalog] , query the [event_messages] view.