Microsoft SharePoint 2007 Administration and Development

WebParts can be closed by users and removed permanently by page owners. They can also be minimized to reduce screen space while remaining on the page. WebParts cannot be individually disabled - they must be closed or removed from the page.

Feature.xml defines the feature itself including properties and activation scope. Elements.xml contains the feature's actual elements like site columns, content types, or list templates. Schema.xml defines list views and forms, while Manifest.xml is for solution packages.

Features can only be installed using STSADM command-line tools in SharePoint 2007. However, once installed, features can be activated through both STSADM commands and the SharePoint user interface. Uninstallation requires STSADM and cannot be done through the UI.

Application pages in SharePoint 2007 are stored in the LAYOUTS directory and are available farm-wide across all sites. They do not run in safe mode - that applies to site pages. Their accessibility spans the entire farm, not limited to a specific site scope.

To enable Create Page and Create Site options in a Team Site, you must activate the Office SharePoint Server Publishing Infrastructure at the site collection level and the Office SharePoint Server Publishing feature at the site level. These publishing features add the necessary content creation capabilities.

SharePoint 2003 uses 'Virtual Server' terminology, not 'Virtual Site'. IIS correctly maps to 'WebSite', and SharePoint 2007 onwards uses 'Web Application'. Option C is indeed the incorrect mapping because it misstates SharePoint 2003's terminology.

SPWebConfigModification is the correct SharePoint API class for programmatically modifying web.config files through the SharePoint object model. It provides safe, tracked modifications without manual file editing.

Business Data Catalog (BDC) is an Enterprise-only feature in SharePoint 2007. Standard Edition and Windows SharePoint Services 3.0 do not include BDC capabilities. There is no separate 'Developer Edition' of SharePoint Server 2007.

In SharePoint 2007, the available permissions include 'Manage Lists', 'Manage Permissions', and 'Manage Web Site', but there is no permission called 'Manage List Item' - this is the incorrect option.

The 'Use Client Integration Features' permission controls whether users can access features that require client-side integration, including 'Upload Multiple Documents', 'Edit in Datasheet view', and 'Open with Windows Explorer'. Removing this permission hides these options.

Site-level events like SiteDeleted and SiteDeleting are handled by SPWebEventReceiver. SPSiteEventReceiver does not exist in the SharePoint object model, and SPWebSiteEventReceiver is also not a valid class name.

The number of days to show the 'New!' icon for list items can be changed using the STSADM command line tool with the 'setproperty' operation. This setting is not available through Central Administration UI or individual site collection settings.

The Microsoft.SharePoint.dll is located in the ISAPI folder under the 12 hive: 'Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI'. This is the correct location to add references when developing SharePoint solutions.

Email alert templates in SharePoint 2007 are stored in and can be modified through the AlertTemplates.xml file located in the SharePoint hive. This file contains all the email notification templates used by SharePoint alerts.

Workflows in SharePoint 2007 can be triggered from Content Types, Lists, and Document Libraries, but cannot be directly triggered from Site Columns. Site Columns are reusable column definitions, not list-level or item-level objects where workflows can be attached.

SharePoint Designer workflows in SharePoint 2007 could only be associated with a single list or document library, not multiple lists or libraries simultaneously. Each workflow created in SharePoint Designer is bound to one specific list or library.

The 'Upload Multiple Documents' option requires the 'Use Client Integration Features' permission. Removing this permission hides client-side integration features including the multiple upload functionality, datasheet view, and Windows Explorer access.

In SharePoint list definitions, Schema.xml contains the complete list schema including views, fields, forms, and other list elements. To add a new view to a list definition, you modify the Schema.xml file. Onet.xml defines site definitions and contains references to list templates, Feature.xml defines features, and Fldtypes.xml defines custom field types - none of these directly control list views.

The Lists.asmx web service (accessed via _vti_bin/lists.asmx) is the primary SOAP web service in SharePoint 2007 for working with lists and list items. It provides methods like GetListItems(), UpdateListItems(), and AddListItems() to query and manipulate list data programmatically. SPLIST.asmx and Listdata.asmx are not standard SharePoint web services.

IFilters are the components used by SharePoint Search to index various file formats including PDF documents. IFilters are protocol handlers that extract text and properties from files during the crawling process. JFilter, DocFilter, and SearchFilters are not standard SharePoint 2007 components for this purpose.