SharePoint 2013 Interview Quetions

Sharepoint:

·         It is a .net based set of products & technologies.

·         Using SharePoint we can create dynamic & secured websites.

·         Sharepoint sites can allow to store information and share it with others and search it in secure manner.

·         SharePoint is a tool for Collaboration.

SP Farm:

·         Farm is a collection of Sharepoint servers having same configuration DB.

·         The Configuration DB stores all the required information to run the farm.

·         There is only one configuration DB per form.

·         1 Farm = 20 Web Applications = 7, 50,000 Site Collections (5, 00,000 Personal Sites and 2, 50,000 Other Sites)

·         1 Farm = 500 Content DBs

Web Application:

·         It is an IIS Website extended by SharePoint server and associate with SQL Server DB.

·         From Central Admin we can create the web application.

·         Once the web application is created, we can extend the web application in different zones.

·         For each web application, content database is created

·         1 Web Application = 5 Zones

Zones:

Zones provide a separate logical paths of authentication for the same web application.

Various Zones in Sharepoint 5:

·         Default

·         Internet

·         Intranet

·         Extranet

·         Custom

Site Collection:

Site Collection is a group of related websites under a common Top level site.

Each site is created using a predefined site template.

Site Pages:

Site pages are used to display site content and are customized by either using browser or SP Designer.

Site Pages are pages that are created edited and customized by end user.

Application Pages:

These Pages are common to all sites they are used most often to administer a site.

Wiki Page:

A wiki page contains a rich content area where we can add text, tables, and images web parts. Etc. can placed together.

Web Part Page:

·         It contains one or more web part zones where web parts can be placed.

·         A web part page is specially designed for the use of web parts.

·         Web part pages are personalizable.

Web part:

·         It is called a code component created in Dotnet to display some content or provide some functionality in a SP Site.

·         Web parts are rendered into a rectangular block known as a "Chrome" with a Title and Menu.

Site Template:

·         It provides the basic component and layout of a new site to be created in SharePoint.

·         It contains specific design information about a site, List, libraries, themes, borders, Web parts Etc.

·         Site Templates are stored in Content DB.

Site Definition:

·         It is a collection of XML or ASPX files, which contains all necessary information. (WebTemp.XML, Onet.XML, Default.aspx)

·         It contains the information of web parts, Lists, libraries, Features, Navigation bars to be in the site which are packaged in SharePoint Solution file (.WSP)

·         Site definitions are stored in Hard Disk.

Web Solution Package:

It is a cabinet file that contains assemblies, resource files, features, images, application pages, and site definitions Etc. in to a single file.

Content Type:

A Content type is a flexible and reusable template that defines a column and behavior for an item in list or document in document library.

Content Type Hub:

·         The site collection which will host content types for sharing is known as content type hub.

·         Content type hubs enables you to create you to create a new content types and make them available to other SharePoint site collection’s in the same or different web applications  or across forms.

·         To enable your site collection to be a content type hub need to activate feature known as “Content Type Syndication Hub” in the site collection level.

Features:

·         A feature provide some functionality when it is activated and we can remove that functionality by deactivating the feature

·         Sharepoint built-in features are located under SharePoint Root/Template/Features path

·         SharePoint feature has following scopes

1.       Farm - feature contained functionality becomes available to whole farm

2.       Web application - feature contained functionality becomes available to the web application in which feature is activated

3.       Site - feature contained functionality becomes available to the site collection in which feature is activated

4.       Web - feature contained functionality becomes available to the sub-site in which feature is activated

·         The SharePoint feature contains following type of files

1.       Feature manifest - Feature.xml (Defines the Feature)

2.       Element manifest - Element.xml (Specify Details about the feature such as functionality)

Module Element:

It allows files to be provisioned under a specific path in a Sharepoint or upload files into a specific library in to a SharePoint

Business Data Catalog:

·         Is used to connect an external Database and view it in SharePoint.

·         By Using this we can only Read from External database.

Business Connectivity Service:

·         It is New in SP2010

·         By using this we can Read and Write in the External database.

TO change the Title:

SPWeb web = SPContext.Current.Web;

            web.Title = txt1.Text;(web.Url  web.Created  web.Description)

            web.Update();

TO Display the List names:

