|
|
|
The General Share Point 2007 Interview Questions consists the most
frequently asked questions in Share Point. This list of 100+ questions guage
your familiarity with the Share Point platform. The q&a have been
collected over a period of time from various blogs, forums and other
similar Share Point sites
|
5. Microsoft Share Point 2007 Interview Questions for Administrator
|
| 6.1
What is a SharePoint site definition? What is ghosted (uncustomized) and
unghosted (customized)?
|
| 6.2
How does one deploy new SharePoint site definitions so that they are made aware
to the SharePoint system?
|
| 6.3
What does partial trust mean the Web Part developer?
|
| 6.4
What if my assemblies are installed in the GAC?
|
| 6.5
How do I create a custom policy file?
|
6.1 What is a SharePoint site definition? What is ghosted (uncustomized) and
unghosted (customized)?
|
|
SharePoint site definitions are the core set of functionality from which
SharePoint site are built from, building from the SiteTemplates directory in
the SharePoint 12 hive. Site definitions allow several sites to inherit from a
core set of files on the file system, although appear to have unique pages,
thereby increasing performance and allowing changes that happen to a site
propagate to all sites that inherit from a site definition. Ghosted means that
when SharePoint creates a new site it will reference the files in the related
site definition upon site provisioning. Unghosted means that the site has been
edited with an external editor, and therefore the customizations are instead
stored in the database, breaking the inheritance of those files from the file
system.
|
6.2 How does one deploy new SharePoint site definitions so that they are made
aware to the SharePoint system?
|
|
The best way to deploy site definitions in the SharePoint 2007 framework is to
use a SharePoint solution file, so that the new site definition is
automatically populated to all WFE’s in the SharePoint farm.
|
6.3 - What does partial trust mean the Web Part developer?
|
|
If you install assemblies into the BIN directory, you must ensure your code
provides error handling in the event that required permissions are not
available. Otherwise, unhandled security exceptions may cause your Web Part to
fail and may affect page rendering on the page where the Web Part appears. The
following is a typical example of a security exception:
Request for the permission of type
Microsoft.SharePoint.Security.SharePointPermission,
Microsoft.SharePoint.Security, Version=11.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c failed
As stated previously, the WSS_Minimal trust level does not grant permission to
the
SharePointPermission.ObjectModel to assemblies in the BIN directory for
an application. Therefore, if your code attempts to use the Microsoft
SharePoint object model, the common language runtime (CLR) throws an exception.
Since the minimal permission set provides the smallest set of permissions
required for code to execute, the likelihood of additional security exceptions
is increased.
Recommendation Try-catch critical areas to address situations where you
may not have the necessary permissions to accomplish a specified objective.
|
|
6.4 What if my assemblies are installed in the GAC?
|
|
By default, assemblies installed in the global assembly cache (GAC) run with
Full trust. Although, installing your Web Part assembly in the GAC is a viable
option, it is recommended that you install Web Part assemblies in the BIN
directory for a more secure deployment.
|
6.5 What if my assembly is not strongly named? How does my code group change?
|
|
You can specify
membership conditions for a code group in several ways. You can use the UrlMembershipCondition
to specify conditions as follows:
<CodeGroup class="UnionCodeGroup"
version="1"
PermissionSetName="MyCustomPermissions">
<IMembershipCondition class="UrlMembershipCondition"
version="1"
Url="$AppDirUrl$/bin/MyAssemblyName.dll" />
</CodeGroup>
|
6.6 What is a Shared Service Provider? In what circumstances might you create more than one?
|
|
The Shared Service Provider in MOSS is where the administrator manages the Search crawling and indexing in the portal. It is also where the information from Active Directory is compiled. The reasons for having more than one would be to ensure information in a secure or sensitive part of your portal is not included in search results for the rest of the portal.
|
6.7 What are Features and Solutions and what is the difference between the two?
|
|
Features are a method for developers to package customisations and deploy them to the SharePoint portal. They can then be activated and deactivated at the Site Collection level. Solutions are a way to bundle features together for deployment.
|
6.8 What is the difference between a Site Definition and a Site Template?
|
| Site Definitions are stored on the hard drive of the SharePoint front end servers. They are used by the SharePoint application to generate the sites users can create. Site Templates are created by users as a copy of a site they have configured and modified so that they do not have to recreate lists, libraries, views and columns every time they need a new instance of a site. |