Hi Readers, I have taken reference from google to collect SharePoint
related interview questions from different places and write them in one place to make it easy for you all.
Q. What has Changed in SharePoint 2010 Object model?
Ans. 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 :
* Policy
* UserCode
* WebClients
* WebServices
Q. How would you deploy WebPart Using Windows PowerShell?
Ans. At the Windows PowerShell command prompt (PS C:\>), type the below command :
Install -SPWebPartPack -LiteralPath “FullPathofCabFile” -Name “Nameof WebPart”
Q. How would you re-deploy the old custom solutions in SharePoint 2010.What Changes are needed to the old Solution files.
Ans. SharePoint
2010 object model contains many changes and enhancements, but our
custom code will still compile and, will run as expected. You should
however, rewrite and recompile any code that refers to files and
resources in “12 hive”.
For Details See :
SharePoint Object Model – Backward Compatibility
Q. How would you add a link in the Ribbon?
Ans. You
can add any link or Custom Action under any of the existing tabs of the
ribbon or can create a new a new tab and place your links under it.
Q. What does CMDUI.XML contain?
Ans. The
definitions for the out-of-the-box ribbon elements are split across
several files in the SharePoint root, with TEMPLATE\GLOBAL\XML\CMDUI.XML
being the main one.
Q. What are the Disadvantages of Using LINQ in your Code?
Ans. LINQ
translates the LINQ queries into Collaborative Application Markup
Language (CAML) queries thus adding an extra step for retrieving the
items.
Q. What is different with SharePoint 2010 workflows ?
Ans. Some of the additions in workflow model are :
1. SharePoint 2010 workflows are build upon the the workflow engine provide .Net Framework 3.5.
2. In addition to the SharePoint lists we can now create workflows for SharePoint sites as well.
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
you to edit the out-of-the-box workflows that come with SharePoint.
Q. What is SharePoint 2010?
Def : SharePoint 2010 is the business
collaboration platform for the Enterprise & the Web that enables you
to connect & empower people through an integrated set of rich
features. Whether deployed on-premises or as hosted services, SharePoint
2010 helps you cut costs with a unified infrastructure while allowing
you to rapidly respond to your business needs.
Q. What Has Changed with 12 hive in SharePoint?
Ans. Three New Folders have been added in 12 hive structure.
• UserCode – files used to support sandboxed solutions .
• WebClients – used for the client Object Model.
• WebServices – .svc files .
Q. How would you re-deploy the old custom solutions in SharePoint 2010.What Changes are needed to the old Solution files.
Ans. SharePoint 2010 object model
contains many changes and enhancements, but our custom code will still
compile and, will run as expected. You should however, rewrite and
recompile any code that refers to files and resources in "12 hive".
Q. Whats New with SharePoint WebParts?
A developer can create two types of webparts using Visual Studio 2010.
1. Visual Webparts -
Allows you to Drag and Drop the controls from the Toolbox to WebPart
Design surface. You can of course write your custom code in the code
file. You can also package and deploy your webparts directly to
Sharepoint from VS by pressing Clt+F5. Visual studio 2010 also provides
you with three different views for developing webparts. The views are
split view, design view and Source view(as we have in designer 2007).
Note : The Visual Webpart project Item basically loads a User Control as a WebPart.
2. ASP.Net WebParts -
Where a developer can build up User Interface and logic in a class
file. You do not have designer for drag and drop of controls. This
webpart inherits from standard ASP.Net webpart. For Deployment we can
again use ctrl+f5 to deploy this webpart.
Q. What are the Visual Studio 2010 Tools for SharePoint.
Ans. Visual Studio 2010 includes
SharePoint-specific project types and project item types, and includes
powerful packaging, deployment, and debugging features that help
increase your efficiency as a SharePoint 2010 developer.
Some of the Templates avaiable are :
1.Visual Web Part project template.
2. List defination template.
3. Content Type template.
4. Empty Project template.
5. Event Receiver template.
6. some workflow template.
7. the Site Definition template
and many more....
Q. What are SharePoint Sandboxed soultions ?
Ans. SharePoint 2010 provides a new
sandboxed environment that enables you to run user solutions without
affecting the rest of the SharePoint farm. This environment means that
users can upload their own custom solutions without requiring
intervention from administrators, and without putting the rest of the
farm at risk. This means that the existing sites\pages or components
will not be effected by the newly added soultion.
Users can deploy the below four things as sandboxed soultions :
1. WebParts.
2. Event Receivers.
3. List Definations.
4. Workflows.
Q. What are Requirenments for SharePoint 2010.
Ans. SharePoint Server 2010 will support
only 64 - bit. It will require 64 bit Windows Server 2008 or 64 bit
Windows Server 2008 R2. In addition to this, it will require 64 bit
version of SQL Server 2008 or 64-bit version of SQL Server 2005.
Q. What is LINQ. How is it used in Sharepoint ?
Ans. LINQ is a feature of the programming
languages C# 3.0 and Visual Basic .NET. LINQ allows you to query in an
object-oriented way, supports compile-time check, gives you intellisense
support in Visual Studio and defines a unified, SQL like syntax to
query any data source. But unlike other languages and query syntaxes
which vary from one type of data source to another, LINQ can be used to
query, in principle, any data source whatsoever. Hence, developers may
find that it is the only query syntax that they ever need to know. It is
commonly used to query objects collections, XML and SQL server data
sources.
LINQ to SharePoint is officially being supported with the 2010 release.It works similar to LINQ to SQL or LINQ to Entity.
The LINQ to SharePoint Provider is
defined in the Microsoft.SharePoint.Linq namespace. It translates LINQ
queries into Collaborative Application Markup Language (CAML)
queries.The gateway class for the LINQ to SharePoint provider is
Microsoft.SharePoint.Linq.DataContext which represents the data of a
SharePoint Foundation Web site.
Q. What are the Hardware and Software requirements for SharePoint 2010.
Ans.
Hardware requirements :
# Processor 64-bit, four-core, 2.5 GHz minimum per core.
# RAM 4 GB for developer or evaluation use, 8 GB for single server and multiple server farm installation for production use.
# Hard disk 80 GB for installation
For production use, you need additional
free disk space for day-to-day operations. Add twice as much free space
as you have RAM for production environments.
Software requirements :
# The 64-bit edition of Windows Server
2008 Standard with SP2. If you are running Windows Server 2008 without
SP2, the Microsoft SharePoint Products and Technologies 2010 Preparation
Tool installs Windows Server 2008 SP2 automatically.
Q. What Has Changed with SSP in SharePoint 2010.
Ans. In SharePoint 2010 Shared Service
Providers (SSP's) are replaced by Service Applications. Services are no
longer combined into a SSP. They are running independent as a service
application. The service application architecture is now also built into
Microsoft SharePoint Foundation 2010, in contrast to the Shared
Services Provider (SSP) architecture that was only part of Office
SharePoint Server 2007.
A key benefit here is that all services are installed by default and there is no SSP setup.
Additional improvements for the service application model include:
• The services architecture is extensible, allowing third-party companies to build and add services to the platform.
• Services are managed directly in Central Administration (rather than a separate administration site).
• Services can be monitored and managed remotely.
• Services can be managed and scripted by Windows PowerShell™.
• Shared services communications take place over HTTP(S). Shared services do not directly access databases across farms.
• Most new services are built on the
Windows Communications Framework. They have optimization built into
their protocol, using binary streams instead of XML for data transfer.
Test results show improvements in network throughput with this change.
Q. What are the advantages of Service Applications over SSP ?
Ans. The key limitation of the SSP
architecture was that it was configured by using a set of services, and
all Web applications associated with the SSP bore the overhead of all
the services even if they weren’t being used. To change the service
configuration for a particular Web application, a new SSP would have to
be created.
The service application architecture on
the other hand, allows a set of services to be associated with a given
Web application and a different set of services to be associated with
another Web application. Also, the same service application can be
configured differently in different Web applications; therefore, Web
sites can be configured to use only the services that are needed, rather
than the entire bank of services.
Q. Can we create a Single set of Services that will be shared across the farm?
Ans. Similar to the SSP model in Office
SharePoint Server 2007, a single set of services can be shared by all
sites in a farm. By publishing a service application (from the sharing
group, under Service application tab), you can share it across server
farms. This capability does not apply to all service applications, and
some services can be shared only within a single server farm.
Q. What are Managed Accounts?
Ans. To reduce the load of managing
various service accounts in Microsoft SharePoint Server 2010, the
concept of managed accounts has been introduced. Much like managed
accounts in Windows Server 2008, they allow SharePoint Server to take
control of all the service accounts you use. After SharePoint Server has
control of these accounts, it can either manage their passwords —
automatically changing them as necessary — or it can notify you when an
accounts password is about to expire, allowing you to make the change
yourself.
Q. What are the Methods of Backup and Recovery in SharePoint 2010?
Ans. Microsoft SharePoint Server 2010
provides a broad range of levels for performing backups, including the
entire farm, farm configuration information, site collections, subsites,
or lists.
SharePoint Server 2010 uses two different tools to configure backup and recovery.
1. Central Administration : Central
Administration provides a user interface where SharePoint Administrators
will be prompted via menu structures to select the information that
needs to be backed up. (see the Image below)
2. Windows PowerShell : Windows
PowerShell is a command line tool that provides SharePoint
administrators a way to perform backup and recovery with additional
options such as file compression or working with SQL snapshots.
Listed below are a few of the benefits available when working with Windows PowerShell:
• Windows PowerShell scripts can be
developed and scheduled (with Windows Task Scheduler), whereas Central
Administration is used for single-use backups and restores.
• Windows PowerShell has the advantage of
running against SQL snapshots instead of the production database. One
of the parameters of the Windows PowerShell command will cause a SQL
snapshot to be generated, and then Windows PowerShell will run the
action against the snapshot instead of the production database. This
will reduce the resource impact of the backup operation on the
production environment.
• With Windows PowerShell, SharePoint administrators will have more granular control of options for the backup or restore.
Q. How to Export a Site or List in SharePoint 2010?
Ans. SharePoint Server 2010 provides
several new features that provide a granular level of backup for various
components of site content. This includes content at the site, subsite,
and list level.
Through Central Administration(Granular
level Back-up) a SharePoint Administrator can configure a backup of a
subsite or list. An Administrator can choose a site and a specific list
to be exported.The administrators can also choose to export security and
select the different versions that will be exported with the list.
What are the types of workflow that you can design in SharePoint 2010.
List Workflows, Reusable List Workflows and Site workflows
Reusable List Workflows –
Workflow can be associated to any list, library, or content type in the site collection.
Site workflows -is associated to a site
Can you modify the Out-of-Box workflows in SharePoint 2010 ?
In SharePoint 2010, you have an option to customize the Out-of-Box workflows.
Events
Actions
Conditions
What are the Types of forms associated with the workflow ?
1. Initiation form – An initiation form gathers information from the workflow participant when they start the workflow.
2. Task form – A
custom task form allows workflow participants to interact with tasks in
the Tasks list specified for the workflow. With the Custom Task Wizard,
you can easily create custom form fields and add them to a custom task
form. When you finish designing the workflow, SharePoint Designer 2010
automatically generates the InfoPath or ASP.NET forms for your custom
tasks.
3. Reusable workflow – association form –
A reusable workflow, by default, only provides the fields common to all
items, such as Created and Modified by. This is because a reusable
workflow isn’t by default associated with a list, library, or content
type. An association form enables you to associate fields with a
reusable workflow so that the fields will be available when you design
and run the workflow.
When are these forms get created ? And how do you customize it ?
Ans. SharePoint
Designer 2010 automatically generates the forms, but you can customize
them by going to the settings page for the workflow, in the Forms
section, click the form you want to customize. Workflow forms are either
InfoPath or ASP.NET pages. They are stored on the SharePoint site with
the workflow source files.
Administrator
What Has Changed with SSP in SharePoint 2010.
In SharePoint 2010 Shared Service Providers (SSP's) are replaced by Service Applications
Q. What are the Methods of Backup and Recovery in SharePoint 2010?
Ans. Microsoft
SharePoint Server 2010 provides a broad range of levels for performing
backups, including the entire farm, farm configuration information, site
collections, subsites, or lists.
SharePoint Server 2010 uses two different tools to configure backup and recovery.
1. Central Administration : Central
Administration provides a user interface where SharePoint
Administrators will be prompted via menu structures to select the
information that needs to be backed up. (see the Image below)
2. Windows PowerShell : Windows
PowerShell is a command line tool that provides SharePoint
administrators a way to perform backup and recovery with additional
options such as file compression or working with SQL snapshots.
Q. How to Export a Site or List in SharePoint 2010?
Ans. SharePoint
Server 2010 provides several new features that provide a granular level
of backup for various components of site content. This includes content
at the site, subsite, and list level.
Through Central
Administration(Granular level Back-up) a SharePoint Administrator can
configure a backup of a subsite or list. An Administrator can choose a
site and a specific list to be exported.The administrators can also
choose to export security and select the different versions that will be
exported with the list.
Q. What is Enterprise Metadata Management?
Enterprise metadata management (EMM) is
a set of features introduced in Microsoft SharePoint Server 2010 that
enable taxonomists, librarians, and administrators to create and manage
terms and sets of terms across the enterprise.
What is Business Connectivity Services in SharePoint ?
Ans.SharePoint
2010 provides a new set of technologies known as Business Connectivity
Services for retrieving, editing, updating, and deleting data from
external systems(for e.g. data from ERP or CRM database). BCS enhances
the SharePoint platform’s capabilities with out-of-box features,
services and tools that streamline development of solutions with deep
integration of external data and services.
General
What are the security improvements in SharePoint 2010 ?
Ans. In SharePoint 2010 a variety of security methods have been introduced.
Claims-Based Authentication - Claims based authentication is based on identity. and trust.
Code Access Security - in which you can specify your own code access
security (CAS) policy for your web parts.
Sandbox Solutions - Sandbox Solutions which when deployed to the server, SharePoint runs in a special process that has limited permissions.
Cross-Site Scripting - Introduced to prevent Cross - Site Scripting (XSS) attacks
Q. Whats New with SharePoint WebParts?
A developer can create two types of webparts using Visual Studio 2010.
1. Visual Webparts - Allows
you to Drag and Drop the controls from the Toolbox to WebPart Design
surface. You can of course write your custom code in the code file. You
can also package and deploy your webparts directly to Sharepoint from VS
by pressing Clt+F5. Visual studio 2010 also provides you with three
different views for developing webparts. The views are split view,
design view and Source view(as we have in designer 2007).
Note : The Visual Webpart project Item basically loads a User Control as a WebPart.
2. ASP.Net WebParts - Where
a developer can build up User Interface and logic in a class file. You
do not have designer for drag and drop of controls. This webpart
inherits from standard ASP.Net webpart. For Deployment we can again use
ctrl+f5 to deploy this webpart.
Q. What are the Visual Studio 2010 Tools for SharePoint.
Ans. Visual
Studio 2010 includes SharePoint-specific project types and project item
types, and includes powerful packaging, deployment, and debugging
features that help increase your efficiency as a SharePoint 2010
developer.
Some of the Templates avaiable are :
1.Visual Web Part project template.
2. List defination template.
3. Content Type template.
4. Empty Project template.
5. Event Receiver template.
6. some workflow template.
7. the Site Definition template
and many more....
What are SharePoint Sandboxed soultions ?
Ans. SharePoint
2010 provides a new sandboxed environment that enables you to run user
solutions without affecting the rest of the SharePoint farm. This
environment means that users can upload their own custom solutions
without requiring intervention from administrators, and without putting
the rest of the farm at risk. This means that the existing sites\pages
or components will not be effected by the newly added soultion.
Users can deploy the below four things as sandboxed soultions :
1. WebParts.
2. Event Receivers.
3. List Definations.
4. Workflows.
Q. What are Requirenments for SharePoint 2010.
Ans. SharePoint
Server 2010 will support only 64 - bit. It will require 64 bit Windows
Server 2008 or 64 bit Windows Server 2008 R2. In addition to this, it
will require 64 bit version of SQL Server 2008 or 64-bit version of SQL
Server 2005.
Q. What is LINQ. How is it used in Sharepoint ?
Ans.
LINQ is a feature of the programming languages C# 3.0 and Visual Basic
.NET. LINQ allows you to query in an object-oriented way, supports
compile-time check, gives you intellisense support in Visual Studio and
defines a unified, SQL like syntax to query any data source. But unlike
other languages and query syntaxes which vary from one type of data
source to another, LINQ can be used to query, in principle, any data
source whatsoever. It is commonly used to query objects collections, XML
and SQL server data sources.
The LINQ to SharePoint Provider is
defined in the Microsoft.SharePoint.Linq namespace. It translates LINQ
queries into Collaborative Application Markup Language (CAML) queries.
Q. What Changes are made in SharePoint 2010 to enforce Referential Integrity?
Ans. In SharePoint 2010, Referential Integrity is enforced using two options, available with Look-up columns.
While creating a Look-up column,
you can either choose a) Restrict Delete or b) Cascade Delete to define a
relationship between the Look-up list and the list containing the
look-up Column.
Q . Whats New in SPALerts ?
Ans. In
SharePoint 2007, alerts were send only through e-mails, but in SP2010
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.
Q. What is Windows Powershell ?
Ans. Windows PowerShell is a new Windows
command-line shell designed especially for system administrators. In the
SharePoint administration context, Windows PowerShell is another
administration tool that supersedes the existing Stsadm.exe.
Q. How is Windows Powershell different from Stsadm ?
Ans. Unlike stsadm, which accept and
return text, Windows PowerShell is built on the Microsoft .NET Framework
and accepts and returns .NET Framework objects. In addition to that it
also gives you access to the file system on the computer so that you can
access registry,digital signature certificate etc..
Q. What are cmdlet's?
Ans. Windows PowerShell introduces the
concept of a cmdlet which are simple build in commands, written in a
.net language like C# or VB.
Q. Can you Create PowerShell scripts for deploying components in SharePoint ?
Ans. If you are creating a webpart with
VS 2010 then you can deploy it using ctrl + f5. However, to activate the
webpart feature you can write a powershell script (.ps1) and execute it
after dpeloyment.
Q. Where is Powershell located in sharePoint ?
Ans. On the Start menu, click All
Programs -> Click Microsoft SharePoint 2010 Products -> Click
SharePoint 2010 Management Shell.
Q.
If you need going to install a webpart or any custom solution in
SharePoint 2010 using PowerShell What permissions do you need?
Ans. 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.
Q. How to list all the commands in PowerShell ?
Ans. Get-Command * commands gets you all the Powershell commands.
Q.1 What is the Managed Client Object Model?
Ans: The Managed Client Object Model allows sharepoint data to be used by other applications using APIs.
Q.2 What is the Metadata store? Can Multilingual terms be used?
Ans:
Managed metadata is a hierarchical collection of centrally managed
terms that you can define, and then use as attributes for items in
Microsoft SharePoint Server 2010.
Q.3 What is Windows Powershell?
Ans:
Windows PowerShell is Microsoft’s task automation framework, consisting
of a command-line shell and associated scripting language built on top
of, and integrated with the .NET Framework. PowerShell provides full
access to COM and WMI, enabling administrators to perform administrative
tasks on both local and remote Windows systems.
Q.4
An organisation of 150 people would like to leverage SharePoint 2010
for Document Management. Can you describe an appropriate deployment?
Answer:
Web Server, perhaps an Application server and a Database server. This
answer can vary depending on the usage characteristics of users.
Q.5 What is the difference between a Web Part and a User Control?
A
bare ASP.NET ascx control would have to be added to a custom layout
page. This limits the utility of the control a little as it cannot be
added just anywhere.Having a webpart gives the flexibility of the
control being added to the site multiple times in different locations or
even multiple times on the same page with different properties.Webparts
are also able to accept connections from “filter” webparts on the same
page, giving additional flexibility to webparts compared to hosting ascx
controls on the site.When it comes to editors using the site, it makes a
lot of difference for them to be able to add a webpart compared to
editing a page layout, publishing it and then creating pages based on
that page layout, so from the perspective of a site editor, the
difference in usability is really quite large.