SPWeb web = SPContext.Current.Web;

            foreach (SPList list in web.Lists)

                writer.WriteLine("" + list.Title + "

");

SharePoint Code Analysis Framework (SPCAF).

Essential tool to ensure SharePoint code quality. SPCop analyses SharePoint code from .wsp and .app files and checks all contained code incl. XML, ASPX, JS, CSS for correctness, best practices, memory disposal etc

http://visualstudiogallery.msdn.microsoft.com/c991a9ed-7a7b-465f-9be3-923443fd6e7b

Sandbox Solution:

·         It run in the particular site collection. The solution can only access resources of that particular site collection where it was deployed.

·         They can’t access any content outside of the current site collection.

·         It can’t contain any files to be deployed to the server file system.

·         They can’t be executed run with elevated privileges.

·         Main advantage Sandbox solution can be DEPLOYED BY A SITE COLLECTION Administrator.

·         Sandbox are hosted in the Sharepoint User Code Solution Worker Process (SPUCWorkerProcess.exe) that can affect the site collection.

Farm Solution:

·         The scope is FARM so it has full trusted access.

·         They don’t have any limitations.

·         Farm solution can be DEPLOYED BY A SERVER FORM Administrator.

·         Farm Solution are hosted in the IISWorker Process that can affect the Whole Farm.

Application Pool:

·         A group of one or more URL’s that are served by a particular worker process or set of worker processes.

·         Application pool provide a way for multiple sites to run on the same server but still have their own worker process and identity.

Worker Process:

·         It is responsible to manage all the request and response that are coming from client system.

·         It is the heart of ASP.Net web application which runs in IIS.

CAML:

·         Collaborative Application Markup Language.

·         It is an XML based language this is used in Microsoft windows Sharepoint server to define sites and lists.

·         Define the tables in the window Sharepoint server database during the site provisioning.

·         Developers mostly use CAML Quires to retrieve data from List/Libraries.

Event Receiver:

·         To handle the basic actions or events against an item, List/Library, a web, or a site.

·         SharePoint Raises two types of Events.

1.       Synchronous Events (Before Events): Item Adding It is raised before the content DB is updated

2.       Asynchronous Events (After Events): Item Added It is raised After the content DB is updated

·         An event receiver is a class that contains one or more methods to handle specific events.

·         Sharepoint provides several event receiver classes such as

Ø  SPFeatureReceiver

Ø  SPWebEventReceiver

Ø  SPListEventReceiver

Ø  SPItemEventReceiver

InfoPath:

·         It is an application to create XML based data entry forms.

·         By using this we can create more sophisticated forms with a little or no code.

·         It is a tool for create forms.

·         It is a part of Microsoft office professional plus.

·         Sharepoint provides a Farm Library that can be associated with an InfoPath form template.

·         InfoPath Templates are stored in .XSN file.

·         InfoPath Data files are stored in .XML file.

Advantages:

Validation for fields.

Flexibility to repeated entries.

Managed Code support.

Without programing skills can create the forms

Retention:

The Retention policy feature lets you define retention stages, with an action that happens at the end of each stage. For example, you could define a two-stage retention policy on all documents in a specific library that deletes all previous versions of the document one year after the document is created, and declares the document to be a record five years after the document is created.

The actions that can occur at the end of a stage include the following:

o    Moving the item to the Recycle Bin

o    Permanently deleting the item

o    Transferring the item to another location

o    Starting a workflow

o    Skipping to the next stage

o    Declaring the item to be a record

o    Deleting all previous drafts of the item

o    Deleting all previous versions of the item

How to set Retention Policy:

1.       First Library and Folder Based Retention feature has been activated under Site collection feature

2.       Second activate Content Organizer feature under site level.

3.       Then go to Specific list settings.

4.       Go to Information Management Policy Settings

5.       Then select Item Content Type

6.       Then Enable Retention then add Retention stage.

7.       Then add the Stage Properties.

8.       Then Click Ok

Auditing:  

The Auditing policy feature logs events and operations that are performed on documents and list items. You can configure Auditing to log events such as the following:

• Editing a document or item
• Viewing a document or item
• Checking a document in or out
• Changing the permissions for a document or item
• Deleting a document or item

·         Opening or downloading documents, viewing items in lists, or viewing item properties

·         Editing items

·         Checking out or checking in items

·         Moving or copying items to another location in the site

·         Deleting or restoring items

Labeling:   

The Labeling policy feature specifies a label to associate with a type of document or list item. Labels are searchable text areas that SharePoint Server 2013 generates based on properties and formatting that you specify. For example, in a law firm, a document related to a legal matter could include a label that contains the clients' names, the case number, and the attorney assigned to the matter. Labels are especially useful in printed versions of documents as a way to display document properties in printed copy. Along with using labels for documents, you can associate a label with a list item and include that label in views of the list.

Note:

The label policy feature has been deprecated and should not be used in SharePoint Server 2013.

Barcode:   

The Barcode policy feature enables you to track physical copies of a document by creating a unique identifier value for a document and inserting a bar code image of that value in the document. By default, bar codes are compliant with the common Code 39 standard (ANSI/AIM BC1-1995, Code 39), and you can plug in other bar code providers by using the policies object model.