A) Table-level and row-level locking B) Exclusive and shared locking C) Latch and spinlock control D) Pessimistic and optimistic concurrency
A) Shared access with other users B) Priority queue access to tables C) Exclusive access to the data D) Read-only access to the data
A) They prevent all other reads B) They are only applied to index leaves C) Multiple users can read data simultaneously D) They allow exclusive locks to be acquired
A) The Lock Manager B) The database administrator C) The SQL Server optimizer D) The end-user client
A) It automatically reduces performance B) It blocks all other users C) It requires more resources D) It cannot be used on indexes
A) Transactions and rollbacks B) Version IDs and metadata C) Shared locks and exclusive locks D) Latches and spinlocks
A) It restarts the entire database instance B) It forces all threads to use optimistic concurrency C) It pauses all threads until the deadlock clears D) It kills one of the threads and rolls back the transaction
A) The Latch Controller B) The Lock Manager C) The Tempdb system D) The Worker Thread Monitor
A) The transaction log B) The main data table C) The index leaf nodes D) Tempdb
A) By the row's physical memory address B) By the user who initiated the update C) By the ID of the transaction that created the version D) By the system timestamp only
A) They are executed on the older version of the row B) They are rejected with an error C) They are immediately blocked D) They are moved to a waiting queue until the transaction ends
A) Latches are more robust than locks B) Locks are used for DMVs while latches are used for tables C) Latches are less resource intensive than locks D) Locks are more lightweight than latches
A) Only if they are using optimistic concurrency B) Only if the database is read-only C) Yes D) No, only one client at a time
A) Entire index or index leaves B) Rows only C) Database level only D) Pages only
A) SQL Server 6.5 B) SQL Server 2005 C) SQL Server 7.0 D) SQL Server 2000
A) SQL Server 2005 B) SQL Server 7.0 C) SQL Server 2008 D) SQL Server 2000
A) SQL Server Compact Edition B) SQL Server 2000 Personal Edition C) SQL Server 2008 R2 Datacenter D) SQL Server 2005 Express Edition
A) Web Server Edition B) Mobile Edition C) Desktop Engine D) Standard Proxy
A) Database engine capabilities B) Microsoft Access compatibility C) A GUI D) Web admin tool
A) Personal Edition B) Datacenter Edition C) Windows CE Edition D) Desktop Engine
A) No size limit B) 4 GB limit C) 1 GB limit D) 10 GB limit
A) Standard management tools B) Transactional replication C) Full-Text Search D) SQL connectivity
A) 512 B) 128 C) 64 D) 256
A) SQL Server 2005 Express Edition B) SQL Server Compact 3.5 C) SQL Server 2005 Mobile Edition D) SQL Server 2000 Personal Edition
A) Windows CE Edition B) SQL Server 2005 Compact Edition C) SQL Server 2008 R2 D) SQL Server Compact 3.5
A) Oracle B) IBM C) Sybase Inc. D) Microsoft
A) TCP/IP B) UDP only C) FTP D) SMTP
A) Read80Trace B) Best Practices Analyzer C) SQLXML D) PSSDIAG
A) Service Pack 2 B) Service Pack 1 C) Service Pack 3 D) Service Pack 4
A) 1985 B) 1995 C) 1989 D) 1993
A) Columnar in-memory storage (xVelocity) B) OS/2 support C) Big Data Clusters D) Linux support
A) NT-OS B) Shiloh C) Big Data D) xVelocity
A) x64 B) x86 C) ARM D) PowerPC
A) November 30, 2024 B) November 18, 2025 C) December 25, 2025 D) January 1, 2025
A) 100 terabytes B) 640 petabytes C) 524 petabytes D) 12 terabytes
A) 12 terabytes B) 524 gigabytes C) 640 terabytes D) 1 terabyte
A) 12 B) 1024 C) 524 D) 640
A) SQL cluster management B) Hot-add memory C) Core database engine D) Stand-alone services
A) Hot-add memory B) Parallel indexes C) Power Pivot D) SQL Server Management Studio Basic
A) 50 GB B) 4 GB C) 10 GB D) 1 TB
A) 10 GB B) 1 GB C) 50 GB D) 4 GB
A) Client-server architecture B) Massively parallel processing (MPP) C) Embedded architecture D) Single-threaded processing
A) Early 2016 B) 2005 C) 2012 D) 2020
A) 30 days B) 180 days C) 90 days D) 365 days
A) SSEE B) LocalDB C) Fast Track D) Compact Edition
A) Database administrators B) Cloud architects C) Application developers D) Mobile device users
A) Partition B) Extent C) Page D) Allocation unit
A) 4 KB B) 2 KB C) 16 KB D) 8 KB
A) .ldf B) .db C) .mdf D) .ndf
A) .mdf B) .log C) .ldf D) .ndf
A) 4 B) 16 C) 8 D) 32
A) Virtual Data Objects B) Dynamic Management Views C) Performance Monitors D) System Statistics Tables
A) Heap B) Partition C) B-tree D) Clustered index
A) 8 bytes B) 128 bytes C) 64 bytes D) 96 bytes
A) binary B) Integer C) Float D) Varchar
A) System log B) Transaction heap C) Buffer cache D) Disk storage
A) Sequential I/O B) Networked I/O C) Asynchronous I/O D) Synchronous I/O
A) A user ID B) A checksum C) A time stamp D) An encryption key
A) PL/SQL B) MySQL C) T-SQL D) PostgreSQL
A) Data retrieval B) Stored procedure C) SQL dialect D) Query plan
A) Query processor B) Network interface C) Database administrator D) Client application
A) Query optimization B) Index restructuring C) Data serialization D) Schema mapping
A) Cloud compatibility B) Performance benchmarks C) Industry standard compliance D) Legacy
A) Large table size B) Low selectivity C) Complex joins D) High system load
A) Transfer-SQL B) Transact-SQL C) Template-SQL D) Table-SQL
A) Windows OS B) SQLOS C) CLR Host D) ADO.NET
A) Via system-defined stored procedures B) Via external PowerShell scripts C) Via direct memory manipulation D) Via GUI configuration files
A) T-SQL exclusively B) Any managed .NET language C) Assembly code only D) Native C++ only
A) External XML schemas B) SQLOS assemblies C) System stored procedures D) Managed code (UDTs)
A) Direct hardware communication B) Context connections C) Automatic memory garbage collection D) GUI development tools
A) Scheduling maintenance plans B) Installing third-party software C) Writing SQL code documentation D) Modifying Windows registry keys
A) Table deletion and indexing B) Backup, copy, restore & check C) User password recovery D) Graphics rendering
A) pandas B) numpy C) revoscalepy D) scikit-learn
A) Route B) Contract C) Message type D) Queue
A) Service program B) Message type C) Route D) Contract
A) As virtual memory buffers B) As flat text files C) As encrypted objects D) As tables
A) Storage B) Receiving C) Insert D) Processing
A) Queues B) Contracts C) Routes D) Message types
A) Physical firewall control B) Biometric authentication C) Password recovery D) Message encryption
A) Master/slave model B) Peer-to-peer model C) Publisher/subscriber model D) Client/server model
A) Merge replication B) Transactional replication C) Distributed replication D) Snapshot replication
A) Primary key B) Index C) Foreign key D) Rowguid
A) Transactional replication B) Merge replication C) Bi-directional replication D) Snapshot replication
A) Unidirectional B) Bi-directional C) Manual only D) Real-time only
A) XML for Analysis B) SQL/RPC C) SOAP D) REST
A) T-SQL B) MDX C) DMX D) LINQ
A) B-Tree indexing B) Merge sort C) Hash join D) Naive Bayes
A) Dijkstra's algorithm B) QuickSort C) Neural networks D) A* search
A) Full-text indexing B) Database administration C) Data warehousing D) Report generation
A) XML files B) PDF files C) RDL files D) SQL files
A) Data Transformation Services B) Filter Daemon C) Report Builder D) SQL Server Management Studio
A) CSV B) JPEG C) PDF D) DOCX
A) SOAP B) SMTP C) HTTP POST D) Writing to a filesystem file
A) December 2000 B) January 2005 C) March 2010 D) August 2008
A) Web report interface B) ETL capabilities C) Full-text searching D) Notification management
A) 500 B) 255 C) 100 D) 1000
A) msftesql.exe B) sqlservr.exe C) msftefd.exe D) ssis.exe
A) msftesql.exe B) gatherer.exe C) sqlindexer.exe D) msftefd.exe
A) Filter Daemon B) Thesaurus C) Gatherer D) Query Processor
A) Empty fragments B) Stop tags C) Noise words D) Excluded tokens |