Question 4

Answers A and B are correct. Table partitioning should balance processing against multiple machines or align resources for more appropriate use. Covering indexes will make queries against index elements operate faster. By definition, covering indexes are those created by need, based on the queries being performed. Triggers generally slow performance due to additional processing during operations affecting the trigger. RAID 5 is a disk orientation in which data is written, a calculation is performed, and then a second write occurs. Two writes for every data operation would negatively affect performance. C2 security is complete auditing that could drastically slow performance.

For more information, see the following sources:

• Chapter 2, "Creating Database Objects"

• SQL Server 2005 Books Online: "SQL Server Database Engine, Designing and Creating Databases, Tables, Understanding Tables, Special Table Types"

• "Partitioned Tables and Indexes in SQL Server 2005," http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsql90/html/sql2k5partition.asp

• "Chapter 14 - Improving SQL Server Performance," http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scalenetchapt14.asp

• Within MSDN Library, go to MSDN Home, MSDN Library, .NET Development, Improving .NET Application Performance and Scalability, Chapter 14 - Improving SQL Server Performance.