SharePoint 2007 Development and Administration

SharePoint architecture allows exactly one WebPartManager instance per web part page. The WebPartManager is a singleton control that manages all WebParts on that page, coordinating their lifecycle, personalization, and connections. This design ensures consistent WebPart management across the page.

When pages customized in SharePoint Designer diverge from the site definition, SharePoint provides a 'Reset to site definition' feature that reverts pages to their original template definition. This restores the corporate design standard while preserving the page content structure. Deploying new solutions (A) or changing master pages (B, C) would not reset individual customized pages effectively.

SPSecurity.RunWithElevatedPrivileges executes code using the Application Pool Identity credentials of the web application. This elevates permissions to run code with higher privileges than the current user. It does NOT use SSP account, server owner, or anonymous access.

When new content is not appearing in search results, a full crawl after resetting crawled content is required. Incremental crawls may miss new content if the index is stale. Restarting services or IIS reset will not fix stale search index issues.

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 2007 allows security to be applied at the item level (individual list items) as the lowest granularity. Document libraries and lists can have permissions, but individual items within them can have unique permissions. Site level is higher, not lowest.

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.

Web Packages (.fwp files) in SharePoint are reusable solution packages created with SharePoint Designer. They can be deployed across multiple sites and contain structural definitions like lists, libraries, and their schemas - but not the actual data stored in those lists.

In SharePoint 2007, Customized pages (stored entirely in the database) were called 'Unghosted' in SharePoint 2003. Uncustomized pages (template on filesystem with database reference) were called 'Ghosted'. The terminology changed but the concept remained the same.

SharePoint Designer allows creating workflows and editing layout pages for publishing sites. However, Application Pages (.aspx files in the _layouts folder) cannot be edited with Designer - they must be modified on the file system. Site Columns are created through browser UI or Features, not directly in Designer.

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 Features have four hierarchical scopes: Farm (widest, farm-level features), Web Application (web app features), Site (site collection features), and Web (individual site features). Scopes determine where the feature is activated and visible.

SharePoint 2007 supports NTLM (Windows integrated authentication), Kerberos (more secure Windows auth with tickets), and Forms-based authentication (custom login against SQL/LDAP/AD). Smartcard authentication itself is not a separate mechanism - smartcards use Kerberos or certificate-based auth under the hood.

Page layouts in SharePoint can contain Web Part Zones for dynamic content and Field Controls for metadata display. They can be created through SharePoint Designer or deployed via Features. However, each page layout is associated with a SINGLE content type, not multiple - this is a one-to-one relationship.

Content Types define the schema and must be associated with Page Layouts in publishing sites. A single Content Type can be used to create multiple Page Layouts, providing flexibility in design while maintaining consistent content structure. Option B is incorrect because Content Types are associated with Page Layouts, not the reverse. Option C is incorrect because Page Layouts require an associated Content Type to function properly.

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, the SSP (Shared Services Provider) architecture establishes a many-to-one relationship where multiple Web Applications can consume services from a single SSP, but each Web Application can only be associated with one SSP at a time. This design centralizes shared services while maintaining clear service boundaries for web applications.

STSADM provides four core solution management commands in SharePoint 2007: addsolution (adds to solution store), deploysolution (deploys to web applications), deletesolution (removes from store), and retractsolution (removes deployed instances). These commands form the complete lifecycle management toolkit for .wsp solutions.

Event receivers in SharePoint 2007 inherit from specific base classes depending on their scope. SPListEventReceiver handles list-level events, while SPItemEventReceiver handles item-level events. Options C and D are incorrect because they represent property/definition classes, not valid receiver base classes for inheritance.