Q1
True / FalseA clustered index determines the physical order of data in a table.
A clustered index defines the physical order of rows in a table based on the index key.
Q2
True / FalseA table can have multiple clustered indexes.
A table can have only one clustered index because it defines the physical order of data.
Q3
True / FalseUnique indexes in SQL Server can enforce the uniqueness of data in one or more columns.
Unique indexes ensure that no two rows have the same values in the indexed columns.
Q4
True / FalseNon-clustered indexes affect the physical order of rows in a table.
Non-clustered indexes do not affect the physical order of rows but create a separate structure for indexing.
Q5
True / FalseFull-text indexes are used for optimizing text-based searches.
Full-text indexes are designed to enhance the performance of text-based searches in SQL Server.
Q6
True / FalseComposite indexes are useful for optimizing queries that involve multiple columns.
Composite indexes include multiple columns, improving the performance of queries that filter or sort based on those columns.
Q7
True / FalseA unique index can be created on a column with duplicate values.
A unique index enforces uniqueness, so it cannot be created on a column with duplicate values.
Q8
True / FalseA filtered index includes only a subset of rows in a table based on a filter condition.
Filtered indexes help to improve performance by indexing only a specific subset of data based on a filter condition.
Q9
True / FalseIndex fragmentation can impact the performance of queries.
Index fragmentation can degrade query performance because the data is not stored in contiguous pages.
Q10
True / FalseSQL Server automatically manages index maintenance tasks like rebuilding and reorganizing indexes.
SQL Server does not automatically handle index maintenance tasks; they need to be managed through scheduled jobs or scripts.
Q11
True / FalseIndexes can speed up data retrieval operations but may slow down data modification operations.
Indexes improve read operations but can slow down insert, update, and delete operations due to the overhead of maintaining the index.
Q12
True / FalseCreating an index on a large table always results in improved query performance.
While indexes can improve query performance, creating too many indexes or poorly designed indexes can lead to performance issues.
Q13
True / FalseCovering indexes include all columns needed by a query, allowing the query to be satisfied entirely by the index.
Covering indexes include all columns required for a query, so SQL Server can retrieve the data directly from the index without accessing the table.
Q14
True / FalseIndex seek operations are generally faster than index scan operations.
Index seeks are more efficient because they search for specific values, while scans read through all rows in the index.
Q15
True / FalseSQL Server automatically decides the best index type for each query.
SQL Server does not automatically choose index types. Database administrators and developers must design and implement indexes based on query requirements.