Database Management Systems

SQL Server indexes use a B-tree structure with multiple levels: the root level at the top, intermediate levels that branch between root and leaves, and the leaf level containing actual data or data pointers. 'Intermediate level' is the correct structural term for non-leaf levels between root and leaf.

Stored procedures can execute DDL commands and create various database objects. While stored procedures can technically create views, defaults, and extended procedures, creating indexes within stored procedures is particularly common for maintenance tasks, performance optimization, and automated index management operations.

sp_configure 'allow updates' was a valid configuration parameter in older SQL Server versions, controlling whether users could directly update system tables. This option has been deprecated and removed in modern SQL Server versions for security reasons. The other options (locking, Setup, no of lock) are not valid sp_configure parameter names.

In Sybase cursor declarations, valid keywords and attributes include SENSITIVE (for sensitive cursors that reflect changes), FORWARD (for forward-only cursors), and FETCH (the operation to retrieve rows). 'Position' is not a cursor keyword or attribute - while you can fetch at specific positions, there is no 'POSITION' keyword in cursor syntax. Cursors have attributes like SCROLL, INSENSITIVE, and FORWARD_ONLY.

DELETE is a logged operation that can be rolled back because it writes entries to the transaction log. TRUNCATE is minimally logged and cannot be rolled back. DELETE ALL and REMOVE are not standard SQL commands.

A many-to-many relationship requires three tables: two entity tables plus a junction table that stores foreign key references to both. This intermediate table breaks the M:M relationship into two 1:M relationships.

Oracle Adaptive Risk Manager is certified to run on multiple application servers including Oracle WebLogic, Apache Tomcat, and IBM WebSphere, providing deployment flexibility across different Java EE environments.

SharePoint supports two primary deployment configurations: Standalone (where all components and a basic database reside on a single machine) and Server Farm (which allows databases, application servers, and web front-ends to scale across multiple servers).

List data in SharePoint can be reused in two primary ways: as a lookup field in another list column, and programmatically through the object model or APIs. Lookup fields create relationships between lists, while programmatic access allows custom solutions to retrieve and manipulate list data. Options A and B are each partially correct, making C the complete answer.

In Microsoft SharePoint (specifically older versions like SharePoint 2007), when a new Web Application is provisioned, IIS virtual directory folders and configurations are created by default under the C:\inetpub\wwwroot\wss\VirtualDirectories folder path.

Hidden form fields are ideal for storing small amounts of frequently changing page-specific data when security isn't a concern, as they persist with the page and form without the size limitations of cookies or URL complexity. Cookies have size limits (~4KB) and are sent with every HTTP request, while query strings and URLs are visible in the address bar and limited in length.

ASP.NET stores SessionIDs in cookies by default, using a non-persistent cookie named ASP.NET_SessionId that identifies the user session across requests. The SessionID can be stored in the URL if cookieless sessions are configured, but cookies are the standard default mechanism.

ASP.NET 2.0 includes the Cassini web server (WebDev.WebServer.exe) which allows development without IIS installed. You can build and test ASP.NET applications using only the built-in development web server, though IIS is required for production deployment.

J2EE (Java Enterprise Edition) provides comprehensive support for developing web services through JAX-WS and JAX-RS APIs. WCF (Windows Communication Foundation) is Microsoft's unified framework for building service-oriented applications and web services. ASP.NET supports web services through ASMX (legacy) and Web API (modern) technologies. WPF and Silverlight are client-side UI frameworks for desktop and browser-based applications respectively - they consume web services but are not used to build them.

DataContractSerializer is the default serializer used by WCF to translate .NET objects into XML. XmlSerializer is an alternative that must be explicitly opted into, while DataContractFormatter is not a standard standalone serializer class.