Professional Documents
Culture Documents
Author Information
Vishal Gupta, having experience of 15 yrs. using Microsoft Technologies. Since last eight years working on
creating solutions using SharePoint 2003, Moss 2007 and SharePoint 2010.The solutions involves creation and
designing of internet & intranet Portals for various small, medium & large-scale organizations. Being an
architect for mission critical assignments, created the architecture to meet functional as well as non-functional
business requirements. I am Microsoft Certified [MCP, MCSE, MCSE+I, MCSD, MCTS]. I Love to enable
organizations to implement SharePoint.
Where to find Vishal Gupta online:
Website: http://vishalguptasharepointblog.blogspot.com/
Twitter: vguptadelhi
Facebook: Facebook profile-vgup
LinkedIn: http://www.linkedin.com/in/vishalguptasharepoint
MySpace: http://www.myspace.com/568552837
Blog: http://vishalguptasharepointblog.blogspot.com/
Mail:vguptadelhi@gmail.com
EBook 4
Vishal Gupta [MCTS, MCP, MCSD, MCSE, MCSE +I, CNA, NCIM, NCIBS, BPP, MCA, MASE]
LinkedIn: Http://in.linkedin.com/in/vishalguptasharepoint
Page 0
vguptadelhi@gmail.com
twitter.com/vguptadelhi
0. Introduction
The aim of writing SharePoint Interview capsule is to list SharePoint 2010 interview questions. This eBook
contains questions in simple language with scenarios to enable user to remember easily.
2.
3.
SharePoint
Products
Site Server V
1.0 (1996)
Site Server V
3.0 (1998)
Microsoft
Frontpage
SharePoint
Team Services
(STS) in 2001
SharePoint
Designer 2007
SharePoint
Portal Server
2003
Windows
SharePoint
Services 2.0
SharePoint
Designer 2010
Office
SharePoint
Server 2007
Windows
SharePoint
Services 3.0
SharePoint
Portal Server
2010
SharePoint
Foundation
Server 2010
SharePoint
Portal Server
(SPS) in 2001
4.
Communities: The new version of SharePoint allows users to work together in different ways.
Microsoft has enhanced the social feature of SharePoint 2007 in SharePoint 2010 and has made it
look better. Communities allow people to collaborate in groups, share knowledge, and find
information on various topics easily.
Content: SharePoint content shifts SharePoint 2010 from a departmental solution to an enterprise
solution. There has been massive improvement in content wherein users can add a significant number
of documents to SharePoint. They can even use external data storage options to store more data.
Search: Microsoft SharePoint 2010 has acquired FAST search server, which improves the search
tremendously for users. Now, users not only can search for content, but also people. User can opt for
better language options with thumbnails and previews. User can even sort out the search queries and
study similar search to get relevant search results.
Insights: with the help of SharePoint insights, users can access information through different data
sources like dashboards, scorecards, reports and more. To help users, Microsoft has introduced
performance point server to the SharePoint platform. It is also known as Performance point services
for SharePoint. It helps users discover right people and expertise to make better business decisions.
Compositions: SharePoint being a complete platform helps users in creating their code solution on
premises or in the cloud. Complex application can be developed with the help of well-known tools
like:
InfoPath
SharePoint designer 2010
Visio 2010
5.
7- Health Monitoring: SharePoint Server 2010 includes an integrated health analysis tool called
SharePoint Health Analyzer that enables SharePoint Server to automatically check for potential
configuration, performance, and usage problems
8- Managed Metadata: The Managed Metadata Service supports the use of managed metadata, as
well as the sharing of content types across the enterprise.
9- Performance Point Services: Performance Point Services in Microsoft SharePoint Server 2010
provides flexible, easy-to-use tools for building dashboards, scorecards, and key performance
indicators (KPIs
10- Records Management: In SharePoint Server 2010, user can manage records in an archive, or can
manage records in the same document repository as active document
11- Sandboxed Solutions: User can deploy sandboxed solutions to quickly and more securely solve
business problems. Sandboxed solutions are like farm solutions except in the following ways:
they are rights-restricted and have a more permissive deployment policy than farm solutions;
they are limited to the site collection to which they are deployed;
12- Social Computing: SharePoint Server 2010 includes social networking tools such as My Site Web
sites and social content technologies such as blogs, wikis, and really simple syndication (RSS).
These features are built upon a database of properties that integrates information about people
from many kinds of business applications and directory services
13- Upgrade:
13.1: Visual Upgrade:
A new feature that is available with upgrade allows the server administrator or site owner to
determine when and if the new look for SharePoint Server 2010 is used for a particular site
collection. Server administrators can choose to adopt the new look and feel for all sites during
upgrade, let site owners make the choice after upgrade, or keep the old look and feel for all site
13.2: Feature Upgrade:
SharePoint Foundation 2010 provides new members and types that make it possible for user to
upgrade custom Features through versioning and declarative upgrade actions. User can update
any Features created for Office SharePoint Server 2007 to work with SharePoint Server 2010 by
using these members.
14- Visio Services: The Visio Graphics Service is a service on the SharePoint Server 2010 platform that
enables users to share and view Visio diagrams and enables data-connected Microsoft Visio 2010
diagrams to be refreshed and updated from a variety of data source
15- Windows Power Shell: Windows Power Shell is the new command-line interface and scripting
language specifically designed for Admin
16- Client Object Model: Microsoft SharePoint Foundation 2010 introduces three new client APIs for
interacting with SharePoint sites: from a .NET managed application, from a Microsoft Silverlight
or from ECMAScript (JavaScript, JScript) that executes in the browser. The new client object
models provide an object-oriented system for interoperating with SharePoint data from a remote
computer easier to use existing SharePoint Foundation Web services.
6.
What are the key differences between Windows Shared Services 3.0 and MOSS 2007?
Feature Name / Area
WSS (3.0)
MOSS 2007
Inc.
Inc.
N/A
New
Wikis
Inc.
Inc.
Blogs
Inc.
Inc.
Email integration
Inc.
Inc.
Document collaboration
Inc.
Inc.
Inc.
Inc.
Enterprise Portal
N/A
N/A
New
User profiles
N/A
New
Collaboration
WSS (3.0)
MOSS 2007
Audience targeting
N/A
New
Site Manager
N/A
New
Inc.
Inc.
N/A
New
N/A
New
Content syndication
N/A
New
Inc.
Inc.
Inc.
Inc.
Integration
with
access,
PowerPoint, word 2007
Enterprise search
Inc.
Inc.
Search results
Inc.
Inc.
N/A
New
People search
N/A
New
N/A
New
Indexing controls
N/A
New
Administration management
N/A
New
User interface
Inc.
Inc.
N/A
New
Inc.
Inc.
N/A
New
Page layouts
N/A
New
Navigation controls
N/A
New
Content authoring
N/A
New
N/A
New
Records repository
N/A
New
N/A
New
N/A
New
N/A
New
N/A
New
N/A
New
N/A
New
N/A
New
N/A
New
Integrated
business
intelligence
dashboards
Web based business intelligence using
excel services
N/A
New
N/A
New
excel,
and
Business intelligence
WSS (3.0)
MOSS 2007
N/A
New
N/A
New
Notification service
N/A
New
Single sign on
N/A
New
N/A
New
Inc.
Inc.
Inc.
Inc.
Platform services
7.
8.
What are the key differences between Windows Shared Services 3.0 and Microsoft SharePoint
Foundation 2010?
Feature Name / Area
WSS (3.0)
Foundation 2010
N/A
New
Windows PowerShell
N/A
New
Sandboxed solutions
N/A
New
N/A
New
Central administration
N/A
New
N/A
New
Ribbon Interface
N/A
New
ULS Logging
N/A
New
N/A
New
Upgrade
N/A
New
Health monitoring
N/A
New
Audience targeting
N/A
New
N/A
New
N/A
New
Workflows
N/A
New
SharePoint designer
N/A
New
N/A
New
N/A
New
What are the key differences between SharePoint Server 2007 vs. SharePoint Server 2010?
Feature Name / Area
Office Integration
Inc.
Imp
Line-of-Business Integration
Inc.
Imp
Inc.
Imp
Inc.
Imp
Sites
Web Analytics
N/A
New
Mobile Connectivity
Inc.
Imp
Full-fidelity viewing
N/A
New
Editing to mobile
N/A
New
Contextual Ribbon
N/A
New
Microsoft Silverlight
N/A
New
N/A
New
Tagging
N/A
New
Audience Targeting
Inc.
Imp
People profiles
Inc.
Imp
N/A
New
Micro blogging
N/A
New
Note Board
N/A
New
Recent activities
N/A
New
Organization Browser
N/A
New
Add colleagues
Inc.
Imp
Social bookmarks
N/A
New
Tags
N/A
New
Blogs
Inc.
Imp
Wikis
Inc.
Imp
Enterprise Wikis
N/A
New
Ratings
N/A
New
Colleague suggestions
Inc.
Imp
Keyword suggestions
N/A
New
Compliance Everywhere
N/A
New
N/A
New
N/A
New
N/A
New
N/A
New
Document Sets
N/A
New
N/A
New
N/A
New
Inc.
Imp
Inc.
Imp
Inc.
Imp
Inc.
Imp
Inc.
Imp
N/A
New
Communities
Content
Search
N/A
New
N/A
New
N/A
New
KPI details
N/A
New
Dashboard Designer
Inc
Imp
N/A
New
N/A
New
N/A
New
PowerShell scripting
N/A
New
N/A
New
Support
for
Analytical
Services
formatting
Additional data sources, including
external lists and "Power Pivot"
workbooks (naming to come)
Imp strategy map connection and
formatting
Seamless management of dashboard
content
Integrated filter framework
N/A
New
N/A
New
N/A
New
Inc.
Imp
N/A
New
Calculated KPIs
N/A
New
Imp visualizations
N/A
New
N/A
New
N/A
New
Browser-based customizations
Inc.
Imp
N/A
New
SharePoint Designer
Inc.
Imp
Human workflow
Inc.
Imp
Form Services
Inc.
Imp
Visio Services
N/A
New
Access Services
N/A
New
Sandboxed Solutions
N/A
New
Composites
9.
What are the key differences between SharePoint Foundation 2010 vs. SharePoint Server 2010?
Feature Name / Area
Excel Services
N/A
New
Visio Services
N/A
New
Web analytics
N/A
New
Windows PowerShell
Inc.
Inc
Multilingual interface
Inc
Inc
Ribbon interface
Inc
Inc
Enterprise search
N/A
New
N/A
New
N/A
New
Sandboxed solutions
Inc
Inc
Inc
Inc
Audience targeting
Inc
Inc
Mobile connectivity
Inc
Inc
N/A
New
N/A
New
Inc
Inc
Workflows
Inc
Inc
Query enhancements
Inc
Inc
10. What are the key differences between NET vs. SharePoint?
Feature Name / Area
.NET
SharePoint
Creation
Time
Skilled Professionals
License Requirement
3.
Security: User can define unique user groups and permissions for each site as well as site
elements.
4. Navigation: Site navigation reflects the relationships among the sites in a site collection. User can
fine-tune site's navigation experience by configuring unique navigation links in each part of site's
hierarchy. Therefore, planning navigation and planning sites structures are closely related
activities.
5. Web pages: Web pages in sites or site collection are used to display information.
6. Site layouts: Site Layout dictates the overall look and feel of the SharePoint site.
7. Themes: Themes specify the appearance of site in terms of Color & font.
8. Regional settings: Regional settings are specific to particular country or geography, such as locale,
time zone, sort order, time format and calendar type.
9. Search: User can make each site having unique search settings. For example, user can specify
that a particular site never appear in search results.
10. Content types: A content type defines the attributes of a list item, a document, or a folder.
11. Workflows: Workflow defines the action or series of actions that has to be performed on the
occurrence of event.
13. What is Sub Site?
A sub-site is a single SharePoint site within a site collection. A sub-site can inherit permissions and
navigation structure from its parent site or can be specified and managed independently.
14. What is List?
A SharePoint list is a collection of records related to an entity like a student, employees, etc. Records
in lists are termed as items. A list contains columns or fields that define the item data or metadata.
Lists are created using a GUI interface by defining the metadata types. Once the Lists are created, it
becomes very easy to add, edit, delete, and search items in it.
15. What is Document Library?
A Document library allows users to easily store, upload, share, collaborate, and track documents or
files. Users can also store the properties related to documents called metadata to make the
documents easily searchable.
16. What is Picture library?
A Picture library allows users to easily store, upload, share, collaborate and track images or digital
pictures. Users can also store the properties related to images called metadata to make the images
easily searchable.
17. What is Check-out?
Check-out ensures that only one person can edit a document at a time. To edit a document, a user
would first have to check out a document. This prevents anyone else from editing the document until
that user check the document back in. During the period that the document is checked out, other
users can only view a read-only version of the document.
18. What is Check-in?
Check in a file means that user is uploading the modified file to the library and it is now available for
edit by other users. Once the document is checked in, the document becomes available again to be
checked out by someone else. In addition, all changes made by the person who checked in the
document are now visible to others.
19. What is Versioning?
Versioning allows updates, restoring and tracking of the items in a list or in a library when they are
changed. Versioning makes use of version numbers to keep track of changes.
20. What is Site Columns?
A site column is a reusable column definition, or template that user can assign to multiple lists across
multiple SharePoint sites. Site columns are useful if user organization wants to establish some
consistent settings across lists and libraries.
21. What are the various built in columns available in SharePoint 2010?
1. Single line of text
2. Multiple lines of text
3. Choice (menu to choose from)
4. Number (1, 1.0, 100)
5. Currency ($, , )
6. Date and Time
7. Lookup (information already on this site)
8. Yes/No (check box)
9. Person or Group
10. Hyperlink or Picture
11. Calculated (calculation based on other columns)
12. Full HTML content with formatting and constraints for publishing
13. Image with formatting and constraints for publishing
14. Hyperlink with formatting and constraints for publishing
15. Summary Links data
16. Rich media data for publishing
17. Managed Metadata
22. What is Content Type?
A content type is a reusable collection of metadata (columns), workflow, behavior, and other settings
for a category of items or documents. Content types enable user to manage the settings for a
category of information in a centralized and reusable manner. A content type defines the attributes of
a list item, a document, or a folder. Each content type can specify properties to associate with items
of its type.
23. What is rating?
Rating provides user the ability to rate content (of any type, lists, documents, pages on a site, and
even content types) and stores that rating information in the database. It is an assessment or
classification of content on a scale according to how well the content meets specific criteria. Ratings
show an average score that can range from 1 to 100.
24. What is Audience targeting?
The content inside lists, libraries, web parts, etc., can be targeted to appear only for the users who are
members of a particular group or audience. The audience can be identified via SharePoint groups,
distribution lists and security groups.
25. What are views?
User can use views to see the items in a list or library that are most important to user or that best fit a
purpose. For example, user can create views of the files that were created most recently, of the list
items that apply to a specific department, or of the files created by one person. After creating a view,
it is always available when user looks at a list or library. User can create personal views and public
views. A personal view is available only to user while looking at a list or library. A public view is
available when anyone looks at a list or library. To create a public view, user must have permission to
change the design of the list or library. User can make a public view the default view for a list or
library.
26. What are the various types of views?
1. Standard This view displays list items or files like a traditional list on a Web page. Standard view
is the default for most types of lists and libraries, and user can customize it in several different
ways.
2. Calendar This view displays the calendar items in a visual format that is similar to a desk or wall
calendar. User can apply daily, weekly, or monthly views in this format. For example, user can
create a calendar to track the team's deadlines for a project or holidays for the organization.
3. Datasheet This view provides data in a format that user can edit, such as a table in a database
or spreadsheet. This view can be helpful if user need to perform large editing tasks or
customization, or export data to a spreadsheet or database program. Datasheet view requires a
4.
control or program that is compatible with Windows SharePoint Services, such as Office Access
2007, and ActiveX control support.
Gantt This view provides a visual view of data, with bars that track progress, if data is based on
a time interval. A Gantt view can help user manage projects and see a quick overview of the data.
User can use this view, for example, to see which tasks overlap each other and to visualize overall
progress.
as well as some site content (such as document libraries). Site templates are used to allow the rapid
creation of websites and basic content in a SharePoint system.
Following is a list of site templates available in SharePoint 2010.
Template
Purpose
Category in
Site
Collection
Category in
Site
Assets
Web
Database
Basic Meeting
Workspace
N/A
Meetings
Web
Databases
Meetings
Enterprise
Search
Meetings
Meetings
Collaboration
Collaboration
Blank
Custom
Content
Enterprise
N/A
N/A
Web
Databases
N/A
Web
Databases
Meetings
Meetings
Enterprise
Content
Collaboration
Collaboratio
n, Content
Enterprise
Search
Publishing
Content
Basic
Search
Center
Blank Meeting
Workspace
Blank Site
Blog
Business
Intelligence
Center
Charitable
Contributions
Web Database
Contacts Web
Database
Decision
Meeting
Workspace
Document
Center
Document
Workspace
Enterprise
Search Center
Enterprise Wiki
&
FAST
Search
Center
Group
Site
Work
Issues
Web
Database
Multipage
Meeting
Workspace
My Site Host
Personalization
Site
Projects Web
Database
Publishing
Portal
Enterprise
Search
Collaboration
Collaboratio
n
N/A
Web
Databases
Meetings
Meetings
Enterprise
N/A
N/A
Blank
Custom
N/A
Web
Databases
N/A
Publishing
&
Publishing Site
Publishing Site
with Workflow
Records Center
Social Meeting
Workspace
Team Site
Visio Process
Repository
N/A
Content
N/A
Content
Enterprise
Data
Meetings
Meetings
Collaboration
Collaboratio
n
Collaboration
Content
53. What are the key differences between Site template and site definition?
Site Definitions
Site Templates
2.
3.
Breadcrumb navigation
Metadata navigation
Navigation controls on page layouts
Summary Links
Table of Contents
Content Query
Navigation Web Parts
Categories
Site Aggregator
Site in Category
Tag Cloud
The following navigation Web parts are available only on Publishing sites:
Summary Links
Table of Contents
59. What is Ribbon interface?
Ribbon Interface act as the UI enhancement in the product. It provides the commands to be executed
in the form of Icons and tabs.
A site content type becomes available to lists and document libraries within the site in which the
content type is created and to the lists and document libraries in any child site.
86. What is an ancestral type and what does it have to do with content types?
An ancestral type is the base type that the content type is deriving from, such as Document (0x0101).
The ancestral type will define the metadata fields that are included with the custom content type.
87. Can a list definition be derived from a custom content type?
Yes, a list definition can derive from a content type, which can be seen in the schema.XML of the list
definition in the element.
88. When creating a list definition, how can a user create an instance of the list?
User can create a new instance of a list by creating an instance.XML file
89. What is ghosted page?
A ghosted page is a page in SharePoint website which is not stored in the database instead it
reference to a file which exists in the servers file system. These reference files are common for all the
website/site collection within that SharePoint server, i.e., if user modify a reference file then that
change will reflect in all the websites/site collections within that SharePoint server automatically.
90. What is Un-ghosted page?
All the pages in a SharePoint website, which are stored in the content database, are referred to as unghosted pages. All the un-ghosted pages are specific to that SharePoint website only, i.e., changes
done in an un-ghosted page will not reflect in other websites within that SharePoint server.
91. What are the types of pages available in SharePoint 2010?
There are two types of pages that are available in SharePoint, which are as follows:
1- Application page.
2- Site page.
92. What are application pages?
An application page is the best type of page to create, when there is need to add custom code.
Application pages are stored on the file system of the front-end Web server in the %Program
Files\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\LAYOUTS directory. They
allow in-line code without restriction. They cannot use dynamic Web Parts or Web Part zones or be
modified using SharePoint Designer. Application pages are not tracked in the content database. They
never run in safe mode. Since application pages must be deployed inside the SharePoint Root
directory hence, they cannot be used within sandboxed solutions.
93. When to use application pages?
1. These are generally used as administrative pages.
2. These pages can be used where we want to capture data.
3. These pages can be used for configuration pages.
4. These pages can be used where we want to restrict the users to customize the page.
5. Application pages can be used with any site or site collection or web application on same server.
6. These pages are used when we want to add custom code or inline code to the page.
94. List the folders and files added while creating an application page?
When developer creates an application page, Visual Studio adds the following folders to the project:
Folder
Description
Layouts
Layouts
subfolder
Contains the files that make up the application page. By default, this folder has the
same name as project. This folder can be renamed at any time. At the time of
running of the project, Visual Studio deploys this folder to the _layouts virtual
directory of the SharePoint file system.
File
Description
95. What is the difference between Site page and application page?
S. No
Site Pages
Application Pages
96. Can web parts and web zones be added to an Application page?
No, since Application pages does not support edit mode so web part zones and web parts cannot be
added using SharePoint. However, static web parts can be added by editing then in Visual Studio, as
web parts are nothing but controls with some extra functionality.
97. How to edit an Application page?
An application page can only be edited either by opening the page in Visual Studio or in Notepad.
However, in both the ways, the application page needs to be deployed again for further usage.
98. What is difference between an Application page and a Custom aspx page in SharePoint 2010?
Application Page Developer would typically use an application page when developer need some
content that is merged with SharePoint master page. A master page enables application pages to
share the same appearance and behavior as other pages on a site. Application page generally is
deployed in _layouts and inherits the look and feel of the site that developer is using.
A Custom .net aspx page on the other hand would need content and master page tags in the page to
make it inherit the look and feel of the site.
99. If a page with some code has to be deployed, which type of page should be selected?
Developer must select to deploy an application page with code as it is much easier and built-in
templates are available in VS 2010.
files that a solution needs, such as content types, Web Parts, lists, and site definitions, master page.
Inside the Feature, the feature.xml file contains references to all the element manifests within that
Feature, pluggable behavior for installing or uninstalling Features within a deployment, pluggable
behavior for activating or deactivating Features at a given scope, scoped property bag for storing data
required by a Feature within its scope.
129.What is the scope of feature activation?
Feature can be activated or deactivated at various scopes throughout a SharePoint instances, such as
farm level, web application level, site collection level, web level, etc.
130.What is the difference between feature definition and feature instance?
The feature definition is the set of source files in the Visual Studio 2010 project that is deployed using
a solution package. Once deployed, a feature definition is a set of template files and components that
reside on each front-end Web server. A feature instance is what is created when a user activates the
feature definition.
131.What are the minimum files required for a feature?
Every feature directory should contain at least one file namely feature.xml and should be placed in
the root of the directory. But a feature directory can contain one or more xml files as well as resource
files such as image files, css files or js files. A feature.xml file contains attributes like Id, Title,
Description, Version, Scope, Hidden, and ImageURL.
132.What is hidden attribute in a feature?
Hidden attribute will take the value of True or False. If it is set to False, after installation the feature
definition can be seen by administrators only.
133.What is Elements.xml file in Feature in SharePoint 2010?
Elements.xml file contains the actual feature element. It can contain elements like ListInstance, Field,
ContentType, ListTemplate, Workflow, WorkflowActions etc.
134. What is Feature Receiver in SharePoint 2010, its base class along with the methods that needs to
be override?
A Feature Receiver allows user to write event handlers in a managed programming language such as
C# or Visual Basic. These event handlers are executed during feature specific events such as feature
activation and feature deactivation. The base class is SPFeatureReceiver. The methods to be
overridden are: FeatureActivating, FeatureActivated, FeatureDeactivating,FeatureDeactivated etc.
135.How are features created?
Feature can be created by creating a new Empty SharePoint project from VS 2010 and then add new
item named feature. After user has created the project, right click on the "Features" node in "solution
explorer" and "add feature". This will create a new feature with the title "Feature1". User can rename
it or leave it as it is. On double clicking the name of the feature, the properties of the feature will
appear, such as title, description and the scope. Right click on the "feature1" in solution explorer and
click on "Add feature Receiver" to add it. After the file has been created, uncomment (as required)
the "on activate" and/or on deactivate" and put code in there.
136.How can a feature be deployed?
There are two ways for deploying a feature
1- WSP builder via Visual Studio and activate solution from central admin.
2- Using STS Command, firstly install and then activate.
137.Where the feature receiver file needs to be deployed?
The feature receiver file needs to be deployed in Global Assembly cache (GAC).
138.What is a Manifest.xml File in SharePoint 2010?
Manifest.xml file contains the Meta data of a solution package. At the time of deployment, SharePoint
inspects manifest.xml file to determine which template files it needs to copy into the SharePoint root
directory.
139.Can a page be displayed as a modal dialog?
Yes, any page can be displayed as modal dialog. A Modal dialog takes options as a parameter and
developer can specify the URL for any page usually saved in _layouts.
140.What is New in SPALerts?
In SharePoint 2007, alerts were sent only through e-mails, but in SharePoint 2010, users can also send
an alert to mobile devices as SMS Message. A New property DeliveryChannels is introduced to
indicate, whether the alert is delivered as E-mail or as an SMS Message.
13. The page class is compiled into a .NET assembly and cached on the disk.
14. An instance of the requested pages class is created.
15. The response is generated from the requested page class is sent back to the original caller.
145.What is the difference between 32-bit hardware and 64-bit hardware and software?
The terms 32-bit and 64-bit refer to the way a computer's processor (also called a CPU), handles
information. The 64-bit version of Windows handles just double amounts of data from a 32-bit
system.
146.What is a SharePoint Farm?
A SharePoint farm is a set of one or more server computers working together to provide SharePoint
functionality to clients in terms of executing SharePoint project or solution.
147.How to install or deploy SharePoint 2010?
SharePoint installation/deployment scenarios can be classified as:
1.
Standalone Installation: Most of the small companies prefer standalone installation scenario.
This scenario enables user to install, SharePoint and SQL database on one physical server.
2.
Server Farm Installation: Most of the mid or large size, companies prefer farm installation
scenario. The server farm installation can be performed as:
Complete Installation: Add all the components with ability to add more as per need
Standalone : Install all the components on single server[web server/application
server/database server]
Minimum requirement
Processor
RAM
Hard disk
Minimum Requirement
Database server in
a farm
Minimum Requirement
Front-end
Web
servers
and
application servers
in a farm
Client computer
A supported browser
151.What does the preparation tool installs before installing SharePoint 2010?
The preparation tool installs the following prerequisites:
Web Server (IIS) role
Application Server role
Microsoft .NET Framework version 3.5 SP1
SQL Server 2008 Express with SP1
Microsoft Sync Framework Runtime v1.0 (x64)
Microsoft Filter Pack 2.0
Microsoft Chart Controls for the Microsoft .NET Framework 3.5
Windows PowerShell 2.0
SQL Server 2008 Native Client
Microsoft SQL Server 2008 Analysis Services ADOMD.NET
ADO.NET Data Services Update for .NET Framework 3.5 SP1
A hotfix for the .NET Framework 3.5 SP1
Windows Identity Foundation (WIF)
152.What is the directory structure created during SharePoint installation?
The directory created while installing SharePoint 2010 is
C:\Program Files\Common Files\Microsoft Shared\web server extension\14
1. ADMISAPI
2. BIN
3. CONFIG
4. HCCab
5. Help
6. ISAPI
7. LOGS
8. Policy
9. Resources
10. TEMPLATE Sub Directories (1033, Admin, FEATURES, LAYOUTS, IMAGES, PAGES, Themes, SQL,
XML, ControlTemplates, Document templates, IDENTITYMODEL, Site Template, GLOBAL).
11. UserCode
12. WebClients
13. WebServices
153.What has Changed in SharePoint 2010 Object model?
Microsoft has replaced the 12 hive structure that we had in SharePoint 2007 with 14 Hive
structure in 2010. It has apparently added four new folders to its hive.
The Folders are:
1. Policy
2. UserCode
3. WebClients
4. WebServices
154.List all the databases created at the time of installing SharePoint?
1. Secure Store database - The Secure Store service application database stores and maps
credentials, such as account names and passwords. Prefixed with "Secure_Store_Service_DB_".
2. State database - The State service application database stores temporary state information for
InfoPath Forms Services, the chart Web Part, and Visio Services. Prefixed with "StateService".
3. Web Analytics Staging database - The Staging database temporarily stores un-aggregated fact
data, asset metadata, and queued batch data for the Web Analytics service application. Prefixed
with "WebAnalyticsServiceApplication_StagingDB_"
4. Web Analytics Reporting database - The Reporting database stores aggregated standard report
tables, fact data aggregated by groups of sites, date and asset metadata, and diagnostics
information
for
the
Web
Analytics
service
application.
Prefixed
with
"WebAnalyticsServiceApplication_ReportingDB_"
5. Search service application Administration database - The Administration database hosts the
Search service application configuration and access control list (ACL), and best bets for the crawl
component. This database is accessed for every user and administrative action. Prefixed with
"Search_Service_Application_DB_".
6. Search service application Crawl database - The Crawl database stores the state of the crawled
data and the crawl history. Prefixed with "Search_Service_Application_CrawlStoreDB_'.
7. Search service application Property database - The Property database stores information that is
associated with the crawled data, including properties, history, and crawl queues. Prefixed with
"Search_Service_Application_PropertyStoreDB_"
8. User Profile service application Profile database - The Profile database stores and manages users
and associated information. It also stores information about a user's social network in addition to
memberships in distribution lists and sites. Prefixed with "User Profile Service
Application_ProfileDB_".
9. User Profile service application Synchronization database -The Synchronization database stores
configuration and staging data for use when profile data is being synchronized with directory
services such as Active Directory Prefixed with "User Profile Service Application_SyncDB_".
10. User Profile service application Social Tagging database - The Social Tagging database stores
social tags and notes created by users, along with their respective URLs. Prefixed with "User
Profile Service Application_SocialDB_".
11. Managed Metadata database - The Managed Metadata service application database stores
managed
metadata
and
syndicated
content
types.
Prefixed
with
"
Managed Metadata Service_".
Enterprise edition installation adds two more databases:
1. Performance Point service application database - The Performance Point service application
database stores temporary objects, persisted filter values, and user comments. Name Prefix
"PerformancePointServiceApplication_.
2.
Word Automation Services database - The Word Automation Services database stores
information about pending and completed document conversions.Name Prefix
"WordAutomationServices_..."
Category
Content roll up
document
filters
My information
Office Client
Navigation
People
Performance Point
Search
Miscellaneous
2- Microsoft Visio.
3- SharePoint Designer.
162.What are the various types of workflow in SharePoint?
These are of two types namely:
1. Declarative Workflow: is a workflow that is built from conditions and actions that are assembled
into rules and steps, and that sets the parameters for the workflow without writing any code.
2. Compiled Workflow: is a workflow that can be built from conditions and actions, in addition it
allows custom code to be written inside them unlike Declarative workflows.
163.What is different with SharePoint 2010 workflows?
Some of the additions in workflow model are:
1. SharePoint 2010 workflows are build upon the workflow engine provide .Net Framework 3.5.
2. In addition to the SharePoint lists, workflows can also be created for SharePoint sites.
3. SharePoint Designer 2010 also has a new graphical workflow designer for designing workflows
and deploying them directly to SharePoint.
4. Another Improvement in SharePoint Designer 2010 is that it now allows editing the out-of-thebox workflows that comes with SharePoint.
164.What are Reusable List Workflows and Site workflows?
1. Reusable List Workflows - User can create a reusable list workflow (reusable workflow) in the
top-level site in the site collection, and that workflow can be made globally reusable meaning
that the workflow can be associated to any list, library, or content type in the site collection. User
can also create a reusable workflow in any subsite in the site collection; this workflow is available
for reuse in that particular subsite.
2. Site workflows - A site workflow is associated to a site not to a list, library, or content type.
Therefore, unlike most workflows, a site workflow is not running on a specific list item. Because
of this, many of the actions that is available for items not available for site workflows.
165.How can a workflow be debugged?
1. visual studio debugging add w3wp.exe process
2. Visio workflow cannot be debugged.
3. SharePoint Designer offers no custom debugging functionality; user can write information at
various stages to history and view the content to debug.
166.What are the various types of in-built workflows in SharePoint 2010?
Microsoft SharePoint Server 2010 includes the following predefined workflow templates that address
common business scenarios:
1. Collect Feedback: This Workflow routes a document or item to a group of people for feedback.
Reviewers can provide feedback, which is then compiled and sent to the person who initiated the
workflow. By default, the Collect Feedback workflow is associated with the Document content
type, and therefore it is automatically available in document libraries.
2. Approval: This Workflow routes a document or item to a group of people for approval. By
default, the Approval workflow is associated with the Document content type, and therefore it is
automatically available in document libraries. A version of the Approval workflow is also
associated by default with the Pages library on a publishing site, and can be used to manage the
approval process for the publication of Web pages. The Approval workflow is a staged approval
model (that is, the first set of approvers can undergo the review and approval process, then the
next set of approvers, and so on). Each stage or approval set can also have its own behavior. For
example, members of the first group of approvers can do their review in serial approval order
(one after the other), members of the second group can do their review in parallel, and so on.
3. Disposition Approval: This Workflow manages document expiration and retention by letting
participants to decide whether to keep or delete expired documents. The Disposition Approval
workflow supports record management processes and is intended for use primarily in a Records
Center site.
4. Collect Signatures: This Workflow routes a document that was created in a Microsoft application
to a group of people to collect their digital signatures. By default, the Collect Signatures workflow
5.
6.
7.
is associated with the Document content type, and therefore is automatically available in
document libraries. However, the Collect Signatures workflow appears for a document in the
document library only if that document contains one or more Microsoft Office Signature Lines.
Three-state: This Workflow is designed to track the status of a list item through three states
(phases). It can be used to manage business processes that require organizations to track a high
volume of issues or items, such as customer support issues, sales leads, or project tasks. The
Three-state workflow is so named because it tracks the status of an issue or item through three
different states, and through two transitions between the states. For example, when a workflow
is initiated on an issue in an Issues list, SharePoint Server 2010 creates a task for the assigned
user. When the user completes the task, the workflow changes from its initial state (Active) to its
middle state (Resolved) and creates a task for the assigned user. When the user completes the
task, the workflow changes from its middle state (Resolved) to its final state (Closed), and creates
another task for the user to whom the workflow is assigned at that time. This workflow is only
supported on lists, not libraries.
Translation Management: This Workflow manages manual document translation by creating
copies of the document to be translated and by assigning translation tasks to translators. This
workflow is available only for Translation Management libraries.
Issue Tracking: This Workflow routes an issue to team members for resolution. It presents a Web
page to the user who makes possible the entry of new issues. For example, customer complaints.
As an issue progresses though different workflow states, the Web page of the user changes to
reflect appropriate events. For example, a Web page that was closed when an issue is resolved.
171.What are the key areas in which Governance model should be applied?
The key areas in which governance model should be applied are:
1. IT governance - regulation over hardware, software, security, infrastructure, backup and
recovery, Multitenancy, Windows PowerShell as well as the services provided;
2. Information Architecture - design and administration of information life cycles, content types,
metadata, taxonomy, workflow, navigation and site structure, Document library, lists, web pages
and data.
3. Customization Policy - administration and control of custom solutions built on top of or
integrated within the SharePoint environment. Customization introduces risks to the stability,
maintenance, and security of the SharePoint Server 2010 environment.
4. Branding - A formal set of branding policies helps ensure that sites consistently use enterprise
imagery, fonts, themes, and other design elements.
172.What are the various permission levels in SharePoint?
Eight major Permission level in SharePoint are
1- Full Control
2- Design
3- Contribute
4- Read
5- Limited Access
6- Restricted Read
7- Approve
8- Manage Hierarchy
173.What permissions developer must have to install a webpart or any custom solution in SharePoint
2010 using PowerShell?
In order to use Windows PowerShell for SharePoint 2010 Products, a user must be a member of the
SharePoint_Shell_Access role on the configuration and content database. In addition to this, the user
must also be a member of the WSS_ADMIN_WPG local group on the computer where SharePoint
2010 Products is installed.
174.What is Service application framework?
Service application framework provides a platform that allows developers to build scalable middletier applications.
175.What is SOA?
SOA can be termed as A service-oriented architecture is essentially a collection of services. These
services communicate with each other. The communication can involve either simple data passing or
it could involve two or more services coordinating some activity. Some means of connecting services
to each other is needed. It can also be stated as rather than developing software as a monolithic,
inseparable, intertwined, chunk of code, System design is comprised of autonomous services each
providing some discrete function and/or access to data. These services are usually implemented in
the form of Web Services, which come in many flavors including SOAP, REST, XML over HTTP, etc.
176.What are the benefits of SOA?
SOA benefits include:
1. Reuse once the service is written it can be plugged in wherever needed versus writing the same
application repeatedly every time/place user need it.
2. Consistency the service executes the same way every time so, for example, calculations such as
APR (a tricky calculation for mortgages and one that has to be correct per compliance guidelines)
and underwriting decisions are consistent across applications that consume the service.
3.
Scalability & Reliability - Because the services run in a web server environment, they can take
advantage of load balancing and fault tolerance technologies to provide scalability and reliability.
4.
Rapid development several services can be combined very rapidly to create robust applications
without having to write anything but the code necessary to glue them together
5.
Integration access to line of business systems data and functionality becomes trivial if these
systems are fronted by services.
Description
New service that allows for viewing, editing and interacting with MS
Access through a browser.
Enables users to search and collaborate around business data.
Provides backward compatibility to BDC service.
Access to line of business systems. Service now supports writing to
data services.
Central Admin Site
Schedules and initiates document conversions.
Balances document conversions across the SharePoint farm.
Ability to interact with Excel files in a browser. New extended
functionality.
Index service connector to index Lotus Notes Domino Servers.
Supports hosting InfoPath forms in SharePoint.
New service that manages taxonomy structures and definitions.
Email service. This will run on the machine where the web
application is running.
New service used to track subscription IDs and settings for services
that deployed in partition mode.
New service runs code deployed as part of a sandbox solution and
runs in restricted mode. Must be started on any machine in the farm
that needs to run Sandbox code.
The service that runs the web application.
Responsible for running timer jobs.
BI Dashboard services.
New services that allows viewing, editing and broadcasting
PowerPoint in a browser.
Service that performs a query across built indexes.
Service provide SSO authentication.
Service that provides search capabilities for SharePoint Foundation
Search only. For SharePoint Server 2010 Standard and Enterprise
this service will perform online Help search.
Crawls content, creates indexes and performs queries. Automatically
configured.
New services that provides temporary storage of user session data
for SharePoint components.
Reporting services that provide farm wide usage and health.
New and expanded social networking services and features.
Synchronizes user and group profile information that is stored in the
SharePoint Server 2010 profile store with profile information that is
stored in directory services across the enterprise. Works with AD,
BDC, Novel LDAP and Sun LDAP .
Ability to view published Visio diagrams in a browser.
Web
Analytics
Data
Processing Service
Web Analytics Web Service
Word Automation Services
Maximum value
1.
Content database
2.
Zone
3.
Managed path
4.
Maximum value
5.
Application pools
Web site
Maximum value
2 GB
13. Documents
400000
15. Items
6 table rows internal to the database used for a list or library item
5000
20000
21. Subsite
22. Coauthoring in
Microsoft Word and
Microsoft PowerPoint for
.docx, .pptx and .ppsx files
Column Limit
Maximum value
276
192
26. Choice
276
27. Number
72
28. Currency
72
48
30. Lookup
96
31. Yes / No
96
96
138
34. Calculated
48
35. GUID
36. Int
96
94
Page Limit
Maximum value
Security Limit
Maximum value
5,000
2 million per site collection
5,000 per SharePoint group
10,000 per site collection
5,000 per Access Control List (ACL)
Maximum value
20 per farm
10 crawl databases per search service application 25 million items per
crawl database
100 million per search service application; 10 million per index partition
100 scope rules per scope; 600 total per search service application
53. Scopes
200 site scopes and 200 shared scopes per search service application
25 per site
55. Alerts
100
63. Mappings
1 top level and minimal second and third level pages per search service
application
66. Keywords
recognized
User Profile Service
Limit
Maximum value
Content Limit
70. Content deployment
jobs running on different
paths
20
Blog Limit
Maximum value
72. Comments
Business Connectivity
Services Limit
Maximum value
73.
ECT (in-memory)
85. Cells
512 MB
1 minute (recommended)
For PDF/XPS output formats: 30 x MFor all other output formats: 72 x
M Where M is the value of Frequency with which to start conversions
(minutes)
Maximum value
100 GB
103. Renders
One per document per second per CPU core per application server
(maximum eight cores)
Maximum value
Date: 12/31/2049
1500 deliverables
256
40
The series SharePoint 2010 JumpStart by Vishal Gupta comprise 21 eBooks. These eBooks are written in
simple language covering all the aspects of SharePoint 2010 and are based on practical scenarios with real life
day-to-day examples.
Being an architect for mission critical large-scale projects, I am exploring SharePoint for past eight years, and
Microsoft technologies for near about 15 yrs. My focus is to relate the technology with real life problems in
simplistic manner. The eBooks appraises more towards practical approach and issues faced while doing
customizations, development and deployment of the SharePoint.
These eBooks can be read and purchased individually by experts as per need, while novice users can purchase
them sequentially to become SharePoint 2010 expert.
This eBook in series contains the details about what is SharePoint 2010.
o 1.1What is SharePoint?
o 1.2 History of SharePoint
o 1.3 CMS, DMS & RMS
o
o
o
o
o
o
o
This eBook in series contains the details about the architecture of SharePoint 2010.
o 2.1 Architecture Concepts
o 2.1.1 Software Application Architecture
o 2.1.2 Topology
o 2.1.3 Server and Web service
o 2.1.4 Web server [IIS]
o 2.1.4.1 Elements of IIS
o 2.1.4.2 Modules of IIS
o 2.1.4.3 Authentication modes of IIS
o 2.1.4.4 IIS site creation and deployment
o 2.2 SharePoint Architecture
o 2.3 SharePoint Interaction
o 2.3.1 SharePoint IIS Interaction
o 2.3.2 Difference in User Request Processing in .Net vs SharePoint
o 2.3.3 Physical folder structure
o 2.3.4 SharePoint Logical Directory Structure
o 2.3.5 SharePoint SQL Interaction
3 - SharePoint 2010
[vguptadelhi@gmail.com]
Installation
&
Configuration
Vishal
Gupta
This eBook in series contains the details about step-by-step installation and configuration of
SharePoint 2010.
o 3.1 Hardware and Software recommendations
o 3.1.1 Hardware Requirements
o 3.1.2 Software Requirements
o 3.2. Browser Support
o 3.3. IP Support
o 3.4 SharePoint Standalone Installation
o 3.5 SharePoint Server Farm installation
o 3.5.1 Server Roles
o 3.5.2 Server Topology
o 3.5.3 Server Farm Complete Installation
o 3.6 SharePoint Foundation Installation
o 3.7 Difference in various installation Scenarios
o 3.8 SharePoint server installation scenarios
o 3.9 SharePoint server installation Error
This eBook in series contains the details about the Creation and Site Management in SharePoint
2010.
o 4.1 SharePoint Look & Feel
o 4.2 SharePoint Central Administration
o 4.3 SharePoint Web Application
o 4.3.1 Create a new Web application
o 4.3.2 Extend an existing Web application
o 4.4 Site Collection
o 4.5 Site Actions
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
This eBook in series contains the details about the common operations being performed on basic
elements of SharePoint 2010.
o 5.1 Check out/Check in
o 5.1.1 Check out
o 5.1.2 Check in
o 5.1.3 Discard Check out
o 5.2 Versioning
o 5.3 Column creation
o 5.3.1 Scope of column
o 5.3.2 Creating a column
o 5.4 Content creation
o 5.4.1 Creating a Content type
o 5.5 Validation settings
o 5.5.1 Column level validation
o 5.5.2 List level validation
o 5.6 Rating settings
o 5.7 Audience targeting settings
o 5.8 Views
o 5.8.1 Advantages of Views
o 5.8.2 Types of views
o 5.8.3 Create a view
o 5.8.4 Work with mobile views
o 5.9 Scenario
This eBook in series contains the details about the out of the box elements - I provided by
SharePoint 2010.
o 6.1 List
o 6.1.1 Types of List
o 6.1.2 Creating a List
o 6.1.3 Creating a custom list
o 6.1.4 Add item in a list
o 6.1.5 Delete item from list
o 6.1.6 Edit item in a list
o 6.1.6 Add column in a list
o 6.1.7 Limitations of Lists
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
This eBook in series contains details about the out of the box elements - II provided by SharePoint
2010.
o 7.1 Content Editor Web part
o 7.1.1 Ways to add content to the content editor web part
o 7.1.2 Creation of Content editor web part
o 7.2 Image viewer web part
o 7.2.1 Ways to display an image in image web part
o 7.2.2 Creation of image web part
o 7.3 Announcement
o 7.3.1 Creation of announcement web part
o 7.3.2 Add announcements to a web part
o 7.4 Issue tracking
o 7.4.1 Creation of issue tracking
o 7.4.2 Add Items
o 7.5 Chart web part (CWP)
o 7.5.1 Creation of chart web part
o 7.6 Excel web access web part
o 7.6.1 Add an excel web access web part to a page
o 7.7 RSS viewer
o 7.7.1 Add RSS viewer web part to a page
o 7.8 Web analytics
o 7.8.1 Add web analytics web part to a page.
o 7.9 XML viewer
o 7.9.1 Add XML viewer to a page
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
This eBook in series contains the details about how to provide similar look and feel to portal
created using SharePoint 2010.
o 8.1 Branding in SharePoint
o 8.2 Pages in SharePoint
o 8.2.1 Site Pages
o 8.2.1.1 Use of Site Pages
o 8.2.1.2 Creation of Site pages
o 8.2.1.3 Scenarios for using Site pages
o 8.2.1.4 Drawbacks of using Site pages
o 8.2.2 Application Pages
o 8.2.2.1 Use of Application pages
o 8.2.2.2 Creating Application pages
o 8.2.2.3 Scenarios for using Application pages
o 8.2.2.4 Drawbacks of Application pages
o 8.2.2.5 Difference in Application pages vs. Site Pages
o 8.2.3 Master Pages
o 8.2.3.1 Benefits of using Master Pages
o 8.2.3.2 Master Pages Available in SharePoint 2010
o 8.2.3.3 Customize a master page to brand your site
o 8.2.3.4 FAQs related to Master Pages
o 8.3 CSS in SharePoint
o 8.3.1 How to use CSS
o 8.3.2 Benefits of using CSS
o 8.3.3 FAQs related to CSS
o 8.4 Site Definition in SharePoint
o 8.4.1 Files in Site Definition
o 8.4.2 Create Site Definition
o 8.4.3 Use of Site Definition
o 8.4.4 When to use Site Definition
o 8.5 Template in SharePoint
o 8.5.1 Various Site Templates Available in SharePoint 2010
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
More to Come
9 - SharePoint 2010 Workflows and Deployment - Vishal Gupta [vguptadelhi@gmail.com]
10 - SharePoint 2010 Governance Model - Vishal Gupta [vguptadelhi@gmail.com]
11 - SharePoint 2010 Information Architecture - Vishal Gupta [vguptadelhi@gmail.com]
12 - SharePoint 2010 Capacity Planning & Limitations - Vishal Gupta [vguptadelhi@gmail.com]
13 - SharePoint 2010 Customization using SharePoint 2010 Designer - Vishal Gupta [vguptadelhi@gmail.com]
14 - SharePoint 2010 Customization using InfoPath 2010 - Vishal Gupta [vguptadelhi@gmail.com]
15 - SharePoint 2010 Customization using Visual Studio - Vishal Gupta [vguptadelhi@gmail.com]
16 - SharePoint 2010 Service Oriented Architecture - Vishal Gupta [vguptadelhi@gmail.com]
17 - SharePoint 2010 Administration - Vishal Gupta [vguptadelhi@gmail.com]
18 - SharePoint 2010 Document & Record Management - Vishal Gupta [vguptadelhi@gmail.com]
19 - SharePoint 2010 Migration - Vishal Gupta [vguptadelhi@gmail.com]
20 - SharePoint 2010 Performance Management - Vishal Gupta [vguptadelhi@gmail.com]
21 - SharePoint 2010 Case Studies - Vishal Gupta [vguptadelhi@gmail.com]
------Thanks All----