Professional Documents
Culture Documents
Question Number (ID) : 1 (432P_1.3_03) ______________________________________________________________________________________________________________________________________________ You are configuring the attack surface for your Microsoft SQL Server 2008 instances. One of your requirements is to ensure that someone cannot send a browse request across the network to enumerate all the servers running SQL Server. How do you meet your security requirements?
1. Start the SQL Server Configuration Manager and enable the Hide Instance property. <Correct> 2. Start the SQL Server Configuration Manager and disable the Transmission Control Protocol/Internet Protocol (TCP/IP) protocol. 3. >>Start the SQL Server Configuration Manager and disable the SQL Browser service. 4. Start the SQL Server Surface Area Configuration Manager and disable remote connections.
Explanation: By default, all SQL Server instances respond to an enumeration request sent across the network. This enables anyone with access to the network to browse for a list of all the servers running SQL Server that are online. You can prevent SQL Server from responding to enumeration requests by starting the SQL Server Configuration Manager, expanding the SQL Server Network Configuration node, right-clicking the Protocols for <instance name>, selecting Properties, setting the Hide Instance property to Yes, and restarting the instance. After the instance is restarted, you no longer can enumerate the server running SQL Server on the network. Disabling the TCP/IP protocol prevents anyone from connecting to the instance remotely. Disabling the SQL Browser service forces anyone attempting to access a named instance to specify the port number for the instance. The SQL Server Surface Area Configuration Manager is a SQL Server 2005 utility that is no longer used in SQL Server 2008.
Objective: Installing and Configuring SQL Server 2008 Sub Objective(s): Configure SQL Server services. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 1 - Lesson 3
Microsoft SQL Server 2008 Step by Step Chapter 2 How to: Hide an Instance of SQL Server Database Engine MSDN Link: http://msdn.microsoft.com/en-us/library/ms179327.aspx
1. Configure the targets property to include all databases. 2. Set the Mandate property of the policy category. 3. >>Add the policy to the DEFAULT policy category. 4. Create a condition that checks all databases. <Correct>
Explanation: The only way to ensure that a policy is checked against all databases is to set the MANDATE property of the policy category. By default, every policy that is created is added to the default category. The default category has the MANDATE property set as a required property. To force the policy check for all databases covered by the target set for a policy, all you need to do is subscribe the instance to the default policy category. So long as you do not change the policy category for a policy, you are assured of having the policy checked for all databases.
Objective: Maintaining SQL Server Instances Sub Objective(s): Implement the declarative management framework (DMF). References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 8 - Lessons 1 and 2
Microsoft SQL Server 2008 Step by Step Chapter 19 Administering Servers by Using Policy-Based Management MSDN Link: http://msdn.microsoft.com/en-us/library/bb510667.aspx
1. >>DDL triggers
<Correct>
2. Policy Based Management 3. Performance Studio 4. Event notifications 5. Database Engine Tuning Advisor
Explanation: DDL triggers can be created to execute any time a security statement is executed. Within the DDL trigger, you can access the EVENTDATA() function to log the statement that was executed. Policy Based Management tells you when a violation to your policies has been created, but it cannot log the statement executed or the login of the user. Event notifications are used to alert when an event occurs; it cannot log information or return the statement that was executed. Performance Studio and Database Engine Tuning Advisor cannot audit security.
Objective: Managing SQL Server Security Sub Objective(s): Audit SQL Server instances. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 11 - Lesson 5
Microsoft SQL Server 2008 Step by Step Chapter 18 DDL Triggers MSDN Link: http://msdn.microsoft.com/en-us/library/ms190989.aspx
1. Extended stored procedures 2. SQL Server Integration Services (SSIS) package <Correct> 3. >>Transact-SQL jobs 4. Data Transformation Services (DTS) package
Explanation: Maintenance plans are implemented as one or more SSIS packages, which lets you apply a schedule to each subtask within a maintenance plan. DTS packages can be run only as legacy code in SQL Server 2008 and are not used to execute maintenance plans. A job is created for a maintenance plan, and that job will call an SSIS package instead of embedding Transact-SQL statements into the job steps. SQL Server 2000 made calls to xp_sqlmaint to perform maintenance plan tasks. This capability no longer exists in SQL Server 2005.
Objective: Maintaining a SQL Server Database Sub Objective(s): Maintain a database by using maintenance plans. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 9 - Lesson 1 Maintenance Plans MSDN Link: http://msdn.microsoft.com/en-us/library/ms187658.aspx
UNIQUE,
You run a test to determine how much compression you are achieving. Following the test, you find out that Microsoft SQL Server is providing very little compression. Why is SQL Server not compressing the data?
1. You need to change the primary key to be CLUSTERED. 2. >>You need to change the compression setting to PAGE. 3. You are running SQL Server 2008 Standard. 4. SQL Server can compress only data in the table. <Correct>
Explanation: SQL Server stores XML, VARBINARY(MAX), and VARCHAR(MAX) columns that contain data in excess of the maximum row size in structures external to the table. Large value data types that are not stored in the row cannot be compressed.
Objective: Performing Data Management Tasks Sub Objective(s): Implement data compression. References:
MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 3 - Lesson 1
Microsoft SQL Server 2008 Step by Step Chapter 5 Creating Compressed Tables and Indexes MSDN Link: http://msdn.microsoft.com/en-us/library/cc280449.aspx
1. Execute sp_help_jobhistory @job_name='Alpha'. 2. Execute sp_help_job @job_name='Alpha'. 3. Execute sp_help_job @job_name='Gamma'. 4. Execute sp_monitor. 5. >>Execute sp_help_jobhistory @job_name='Gamma'. <Correct>
Explanation: sp_help_jobhistory @job_name='Gamma' returns the execution history of the job Gamma, thereby allowing you to determine that last time the job was executed. sp_help_job is used to find out information about a job, but it does not provide data on when the job last executed. sp_monitor provides information on how Microsoft SQL Server is running; it does not provide a record of the last time a specific job was run.
Objective: Monitoring and Troubleshooting SQL Server Sub Objective(s): Identify SQL Agent job execution problems. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 10 - Lesson 1
Explanation: The sys.dm_exec_query_stats dynamic management view displays aggregated execution statistics for each query in the query cache along with the associated query plan. Because sys.dm_exec_query_stats displays only the plan handle, you would use sys.dm_exec_query_plan to return the Extensible Markup Language showplan for the given query as well. The sys.dm_exec_sessions dynamic management view displays information related to a System Process ID (SPID), such as login name, connection string settings, and the last time a request was executed on the connection. The sys.dm_exec_requests dynamic management view contains handles to the SQL statement and the query plan that were last used. It also indicates whether a request is being blocked or waiting for a resource to be allocated and the resources being consumed. The sys.dm_os_wait_stats function aggregates the amount of time that processes had to wait for a particular resource to be allocated to an executing request. The sys.dm_exec_sql_text function takes a SQL handle as the input and returns the associated SQL statement.
Objective: Optimizing SQL Server Performance Sub Objective(s): Collect performance data by using Dynamic Management Views (DMVs). References:
MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 13 - Lesson 5
Microsoft SQL Server 2008 Step by Step Chapter 22 sys.dm_exec_query_stats (Transact-SQL) MSDN Link: http://msdn.microsoft.com/en-us/library/ms189741.aspx sys.dm_exec_query_plan (Transact-SQL) MSDN Link: http://msdn.microsoft.com/en-us/library/ms189747.aspx
1. CREATE ENDPOINT Mirroring3 AS TCP ( LISTENER_PORT = 5022 ) FOR DATABASE_MIRRORING ( AUTHENTICATION = WINDOWS KERBEROS, ENCRYPTION = SUPPORTED, ROLE=WITNESS); GO
2. >>CREATE ENDPOINT Mirroring1 STATE = STARTED AS TCP ( LISTENER_PORT = 7022 ) FOR DATABASE_MIRRORING ( ROLE=PARTNER); GO <Correct> 3. CREATE ENDPOINT Mirroring2 STATE = STARTED AS HTTP( PATH = '/mirror', AUTHENTICATION = (INTEGRATED ), PORTS = ( CLEAR ), SITE = 'SERVER' )
4. CREATE ENDPOINT Mirroring4 AS HTTP( PATH = '/mirror', AUTHENTICATION = (INTEGRATED ), PORTS = ( CLEAR ), SITE = 'SERVER' ) FOR DATABASE_MIRRORING (
Explanation: The statement to create the endpoint named Mirroring1 is correct. A database mirroring endpoint must be created with a type of Transmission Control Protocol (TCP) and a payload of Database Mirroring. The state of an endpoint is STOPPED by default, so you must specify STATE = STARTED explicitly. A listener port must be specified along with a role. All other parameters are optional. The endpoint named Mirroring2 has two problems. A database mirroring endpoint cannot be of type HTTP, and this endpoint creation statement does not have the payload clause. The endpoint named Mirroring3 has all the required elements. However, because the default state of an endpoint is STOPPED, this command needs an additional ALTER ENDPOINT statement added to initiate the mirroring session. The endpoint named Mirroring4 combines a valid endpoint type with an invalid payload option. Database mirroring endpoints must be of type Transmission Control Protocol (TCP).
Objective: Implementing High Availability Sub Objective(s): Implement database mirroring. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 15 Database Mirroring MSDN Link: http://msdn.microsoft.com/en-us/library/bb934127.aspx
1. Create a directory to store the documents. 2. >>Execute sp_configure and pass the 'filestream access level' parameter along with the appropriate access level. 3. Create a table that has a column with the FILESTREAM property. 4. >>Change the FILESTREAM properties in SQL Server Configuration Manager. <Correct> <Correct>
Explanation: Enabling FILESTREAM capabilities is a two-step process. You first have to open SQL Server Configuration Manager, right-click the instance, select Properties, and enable FILESTREAM capabilities on the FILESTREAM tab. Then you have to execute sp_configure 'filestream access level' with a second parameter of either 1 or 2 (along with the RECONFIGURE command) to be able to use the FILESTREAM feature within the instance. You cannot create a table that has a column with the FILESTREAM property until you have a filegroup in the database enabled for FILESTREAM. You can't have a FILESTREAM filegroup until FILESTREAM has been enabled. You do not have to create a directory for the documents. The directory is created when you add the FILESTREAM filegroup; it cannot already exist.
Objective: Installing and Configuring SQL Server 2008 Sub Objective(s): Configure SQL Server instances. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 1 - Lesson 3
Chapter 2 Setting Server Configuration Options MSDN Link: http://msdn.microsoft.com/en-us/library/ms189631.aspx How to: Enable FILESTREAM MSDN Link: http://msdn.microsoft.com/en-us/library/cc645923.aspx
1. Configure event notifications. 2. Use SQL Mail to send notifications. 3. Configure a notification to be sent to an operator. 4. Configure a fail-safe operator. <Correct>
Explanation: SQL Server notifies a fail-safe operator when all notifications to the designated operator have failed. An operator is preconfigured with all contact information and can be configured within the job to send an alert on failure. However, if the alert fails, the operator will not be notified. Database Mail and SQL Mail can be used to send notifications, but you need to execute a stored procedure and pass contact information to do this. This does not meet the requirement that the notifications be sent with the least amount of effort. Event notifications cannot be used to alert a DBA when a job fails.
Objective: Maintaining SQL Server Instances Sub Objective(s): Manage SQL Server Agent operators. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 10 -Lesson 3
Microsoft SQL Server 2008 Step by Step Chapter 21 Defining Operators MSDN Link: http://msdn.microsoft.com/en-us/library/ms179336.aspx
1. Execute sp_configure 'filestream_access_level', 0. 2. >>Execute sp_configure 'filestream_access_level', 1. 3. Execute sp_filestream_configure with an option of 1. 4. Execute sp_configure 'filestream_access_level', 2. <Correct>
Explanation: An access level of 1 enables access to FILESTREAM for Transact-SQL only. An access level of 0 disables access to FILESTREAM, while an access level of 2 also allows Win32 API calls to access FILESTREAM data. The sp_filestream_configure stored procedure was removed just prior to the release of Microsoft SQL Server 2008.
Objective: Managing SQL Server Security Sub Objective(s): Configure surface area. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 8 - Lessons 1 and 2 and 3
MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 11 - Lesson 2
Microsoft SQL Server 2008 Step by Step Chapter 18 sp_configure (Transact-SQL) MSDN Link: http://msdn.microsoft.com/en-us/library/ms188787.aspx
1. It enforces a check constraint on data inserted into the Name column. 2. >>It creates a unique nonclustered index on the Name column of the Production.UnitMeasure table. 3. It creates a unique clustered index on the Name column of the Production.UnitMeasure table. 4. >>It enforces a uniqueness constraint on data inserted into the Name column. <Correct> <Correct>
5. It creates a partitioned nonclustered index on the Name column of the Production.UnitMeasure table.
Explanation: The statement creates a unique nonclustered index on the Name column of the Production.UnitMeasure table and enforces a uniqueness constraint on data inserted into the Name column.
Objective: Maintaining a SQL Server Database Sub Objective(s): Maintain database integrity. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 2 - Lesson 4
Microsoft SQL Server 2008 Step by Step Chapter 5 CREATE INDEX (Transact-SQL) MSDN
Link: http://msdn.microsoft.com/en-us/library/ms188783.aspx
1. >>You must have ALTER TABLE permission on the Products table. 2. >>You must have SELECT permission on the Products table. 3. You must have the ADMINISTER BULK OPERATION permission or be a member of the bulkadmin fixed server role. 4. >>You must have INSERT permission on the Products table. <Correct> <Correct>
Explanation: To import data by using the BULK INSERT command, you need to have INSERT permission on the table you want to load. You also need to have the ADMINISTER BULK OPERATIONS instance-wide permission. Being a member of the bulkadmin fixed server role grants you exactly that permission, so both permission settings are valid. To import data by using the BULK INSERT command, you don't need to have SELECT permission on the table you want to load. ALTER TABLE permission is needed only if one of the following conditions is true: you are using the -E option to import identity values, the table has constraints but constraint checking is disabled, or the table has triggers and trigger execution is disabled. Because none of these conditions is true, you don't need the ALTER TABLE permission.
Objective: Performing Data Management Tasks Sub Objective(s): Import and export data. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 7
<Correct>
2. >>The sys.server_audits view in the master database 3. The sys.database_audit_specifications view in the HumanResources database 4. The Windows System Event log
Explanation: Audit specifications can log to a file, the Windows Application Event log, and the Windows Security Event log. When an audit specification is disabled, an entry is written to the logging location specified for the audit. To find out who disabled a database audit specification and when the audit specification was disabled, you need to look in the Windows Application Event log.
Objective: Monitoring and Troubleshooting SQL Server Sub Objective(s): Locate error information. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 12 - Lesson 1 SQL Server Audit Records MSDN Link: http://msdn.microsoft.com/en-us/library/cc280545.aspx
1. Microsoft Operations Manager (MOM) 2. Third-party performance monitoring tools 3. >>Performance Studio 4. Policy Based Management <Correct>
Explanation: Performance Studio is built into SQL Server 2008, and because Wide World Importers has already deployed SQL Server 2008, there is no additional cost to use the data collection capabilities that can be targeted at any version of SQL Server. Although Policy Based Management can target SQL Server 7.0 through SQL Server 2008, it does not capture performance data. MOM and third-party performance monitoring tools can be used to capture performance and database growth statistics, but each requires a separate installation and license fees, which is a higher-cost solution than using Performance Studio.
Objective: Optimizing SQL Server Performance Sub Objective(s): Use Performance Studio. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 13 - Lesson 7 SQL Server 2008 Performance Management and Analysis Tools Microsoft SQL Server 2008 Step by Step Link: http://microsoftpresssrv.libredigital.com/serverclient/
1. Use database mirroring to copy the primary database in each of the secondary servers and use the Use An Already Initialized Database option. 2. Using SQL Server Management Studio (SSMS), for the first server, select the Generate A Backup On The Primary Database option; for the other servers, use the Restore An Existing Backup option. <Correct> 3. >>Use Transact-SQL BACKUP statements to back up the primary database, and use RESTORE commands in each secondary server. Use SQL Server Management Studio (SSMS) to configure log shipping with already-initialized databases. <Correct> 4. None of the options works for this scenario. Log shipping supports only one secondary database in a log shipping configuration.
Explanation: You can use two options. You can use Transact-SQL statements to back up the primary database and restore it to initialize the secondary database. Alternatively, you can use SSMS to create the first backup and use that backup to initialize all other servers. The option to use database mirroring to create a secondary database doesn't work because you can't use database mirroring to initialize a secondary database. Log shipping supports multiple secondary databases in a single configuration.
Objective: Implementing High Availability Sub Objective(s): Implement log shipping. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 16
Microsoft SQL Server 2008 Step by Step Chapter 23 Log Shipping MSDN Link: http://msdn.microsoft.com/en-us/library/bb895393.aspx
1. Set the priority boost to 1. 2. >>Set the max degree of parallelism to 1. 3. Set the network packet size to 8192. 4. Set the query governor cost limit to 8192. <Correct>
Explanation: CXPACKET is a wait for a synchronization thread due to a parallel query operation. Because your instance should not have any queries that require parallelism, setting the max degree of parallelism to 1 eliminates the possibility of a query being executed with a parallel query plan. The priority boost is used to raise the Microsoft Windows priority of the Microsoft SQL Server service and should not be changed from the default value. The network packet size changes the size of the network packets for the instance and does not affect parallel query plans. The query governor cost limit specifies an upper limit on the amount of time a query is allowed to execute. Setting the query governor cost limit to a nonzero value causes SQL Server to reject any query that is estimated to require more than the configured number of seconds to execute.
Objective: Installing and Configuring SQL Server 2008 Sub Objective(s): Configure SQL Server instances. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 1 - Lesson 3
Microsoft SQL Server 2008 Step by Step Chapter 2 Setting Server Configuration Options MSDN Link: http://msdn.microsoft.com/en-us/library/ms189631.aspx sys.dm_os_wait_stats (Transact-SQL) MSDN Link: http://msdn.microsoft.com/en-us/library/ms179984.aspx
<Correct>
4. mssqlsystemresource
Explanation: The msdb database contains all the policy definitions, as well as the jobs that execute the policy checks. If you do not have a backup of the msdb database, you lose all your policy definitions if you lose the msdb database on the central management server.
Objective: Maintaining SQL Server Instances Sub Objective(s): Back up a SQL Server environment. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 9 - Lessons 1 and 2 and 3
MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 11 - Lesson 6
Microsoft SQL Server 2008 Step by Step Chapter 20 Considerations for Backing Up the model and msdb Databases
Explanation: Members of the securityadmin role can create logins but do not have the authority to assign permissions or reset passwords.
Objective: Managing SQL Server Security Sub Objective(s): Manage logins and server roles. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 11 - Lesson 3
Microsoft SQL Server 2008 Step by Step Chapter 18 Server-Level Roles MSDN Link: http://msdn.microsoft.com/en-us/library/ms188659.aspx
<Correct>
2. ALTER TABLE Fees ADD CONSTRAINT stu_ssnum_unique UNIQUE (Enrollment_Data.stu_ssnum); 3. >>ALTER TABLE Fees ADD CONSTRAINT stu_ssnum_unique FOREIGN KEY (Enrollment_Data.stu_ssnum); 4. ALTER TABLE Enrollment_Data ADD CONSTRAINT stu_ssnum_unique PRIMARY (stu_ssnum); 5. ALTER TABLE Enrollment_Data ADD CONSTRAINT stu_ssnum_unique FOREIGN KEY (stu_ssnum);
Explanation: Foreign keys can reference only columns that have PRIMARY KEY or UNIQUE constraints. Because a table can have only a single primary key, and the Enrollment_Data table already has the stu_id column configured in this role, a UNIQUE constraint needs to be applied to the stu_ssnum column.
Only one primary key can be configured per table. The Key constraint should not be added to the Fees table, but to the Enrollment_Data table. Not only should the FOREIGN KEY constraint not be added to the Enrollment_Data table, but the syntax presented in this statement is incorrect as well. Although it is necessary to add the FOREIGN KEY constraint, a unique index must be placed on the Enrollment_Data table first.
Objective: Maintaining a SQL Server Database Sub Objective(s): Maintain database integrity. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 2 - Lesson 4
Microsoft SQL Server 2008 Step by Step Chapter 5 Enforcing Data Integrity MSDN Link: http://msdn.microsoft.com/en-us/library/ms190765.aspx
1. You need to create a clustered index on the CustomerAddress table. 2. >>You need to defragment the nonclustered indexes with the REBUILD option. 3. You need to alter the nonclustered indexes and apply row compression. <Correct>
4. You need to insert rows into the CustomerAddress table using the TABLOCK query hint.
Explanation: Nonclustered indexes do not inherit the compression properties of the table. To compress an index, you must define the compression setting. After you create an index, you can change the compression settings by executing the following: ALTER INDEX <index name> ON <table name> REBUILD WITH (DATA_COMPRESSION = <ROW | PAGE | NONE>)
Objective: Performing Data Management Tasks Sub Objective(s): Implement data compression. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 3 - Lesson 1
Microsoft SQL Server 2008 Step by Step Chapter 5 Creating Compressed Tables and Indexes
1. Microsoft Windows accounts 2. Microsoft SQL Server logins 3. Proxy accounts <Correct>
Explanation: Proxy accounts are used to grant access to subsystems that will be accessed within a job step, such as SQL Server Integration Services, CmdExec, and replication. For a Windows account to be granted access to a resource within a job step, it has to be granted the authority to log in to the server running SQL Server as well as being added to a specific proxy. Although Windows accounts can be used to control access to resources within job steps, not all Windows accounts can do so. SQL Server logins cannot be used to control access to resources within a job step unless the login was added to a proxy account, and then the proxy account was assigned to the job step. Accounts that have access to SQL Server Agent by being a member of one of the SQL Server Agent roles must still be added to a proxy account before they can control resource access within a job step.
Objective: Monitoring and Troubleshooting SQL Server Sub Objective(s): Identify SQL Agent job execution problems. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 10 - Lesson 1
How to: Configure a User to Create and Manage SQL Server Agent Jobs (SQL Server Management Studio) MSDN Link: http://msdn.microsoft.com/en-us/library/ms187901.aspx
1. Configure the query governor cost limit. 2. Configure the max degree of parallelism. 3. Configure the query cost for parallelism. 4. >>Use Resource Governor. <Correct>
Explanation: The Resource Governor is used to limit the memory and central processing unit utilization of classes of workload executed against an instance. The query cost for parallelism controls the threshold for a query to use multiple processors. The max degree of parallelism controls the number of processors a query can utilize. The query governor cost limit controls the number of seconds that a query can be executed, depending on a specific hardware configuration. Although the query governor can be used to control runaway queries, queries exceeding the threshold are terminated instead of limiting the impact to other users.
Objective: Optimizing SQL Server Performance Sub Objective(s): Implement Resource Governor. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 13 - Lesson 6 SQL Server 2008 Performance and Data Capture Tools Microsoft SQL Server 2008 Step by Step Link: http://microsoftpresssrv.libredigital.com/serverclient/
Managing SQL Server Workloads with Resource Governor MSDN Link: http://msdn.microsoft.com/en-us/library/bb933866.aspx
<Correct>
<Correct>
Explanation: There are many definitions for a hot standby server. Many of these mistakenly try to dictate a time component, such as simultaneous or instantaneous. A hot standby technology is defined as having the capability to detect failures and fail over automatically. Both failover clustering and database mirroring detect failures and fail over automatically. NOTE: Database mirroring meets the requirements for a hot standby only when configured in High Availability operating mode. Log shipping and replication are both warm standby options because they do not have any capability to detect failures or fail over automatically.
Objective: Implementing High Availability Sub Objective(s): Implement a SQL Server clustered instance. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 14
Microsoft SQL Server 2008 Step by Step Chapter 23 Failover Clustering How-to Topics MSDN Link: http://msdn.microsoft.com/en-us/library/ms190990.aspx
1. Location of the snapshot folder 2. Location of the subscriber 3. >>Location of the distribution database 4. Location of the publisher <Correct>
Explanation: The location of the distribution database is critical to the performance of transactional replication because all replicated transactions must be written to the distribution database prior to being forwarded to a subscriber. If you have a high transaction volume, you need to configure the distribution database on another server to isolate the resource consumption. However, the location of the distribution database is almost irrelevant to merge replication. Merge replication uses the distribution database only to log status and error messages. Regardless of the location of the distribution database, merge replication consumes the resource of both the publisher and subscriber to calculate the rows that need to be moved. The location of the publisher or subscriber is relevant only within the application architecture and has the same effect on replication performance regardless of whether you are using transactional or merge replication. The location of the snapshot folder only affects the initial snapshot. The snapshot folder location has an equal effect on transactional and merge replication.
Objective: Installing and Configuring SQL Server 2008 Sub Objective(s): Configure additional SQL Server components. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 1 - Lessons 1 and 2
Microsoft SQL Server 2008 Step by Step Chapter 23 Configuring Distribution Microsoft TechNet Link: http://technet.microsoft.com/en-us/library/ms151860.aspx
1. Set the policy to an on-schedule execution mode. 2. Create an alert to execute a job to expand the database. 3. Set the policy to a check and log. <Correct> <Correct>
4. Create a job to evaluate the policy and expand the database. 5. >>Create a policy on the Size property of the Database facet. 6. >>Create a policy on the SpaceAvailable property of the Database facet. <Correct>
Explanation: The SpaceAvailable property of the Database facet reports the space available in the database in kilobytes. The policy can be set to log when available space falls below a specified threshold. Although you can create an alert directly for the percentage of log space used, you need a policy to log a space event for data files on which an alert can be raised.
Objective: Maintaining SQL Server Instances Sub Objective(s): Implement the declarative management framework (DMF). References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 8 - Lessons 1 and 2
1. Windows login 2. >>Certificate 3. Windows group 4. >>Asymmetric key 5. SQL Server login <Correct> <Correct>
Explanation: You can create logins mapped to certificates and asymmetric keys, but you cannot use either type of account to log in to an instance. You also cannot impersonate a login mapped to a certificate or asymmetric key.
Objective: Managing SQL Server Security Sub Objective(s): Manage logins and server roles. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 11 - Lesson 3
Microsoft SQL Server 2008 Step by Step Chapter 18 Choosing an Authentication Mode MSDN Link: http://msdn.microsoft.com/en-us/library/ms144284.aspx
<Correct>
Explanation: The first step in any restore operation is to back up the tail of the log. By taking a final transaction log backup, you can preserve the maximum amount of committed data for the database. If you start with a full backup, you lose any committed transactions since the last transaction log backup was taken.
Objective: Maintaining a SQL Server Database Sub Objective(s): Back up databases. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 9 - Lesson 1 and Chapter 2 - Lesson 1
Microsoft SQL Server 2008 Step by Step Chapter 20 Tail-Log Backups MSDN
Link: http://msdn.microsoft.com/en-us/library/ms179314.aspx
1. Replication is not configured properly. 2. The tables are defined with non-Unicode data types. 3. >>The collation sequence between the databases does not match. <Correct> 4. You do not understand Russian or French.
Explanation: The replication engine replays transactions that occur against the databases. Because data at each location is stored in the local language, you have three character sets to deal with in the data. If you attempt to insert a character that does not exist for the collation sequence defined, Microsoft SQL Server cannot translate the data and you end up with unintelligible information. The best way to avoid this problem is to use Unicode data types, which can handle all characters used within a language set. In this particular case, the data types in the tables would be non-Unicode and the collation sequences between the databases do not match.
Objective: Performing Data Management Tasks Sub Objective(s): Manage collations. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 2 - Lesson 3
Explanation: READ COMMITTED causes any SELECT operations against the rate table to be blocked until the update has been committed. READ UNCOMMITTED allows data to be read that has not been committed to the database yet, which would violate the business rules. SNAPSHOT isolation level allows read operations to retrieve the data from the rate table as it existed before the update operation began. This would violate the business rules, which do not allow reads to occur during the update process. READ SERIALIZABLE holds locks until the duration of the transaction. Although this also meets the business requirements, it does so with much less concurrency than the READ COMMITTED isolation level.
Objective: Monitoring and Troubleshooting SQL Server Sub Objective(s): Identify concurrency problems. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 12 - Lesson 2
Microsoft SQL Server 2008 Step by Step Chapter 10 SET TRANSACTION ISOLATION LEVEL (Transact-SQL) MSDN Link: http://msdn.microsoft.com/en-us/library/ms173763.aspx
1. >>SQL Server Profiler 2. >>exec sp_who2 3. Application event log 4. Database Engine Tuning Advisor <Correct>
<Correct>
Explanation: The sp_who2 tool returns session-related information, particularly if a process is being blocked. If a process is being blocked for an extended period of time, the user has to wait for the process to complete. This issue normally manifests itself with a call to the Help Desk that performance is slow. If the performance degradation is not due to blocking, you can use SQL Server Profiler and System Monitor to gather information about the system. You can then correlate traces from both tools inside SQL Server Profiler to pinpoint the performance issue. These tools do not represent all the mechanisms you can use to solve the problem: Dynamic Management Views and Dynamic Management Functions contain additional data in the form of wait types, wait times, index statistics, and several other pieces of information that are key to determining the state of the system completely. The Database Engine Tuning Advisor makes performance suggestions based on a workload file from SQL Trace. But it cannot be used to diagnose performance issues as they occur. DAC always lets an administrator connect to a server running Microsoft SQL Server, regardless of how busy it is. DAC is simply an endpoint connected to a User Mode Scheduler (UMS) that is always running; it does not play any role in diagnosing issues. The Application event log contains errors, warnings, and information messages that SQL Server and other applications log. It does not have anything to do with evaluating performance.
Sub Objective(s): Collect trace data by using SQL Server Profiler. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 13 - Lesson 1 SQL Server 2008 Performance and Data Capture Tools Microsoft SQL Server 2008 Step by Step Link: http://microsoftpresssrv.libredigital.com/serverclient/ Using SQL Server Profiler MSDN Link: http://msdn.microsoft.com/en-us/library/ms187929.aspx Monitoring Resource Usage (System Monitor) MSDN Link: http://msdn.microsoft.com/en-us/library/ms191246.aspx
1. Configure the foreign constraint as NOT FOR REPLICATION on the table in the publisher database. 2. >>Configure the check constraint as NOT FOR REPLICATION on the table in the subscriber database. 3. Configure the foreign key constraint as NOT FOR REPLICATION on the table in the subscriber database. 4. Configure the check constraint as NOT FOR REPLICATION on the table in the publisher database. <Correct>
Explanation: Configuring the check constraint as NOT FOR REPLICATION on the table in the subscriber database is correct because when configured as such, the subscriber does not enforce the check constraint during replication. Configuring the check constraint as NOT FOR REPLICATION on the publisher database table is incorrect because you do not want to enforce the check constraint on the subscriber database table. The question did not mention foreign constraints, so the answer about setting them as NOT FOR REPLICATION on the table in the publisher database is incorrect. The question did not mention foreign constraints, so the answer about setting them as NOT FOR REPLICATION on the table in the subscriber database is incorrect.
Objective: Implementing High Availability Sub Objective(s): Implement replication. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 17
Microsoft SQL Server 2008 Step by Step Chapter 23 Controlling Constraints, Identities, and Triggers with NOT FOR REPLICATION MSDN Link: http://msdn.microsoft.com/en-us/library/ms152529.aspx
<Correct>
<Correct>
Explanation: SQL Server Standard and SQL Server Enterprise support database mirroring. Although SQL Server Express and SQL Server Workgroup can be used for the Witness, only databases on SQL Server Standard and SQL Server Enterprise can be partners.
Objective: Installing and Configuring SQL Server 2008 Sub Objective(s): Install SQL Server 2008 and related services. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 1 - Lesson 3
Microsoft SQL Server 2008 Step by Step Chapter 23 Features Supported by the Editions of SQL Server 2008 MSDN Link: http://msdn.microsoft.com/en-us/library/cc645993.aspx
1. >>Use Database Mail to send notifications. 2. Configure event notifications. 3. Configure a notification to be sent to an operator. <Correct> 4. Use SQL Mail to send notifications.
Explanation: An operator is preconfigured with all contact information and can be configured within the job to send an alert on failure. Database Mail and SQL Mail can be used to send notifications, but you need to execute a stored procedure and pass contact information to do this. This does not meet the requirement not to hard-code contact information into the backup jobs. Event notifications cannot be used to alert a DBA when a job fails.
Objective: Maintaining SQL Server Instances Sub Objective(s): Manage SQL Server Agent operators. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 10 -Lesson 3
How to: Create an Operator (SQL Server Management Studio) MSDN Link: http://msdn.microsoft.com/en-us/library/ms175962.aspx
1. Create a service master key and use the service master key to encrypt the data. 2. Create a database master key and certificate in the master database. Use the certificate to encrypt a database encryption key. 3. Implement passphrase encryption within the applications. 4. >>Create a database master key and use the database master key to encrypt the data. <Correct>
Explanation: Transparent database encryption (TDE) encrypts data in the data and log files, thereby meeting the minimum auditing requirements that credit card information be encrypted. TDE uses a database master key in the master database to secure a certificate stored in the master database. The certificate stored in the master database is used to protect a database encryption key. The database encryption key encrypts and decrypts all the pages in the data and log files transparently. Data is encrypted, but applications do not need to be changed to interact with the encryption hierarchy. The service master key is generated automatically the first time you start the SQL Server instance. Database master keys and service master keys can be used to protect other encryption keys, such as certificates, symmetric keys, and asymmetric keys; however, master keys are not used to encrypt data directly. Passphrase encryption would meet the requirements; however, you would have to modify the database structure as well as every application to encrypt and decrypt the necessary data. This would have a great impact on the existing applications, which violates the business requirements.
Objective: Managing SQL Server Security Sub Objective(s): Manage transparent data encryption. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance
Chapter 11 - Lesson 6
Microsoft SQL Server 2008 Step by Step Chapter 18 SQL Server and Database Encryption Keys (Database Engine) MSDN Link: http://msdn.microsoft.com/en-us/library/bb964742.aspx
1. Change the recovery model to BULK-LOGGED during the load process and then back to FULL. 2. Change the recovery model to BULK-LOGGED. 3. Change the transaction log size to accommodate the load. 4. >>Change the recovery model to SIMPLE during the load process and then back to FULL.
<Correct>
Explanation: Bulk operations generate a lot of entries in transaction logs when the recovery model is configured as FULL. You can avoid massive write activity by changing the recovery model to BULK-LOGGED during the load process. But then you should change the recovery model for the database back to FULL. Changing the transaction log size does not solve the problem, which is related to the recovery model setting for the database. Although changing the recovery model to SIMPLE reduces the number of entries written to the transaction log, it is not a recommended recovery model option. The SIMPLE recovery model truncates the transaction log on every checkpoint, so you cannot perform transaction log backups.
Objective: Maintaining a SQL Server Database Sub Objective(s): Manage and configure databases. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 2 -- Lessons 2 and 3 and 4
Microsoft SQL Server 2008 Step by Step Chapter 20 Backup Under the Bulk-Logged Recovery Model MSDN Link: http://msdn.microsoft.com/en-us/library/ms190692.aspx
1. A clustered index on concentration 2. A clustered index on sampleid 3. A clustered index on site 4. >>A nonclustered index on sampleid <Correct>
Explanation: Because the WHERE clause always returns a distinct value, you should use a clustered index. Clustered indexes should be created on values that are unique or highly differentiated. The unique value in this scenario is sampleid. Clustered indexes usually require unique or highly different values. There are likely to be many records that match a particular site (because multiple samples can be drawn from the same site). Clustered indexes usually require unique or highly different values. There are probably as many records that match a particular concentration (because multiple samples from the same site might have the same mineral composition). Nonclustered indexes are usually used when an exact match for a query returns multiple records. The records in sampleid are unique.
References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 4 - Lesson 3
Microsoft SQL Server 2008 Step by Step Chapter 6 Clustered Index Design Guidelines MSDN Link: http://msdn.microsoft.com/en-us/library/ms190639.aspx
1. Database backups
<Correct>
2. >>Blocked processes 3. >>Processes that have been killed 4. Isolation level changes on a connection 5. SQL Server Agent alerts 6. >>Severe errors <Correct> <Correct>
Explanation: The SQL Server error log contains a variety of server-level events, such as each database backup executed, SQL Traces being started or stopped, general instance startup messages, and database recovery operations. It also contains an entry for each server process identifier (SPID) that is killed, as well as any severe error occurring with the instance. A severe error is classified as an error with a severity level of 16 or higher. Blocked processes are not an error condition and do not log information to the SQL Server error log. When the isolation level is changed for a connection, the corresponding entry in sys.dm_exec_requests is updated, but an entry is not made in the SQL Server error log. SQL Server Agent alerts send a notification to an operator, but they do not log information to the SQL Server error log.
Objective: Monitoring and Troubleshooting SQL Server Sub Objective(s): Locate error information. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 12 - Lesson 1
Microsoft SQL Server 2008 Step by Step Chapter 3 Viewing the SQL Server Error Log MSDN Link: http://msdn.microsoft.com/en-us/library/ms187885.aspx
1. >>Integration Services 2. >>Data Mining 3. SQL Server Agent 4. System Monitor 5. Reporting Services 6. Profiler <Correct>
<Correct>
Explanation: SQL Server Agent is used to schedule data collection activities, which are performed by Integration Services packages. Although you can build data mining models against the data collected, data mining is not used by Performance Studio. SQL Server Management Studio ships with many reports to view the data collected into the performance data warehouse and Reporting Services can be used to create additional reports. However, Reporting Services is not used directly by Performance Studio. Collection sets can target performance counters, but System Monitor is not started to gather the counters. Performance Studio uses the SQL Trace API to capture Microsoft SQL Server event data. Profiler is a graphical tool that allows you to interact with the SQL Trace API, but it is not used by Performance Studio.
Objective: Optimizing SQL Server Performance Sub Objective(s): Use Performance Studio. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance
Chapter 13 - Lesson 7 SQL Server 2008 Performance Management and Analysis Tools Microsoft SQL Server 2008 Step by Step Link: http://microsoftpresssrv.libredigital.com/serverclient/ SQL Server Agent MSDN Link: http://msdn.microsoft.com/en-us/library/ms189089.aspx SQL Server Integration Services MSDN Link: http://msdn.microsoft.com/en-us/library/ms141026.aspx
1. >>Changing the SQL Server Agent service account 2. Backing up the transaction log of the primary database 3. >>Changing the schema of the primary database 4. Changing the SQL Server service account
<Correct> <Correct>
Explanation: Changing the SQL Server Agent service account might leave the log shipping jobs without the required permissions to back up and copy. Also, by default, when you back up the transaction log, it is truncated, leaving a gap of transactions that cannot be restored by the log shipping process. Neither changing the SQL Server service account nor changing the schema of the primary database disrupts the log shipping process.
Objective: Implementing High Availability Sub Objective(s): Implement log shipping. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 16
1. Use the CREATE FUNCTION statement. 2. >>Use the CREATE ASSEMBLY statement. 3. Use the ALTER ASSEMBLY statement. 4. Use the ALTER FUNCTION statement. <Correct>
Explanation: You must register the assembly using CREATE ASSEMBLY prior to using CREATE FUNCTION. You need to use the CREATE ASSEMBLY statement prior to the CREATE FUNCTION statement because the assembly must be registered. You can use the ALTER ASSEMBLY statement only after you have registered an assembly using the CREATE ASSEMBLY statement. Because CREATE ASSEMBLY must precede CREATE FUNCTION, it follows that you must use CREATE ASSEMBLY prior to ALTER FUNCTION.
Objective: Installing and Configuring SQL Server 2008 Sub Objective(s): Configure additional SQL Server components. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 1 - Lessons 1 and 2
Microsoft SQL Server 2008 Step by Step Chapter 1 CLR User-Defined Types
1. >>Configure a notification to be sent to an operator. 2. Use Database Mail to send notifications. 3. Configure event notifications. 4. Use SQL Mail to send notifications.
<Correct>
Explanation: Operators can be configured with a pager-on-duty schedule and notifications will not be sent to an operator outside of this schedule. Database Mail and SQL Mail can be used to send notifications, but you need to execute a stored procedure and pass contact information in order to do this. This does not meet the requirement that the notifications be sent with the least amount of effort. Event notifications cannot be used to alert a DBA when a job fails.
Objective: Maintaining SQL Server Instances Sub Objective(s): Manage SQL Server Agent operators. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 10 -Lesson 3
How to: Create an Operator (SQL Server Management Studio) MSDN Link: http://msdn.microsoft.com/en-us/library/ms175962.aspx
1. Create a loginless user named AuditUser. 2. Create a certificate named CerAudit. 3. Add a signature to the DML triggers. 4. Add a countersignature to the DML triggers. 5. Grant Select and Insert permissions to AuditUser. 6. Create a user mapped to CerAudit named CerUser. 7. >>Grant Select and Insert permissions to CerUser. 8. >>Revoke View Definition on the database. 9. Drop the DML triggers and move the code to the stored procedures that modify data in the database. 10. Grant Select and Insert permissions to CerAudit. <Correct> <Correct> <Correct> <Correct>
Explanation: Changes are being rolled back in the HR and Payroll databases because the audit triggers no longer have sufficient permissions to access the audit tables. If you add a signature to the DML triggers, you can elevate the permissions to allow access to the audit tables, but only through the triggers. Users will still not be able to either see or directly access the audit tables. To create a signature with the required authority, you need to create a certificate, create a user mapped to the certificate, grant permissions to the certificate-mapped user, and then add a signature to the DML triggers for the certificate. Revoking View Definition only hides the metadata; it does not fix the permission issue. Creating a loginless user and granting permissions to the loginless user fixes the permission issue only if users can impersonate the loginless user. However, you would expose the audit tables to direct manipulation and violate the business requirements.
Moving the audit code to stored procedures does not solve the permission problem. A countersignature would allow the Select and Insert permissions on the audit tables to be passed back to the user that modified the data, which would violate the business requirements.
Objective: Managing SQL Server Security Sub Objective(s): Manage database permissions. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 11 - Lesson 4
Microsoft SQL Server 2008 Step by Step Chapter 18 ADD SIGNATURE (Transact-SQL) MSDN Link: http://msdn.microsoft.com/en-us/library/ms181700.aspx
1. Select the Use The Detach And Attach Method option in the Copy Database Wizard. 2. >>Drop and then recreate the full-text index after the database is moved to NewAnalysis. 3. >>Select the Use The SQL Management Object Method option in the Copy Database Wizard. 4. Repopulate the full-text index by hand after the Analysis database is moved to NewAnalysis. <Correct> <Correct>
Explanation: The SQL Management Object method in the Copy Database Wizard ensures that the database is not taken offline and can still be accessed. If you select the SQL Management Object Method to move the full-text catalog, you need to repopulate the index manually. Dropping and recreating the full-text index is less administratively efficient than repopulating. If you select the Detach And Attach Method option in the Copy Database Wizard, the database is taken offline and is inaccessible to users.
Objective: Maintaining a SQL Server Database Sub Objective(s): Manage and configure databases. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance
Microsoft SQL Server 2008 Step by Step Chapter 17 Full-Text Index Population MSDN Link: http://msdn.microsoft.com/en-us/library/ms142575.aspx
1. CREATE CLUSTERED INDEX IX_StudentID_EnrollDate On StudentEnrollment (StudentID) On EnrollmentYear_PartFunct (StudentID)[\code] 2. CREATE CLUSTERED INDEX IX_StudentID_EnrollDate On StudentEnrollment (FirstName,Surname) On EnrollmentYear_PartScheme (Firstname,Surname)[\code] 3. CREATE CLUSTERED INDEX IX_StudentID_EnrollDate On StudentEnrollment (EnrollDate) On EnrollmentYear_PartFunct (EnrollDate)[\code] 4. >>CREATE CLUSTERED INDEX IX_StudentID_EnrollDate On StudentEnrollment (StudentID)
On EnrollmentYear_PartScheme (StudentID) 5. CREATE CLUSTERED INDEX IX_StudentID_EnrollDate On StudentEnrollment (EnrollDate) On EnrollmentYear_PartScheme (EnrollDate)[\code]
<Correct>
Explanation: Because the table is partitioned on the basis of enrollment date, the clustered index must also be based on the enrollment date. When creating a clustered index, you must specify the appropriate partition scheme rather than the partition function to tell Microsoft SQL Server which information should be allocated to which filegroups.
Objective: Performing Data Management Tasks Sub Objective(s): Manage data partitions. References: MCTS Self-Paced Training Kit (Exam 70-432): Microsoft SQL Server 2008 - Implementation and Maintenance Chapter 6
Microsoft SQL Server 2008 Step by Step Chapter 7 CREATE INDEX (Transact-SQL) MSDN Link: http://msdn.microsoft.com/en-us/library/ms188783.aspx