Markup and Web Languages

Content Editor Web Part is the best choice for embedding JavaScript in SharePoint 2007 pages. It allows direct HTML/JavaScript input via source editing. Content Query, Page Viewer, and List View web parts do not support custom JavaScript injection.

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.

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.

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.

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.

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.

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.

When resetting a customized page to site definition: (A) Any Web Part Zones added during customization are removed, (B) Web Parts within zones that existed in the original site definition retain their content because those zones are part of the template, (D) Additional Web Parts added to original zones are not removed. Option C is incorrect because custom zones are indeed removed during reset.

When creating a Site Collection named 'zzz' based on the Team Site template, SharePoint automatically creates three default SharePoint groups: zzz Members (Contribute permissions), zzz Owners (Full Control permissions), and zzz Visitors (Read permissions). There is no 'zzz Readers' group created.

SharePoint Features require two XML files: Feature.xml contains metadata (name, ID, scope, description) and Elements.xml contains the feature's actual definitions (lists, modules, content types). Schema.xml is for list definitions, not features. Manifest.xml is not a SharePoint term.

When resetting a customized page to site definition: (A) Web Part Zones added to the customized page are removed, (B) Contents of Web Parts that were part of the original site definition are not changed, and (D) Additional web parts added in zones from the original definition are not removed. Option C is incorrect because added zones ARE removed during reset.

When creating a Site Collection named 'zzz' using the Team Site template, SharePoint automatically creates three groups: zzz Members (for contributors), zzz Owners (for administrators), and zzz Visitors (for readers). There is no 'Readers' group - that's what Visitors is for.

To create a feature in SharePoint 2007, you need two XML files: Feature.xml (which defines the feature itself - its ID, name, scope, etc.) and Elements.xml (which defines what the feature does - the actual elements like site columns, content types, etc.). Schema.xml is for list definitions, Manifest.xml is not used for features.