Friday, April 9, 2010

SharePoint 2007 Interview Questions

SharePoint Concepts

What is Content Type? Where did you use content type?

A content type is a flexible and reusable WSS type definition that defines the columns and behavior for an item in a list or a document in a document library.
For example, consider the following two types of documents: software specifications and legal contracts. It is reasonable that you might want to store documents of those two types in the same document library. However, the metadata you would want to gather and store about each of these document types would be very different. In addition, you would most likely want to assign very different workflows to the two types of documents.

Why to maintain separate SSP? Is there any specific reason?

Did you involved in Site Governance?

How many Site Collections are there in your current SharePoint Environment?

What is Item level security?

Why did you use SharePoint Central Administration to deploy InfoPath Form?

Because my InfoPath Form has custom code (code behind files) and its needs to be approved by the administrator.

How to migrate SharePoint 2003 to SharePoint 2007?

There are multiple approaches depends on the customizations. I followed Database migration.

What kind of authentication providers did you use in SharePoint?

We can use Windows authentication and Form based authentication.

How do you setup Form based authentication?



Why you used K2 BlackPearl instead of Microsoft Workflow Framework?

Due to lot of customizations in our workflow. By using K2 we can create complex workflows with out writing code or with minimal code.

Why cant you use SharePoint Designer workflows instead of custom Workflows (K2/WF)?

Due to lot of customizations in our workflow.

What is Workflow Task Forms?

Describe the difference between a Site definition and a Site template?

I have a single SharePoint list in which I want to keep a list of computers and metadata describing each computer's properties. For desktops, I have one set of metadata fields. For laptops, I have another set of metadata fields. How can I store both laptops and desktops in this same list?

By using Content Types.

What is a SharePoint Feature? What files are used to define a feature?

A SharePoint Feature is a functional component that can be activated and deactivate at various scopes throughout a SharePoint instances. Scopes include
  • Farm
  • WebApplication
  • Site (site collection)
  • Web (site)
Features have their own receiver architecture, which allow you to trap events such as when a feature is
  • installing
  • uninstalling
  • activated
  • deactivated
The element types that can be defined by a feature include
  • menu commands
  • link commands
  • page templates
  • page instances
  • list definitions
  • list instances
  • event handlers
  • workflows

The two files that are used to define a feature are

  • feature.xml - The feature XML file defines the actual feature and will make SharePoint aware of the installed feature.
  • manifest file(elements.xml) - The manifest file contains details about the feature such as functionality.

Common stsadm commands associated with feature are

  • stsadm -o installfeature
  • stsadm -o uninstallfeature
  • stsadm -o activatefeature
  • stsadm -o deactivatefeature

Workflow can be applied to what all elements of SharePoint ?

  • At the level of a list or document library
  • At the level of a content type defined at site scope
  • At the level of a site ( SharePoint 2010 )

What are ways to create input forms for workflow ?

Two different approaches can be used to develop custom input forms for a WSS workflow template.
  • You can create your forms by using custom application pages, which are standard .aspx pages deployed to run out of the _layouts directory. ( disadvantage: lot of code required when compared to InfoPath approach)
  • using Microsoft Office InfoPath 2007 (disadvantage: picks up a dependent on MOSS, i.e., it cannot run in a standalone WSS environment)

Can you explain what is the difference between Column vs. Field vs. Property?

What are called columns in the user interface are referred to as fields in the schema and object model.
You can create columns at two levels: the site, and list levels. These columns are represented as elements in the site and list schema, and Field objects in the object model. List columns created when you add a site column to a list retain a child/parent relationship with the site column, and retain the same field ID as the site column.
You cannot create a column in a content type. When you add a column to a content type, it's added as a in the content type schema. When you add a content type to a list, the columns referenced by the elements in that content type schema are added to the list as elements.
Therefore, columns are always represented by elements in site and list schemas, and always represented by elements in content type schemas.
Document properties usually just refer to a field as it applies to a specific document. The document property might be something you're tracking solely at the document library level, or it might also be included in the document itself.









  1. WebParts
  1. Did you use DataView webpart? If yes, in what scenario?
  2. Can we use DataView webpart to show document libraries and list to show data?
  3. How to deploy web parts?
  4. What are the challenges you faced while building web parts?
  5. How to create Connected webparts?
  6. What is Event Listeners? Why to use them?
  7. How to deploy event listeners?
  8. What is Content Query WebPart?
  9. I'm writing code to iterate thru the items in a SharePoint list.  What two objects would I use to get a handle on the list and each list item?

0 comments:

Post a Comment