Software Development and Management

In multitiered applications, the browser serves as the first tier (presentation layer), handling user interactions and displaying data. The other tiers typically include application servers and databases.

Selenium is released under the Apache 2.0 license and is freely available, making it open source software. Anyone can use, modify, and distribute it.

The MP View Tool (MPViewer) is used to export and view management pack settings and XML. It allows administrators to extract management pack configurations for backup or transfer. SCOM 2007 and Authoring tool serve different purposes.

ChangeMan and ClearCase are both Configuration Management (CM) tools used for version control and change tracking in software development. They manage source code versions, track changes, and coordinate team access. They are not functional automation or performance testing tools, making 'Configuration Management tools' the correct classification.

SharePoint provides a query string parameter to expose WebParts on a page for debugging and management. Appending ?contents=1 to the page URL displays all WebParts in maintenance view, allowing you to see and manage them. The # prefix is incorrect (it's a client-side fragment), and ?contents=0 would hide the view rather than show it.

In SharePoint solution packages (.wsp files), Manifest.xml is the core file that defines the solution package structure and contents. It lists all features, assemblies, files, and other components included in the solution. Onet.xml, Feature.xml, and Elements.xml are component-level files, not the solution package definition file.

In SharePoint 2007, the hive folder is at %SystemDrive%\Program Files\Common Files\Microsoft Shared\web server extensions\12. This directory contains SharePoint installation files and templates. The '12' refers to SharePoint version 2007 (WSS 3.0/MOSS 2007).

SharePoint event receivers use naming conventions: '-ing' suffix (ItemDeleting, ItemUpdating) are synchronous events that run BEFORE the action and can cancel it. '-ed' suffix (ItemDeleted, ItemUpdated) are asynchronous events that run AFTER the action completes.

SharePoint 2007 site templates are saved as .stp files with a default 10 MB size limit, which can be modified using STSADM commands. These templates capture list structure and library content but exclude certain items like workflow associations. All four statements correctly describe site template behavior and configuration options in MOSS 2007.

.DDF (Data Directive File) files contain instructions for the makecab utility to package SharePoint Solution files (.wsp). They define the source files and cabinet structure needed to create deployment packages. Option B incorrectly identifies the acronym, and Option D is incorrect because .ddf files are typically required for automated .wsp creation.

In SharePoint 2007's content type hierarchy, 'System' is the root parent content type from which all others derive. Content type IDs are hexadecimal strings that always start with '0x' - this is part of their internal identifier structure. 'Item' is a built-in content type but not the parent - it's a child of System. 'Document' is another built-in content type derived from Item, not the parent. The System content type serves as the ultimate base for the entire content type inheritance tree.

To prevent a document deletion, you must use the ItemDeleting event (option B), which fires before the deletion occurs and can be cancelled. The ItemDeleted event (option A) fires after deletion is complete, making it too late to prevent. Setting properties.Cancel = true (option C) within the ItemDeleting event handler cancels the deletion operation. Setting it to false (option D) would allow the deletion to proceed, which is the opposite of what we want.

Creating a custom field type in SharePoint requires three components: an XML definition file (option A) that defines the field type, a field class (option B) that represents instances of the field, and this class must inherit from SPField (option D) or one of its derived classes. SPCustomField (option C) is not a valid base class in the SharePoint object model - this is a common misconception. The correct base class is SPField, which provides the foundational functionality for all SharePoint field types.

The Content Query Web Part (CQWP) can query from a specific site collection (option B), from one specific site and all its subsites (option C), or from a specific list (option D). However, it cannot query across multiple site collections (option A) - this is a known limitation of the CQWP in SharePoint 2007. Each CQWP instance is scoped to a single site collection, making cross-site collection aggregation impossible with this web part alone.

Packaging a workflow feature in SharePoint 2007 requires four files: Manifest.xml (option A) defines the solution manifest, Feature.xml (option B) defines the feature itself, Workflow.xml (option C) contains the workflow definition, and Package.ddf (option D) is the makecab directive file for packaging the solution into a .wsp file. All four files are essential components of the workflow packaging process. The Manifest.xml lists the features in the solution, Feature.xml declares the workflow feature, Workflow.xml defines the workflow structure, and Package.ddf controls the cabinet file creation.