As I explained in the introduction to part one, the blog is published retrospectively and (aside from correcting the odd typo) I haven’t made any changes to my original revision notes so as to ensure I don’t violate the  that all exam candidates must sign. As such, you might notice the odd error or missing section (in particular you will notice that there are very few notes on Sandboxed Solutions). This is deliberate, although I would appreciate a comment if you notice any glaring mistakes so as to prevent misinformation.

The final part will contain a downloadable PDF containing the complete series, for those of you that prefer to view content locally.

For those that celebrate it, Happy Easter!

1. Introduction and ” Installing and Configuring a SharePoint Environment (25 per cent)”
2. “Managing a SharePoint Environment (26 per cent)”
3. “Deploying and Managing Applications (24 per cent)” – you are reading this.
4. “Maintaining a SharePoint Environment (25 per cent)”​

3. Deploying and Managing Applications (24 percent)

Manage Web Applications.

From the 

This objective may include but is not limited to: managing databases, Web Application settings, security, and policies

Suggested reading (Web applications)

2. Chapter 6 & 8 of 
3. SharePoint 2010 SQL DB autogrowth – leave it on! (my blog)
4. Web [Application] limits in SP2010 – keep it low! (my blog)

My revision notes (Web applications)

• The “User Policy” option within Web Application management is equivalent to the “Policy for Web application” option in MOSS Central Administration. The “Permission Policy” option contains the definitions of the permission levels that can be selected within user policy (e.g. Full Read).
• Web application policies are the only place in SharePoint where an object can be denied access – this policy cannot be overridden by site level changes to permission (such as those made by a site collection administrator). Policies are typically used for audit purposes – for example auditors could be granted full read with little administrative effort.
• Inherited permissions are generally easier to manage than broken site permissions.
• Permissions should generally be configured on a per-group basis, as opposed to granting individual permissions which can quickly become unmanageable.
• Anonymous user access in SharePoint is determined by the “Limited access” permission level. This permission level is automatically assigned at the root Web if a user or group is given access to a sub site with broken (i.e. not inherited) permissions.
• Anonymous access to application pages can be controlled by the ViewFormPagesLockDown feature.
• The Databases category within Central Administration is very similar to that used for MOSS – one obvious exception is that a failover can be specified for high availability purposes. The database schema level can also be checked – this is important in SP2010 as databases can be upgraded separately from the farm binaries (another high availability feature as downtime is minimised).

Manage site collections.

From the 

This objective may include but is not limited to: managing site collection policies, features, caching, andauditing; configuring site collection security; configuring multi-tenancy; and configuring site collection quotasand locks

Suggested reading (site collections)

6. Content Deployment in SharePoint 2010 (my blog)
7.  (my old blog site)

My revision notes (site collections)

• Options for creating new site collections are identical to those in MOSS with the exception of not being forced to select a template upon creation – you can opt to select one later and delegate this job to the site collection administrator.
• The BLOB cache is a disk-based caching mechanism that is enabled on a per Web application basis in the site web.config file. it is especially useful where content is largely static – e.g. a public facing Web site.
• The output cache (OFF by default) can result in substantial gains in throughput, but uses additional Web server memory due to files being retained for longer. It is configured on a per site collection basis and is only available where the publishing feature is being used. It can also be configured using the Web application configuration (web.config) file, but will then apply to all cache profiles in all site collections.
• Similarly, the object cache (ON by default) reduces the amount of traffic passed between WFE and SQL servers. Again, it can be configured at the Web application and site collection level, and requires the publishing feature to be enabled.
• Site collection locks can be used to place a site collection in a read only or inaccessible state.
• Site collection quotas can be configured to limit site storage, send warning emails upon reaching a certain threshold and limit sandboxed solution resource usage.
• Multi-tenancy in SharePoint 2010 enables hosted service providers to partition client data using shared resources. Hosting is a “first class citizen” (according to ).
• Multi-tenancy provides a real alternative to hosting a Web application per client (which does not scale).
• Grouping (and partitioning) tenants is enabled through the use of Site Subscriptions and an associated ID (GUID) which must be created via PowerShell or the OM.
• Feature packs (sets) allow grouping of site and Web scope features – hosters could use this to group by license type, ISVs can use to package features.
• Host-named site collections allow “vanity URLs” to be used by tenants, even for SSL enabled sites.
• “Content deployment” is the authoring of content in one site collection that will be deployed to another site collection according to a schedule or on an as-need basis.

Deploy and manage SharePoint solutions.

From the 

This objective may include but is not limited to: deploying and managing SharePoint solution packages,managing sandbox solutions, and managing user solutions

Suggested reading (solutions)

My notes (solutions)

Solution resource quota information is available within the “Solutions” gallery underneath top level site settings.