Workflow Interview Questions

What  is Workflow ?

Workflow is a series of tasks that produce an outcome.

workflow is  automated movement of documents or items through a sequence of actions or tasks that are related to a business process.

WF programs run in a special environment known as the WF runtime

Activities are the building bricks that developers use to construct WF programs

We can consider each activity as an atomic and reusable set of instructions that represents a single unit of work.

activities are black boxes of reusable code that expose properties and events.

The consumer of an activity can simply drag and drop it on a design surface within Visual Studio.

The consumer of activity also generates event handlers for activities and write code behind these event handlers.

What are the Different Stages of SharePoint Workflow Life Cycle?

There are four stages in the Sharepoint workflow cycle -- associate, initiate, modify and complete

 Workflow Types:

Workflows that are included in Office SharePoint Server 2007

Approval

Collect Feedback

Collect Signatures

Disposition Approval

Three-state

Group Approval

Translation Management

Steps involved in using workflows

1.      Adding a workflow to a list, library, or content type

2.      Starting a workflow on a document or item

3.      Modifying a workflow in progress

4.      Completing workflow tasks

5.      Tracking the status of workflows

What are the types of workflow that you can design in SharePoint 2010.

Ans. you can design List Workflows, Reusable List Workflows and Site workflows using SharePoint designer 2010.

Steps Involved to Create Workflow from SPD :

Steps : Initialize
            Modify
            Associate

Steps:
It is used to organize the actions and conditions that make up the workflow into groups

Actions:
A very basic unit of work that can be added to the workflow.

Conditions:
conditions control whether or how actions will do their work.Conditions give the workflow author the opportunity to add branching and conditional logic to the workflow, hence controlling what happens based upon circumstances at run time.

Q. What is a workflow?

Ans. Workflows are the way an organization functions, a series of actions that correspond to a work process, such as the process for purchase orders.SharePoint 2010 helps you automate these workflows, thereby increasing the efficiency and productivity of the organization.

Q.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. ( disadv: lot of code required when compared to Infopath approach)
• using Microsoft Office InfoPath 2007 (disadv: picks up a dependenct on MOSS, i.e. it cannot run in a standalone WSS environment)

Q. What is the difference between method activity and event activity in WF ?
A method activity is one that performs an action, such as creating or updating a task. An event activity is one that runs in response to an action occurring.

Q. What are the types of workflow that you can design in SharePoint 2010.

Ans. you can design List Workflows, Reusable List Workflows and Site workflows using SharePoint designer 2010.

Q. What Reusable List Workflows and Site workflows ?

Ans.

Reusable List Workflows -

You 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. You can also create a reusable workflow in any subsite in the site collection; this workflow is available for reuse in that particular subsite.

Site workflows - A site workflow is associated to a site — not to a list, library, or content type. So unlike most workflows, a site workflow is not running on a specific list item. Because of this, many of the actions that are available for items not available for site workflows.

Q. Can you modify the Out-of-Box workflows in SharePoint 2010 ?

Ans. In SharePoint 2010, you have an option to customize the Out-of-Box workflows. The four most popular workflows in SharePoint Server 2007 — the Approval, Collect Feedback, Collect Signatures, Publishing Approval workflows — have been completely rebuilt as declarative reusable workflows, meaning that they are now fully customizable in SharePoint Designer 2010.

Q. What are events, actions, conditions and steps?

Ans. Lets look at this one by one.

Events - An event is what starts or initiates a workflow. Events can also be used to manage the timing of actions within a workflow, such as waiting for the status of an item to change. There are three events that can start a workflow:

* An item is created.
* An item is changed.
* A workflow participant clicks a start button on the SharePoint site.

Actions – An action is the most basic unit of work in a workflow. SharePoint Designer 2010 provides a set of ready-made, reusable actions for you to incorporate into your workflow.

For example, your workflow can:

* Create, copy, change, or delete list items (including documents).
* Check items in or out.
* Send an e-mail message.

Conditions - When you design a workflow, you can use the workflow editor to create rules that apply conditional logic to SharePoint sites, lists, items and content types. A rule establishes a condition where the workflow performs the associated action only if that condition is true. For example, you can create a rule where the workflow sends a reviewer an e-mail message only if an item is created by a specific person.

Q. What are Parallel and Serial actions ?

Ans. When you have more than one action associated with a condition, the actions can be set up to run at the same time (parallel) or one after another (serial), the default.

Q. What are the Types of forms associated with the workflow ?

Ans. With SharePoint Designer 2010, you can create three types of workflow forms:

Initiation form – An initiation form gathers information from the workflow participant when they start the workflow. It is automatically generated when you create the workflow in SharePoint Designer 2010. Initiation forms are displayed to users when they manually start a workflow on a given SharePoint item. With an initiation form, users can specify additional parameters or information about the workflow as it applies to the given SharePoint item.

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.

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.

Q. 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.

8 Steps to Create Workflows using SharePoint Designer

Introduction

Workflows are now an integral part for any project. You can build a SharePoint work flow using the available templates, SharePoint designer and Visual Studio 2005 / 2008. This tutorial will mainly concentrate on workflow creation using SharepPoint designer. We will walk through the basic 8 steps needed to create workflows using SharePoint designer.

I have published some videos on SharePoint, WCF, WPF, WWF, design patterns, UML, FPA, Enterprise blocks, etc. You can watch the videos here. You can download my 400 .NET FAQ EBook from here.

8 Steps to Create Workflow using SharePoint Designer

SharePoint designer helps us to create workflows and attach the workflows to a content type like list, document, etc. In other words, SharePoint designer creates workflows and publishes the workflow on the SharePoint server site.

To understand it better, we will build a simple workflow of completed and incomplete tasks. We will create two lists, one is the incomplete tasks and the other the completed tasks. The workflow will flow something like this:

• User will create a task and enter the status of the task. 
• If the task is incomplete, nothing will happen. 
• Once the task is marked as complete, the task will be copied from incomplete task list to completed task list. 
• The task will be deleted from the incomplete task list. 

So let’s understand the eight important steps we will need to create the above workflow using SharePoint designer.
Step 1

Create a team site using the SharePoint team site template.
Step 2

Create two task lists, one is incomplete task list and the other completed task list.
To create task list, click on site action -> Create: Add a new library list -> create a task.

Step 3
Start the SharePoint designer.

Step 4

Open the site in your SharePoint designer using click on file -> open site.

Step 5

Go to workflows by clicking on file -> new -> SharePoint content and click ok as shown in the below figure:

Step 6

This is an important step. In this step, we define two important things. The first is this workflow will be attached to which list. Currently we have attached the workflow to incomplete tasks list. Second we need to define the events on which the workflow should be activated. For the current scenario, we have considered two events; one when the item is created and the second when the item is updated.

Step 7

This is one more crucial step where we need to define on what condition the workflow will execute and what action should take place if the condition is true. So when a task status is completed, two actions will take place. First the task will be copied from the incomplete task list to the completed task list. Second the task is deleted from the incomplete task list.

Once you click finish, you can see the workflow created in the SharePoint designer. This workflow is also published to the SharePoint server,

You can see if the workflow is associated with the incomplete task list. Go to incomplete tasks -> Settings -> List settings -> Workflow settings. You can see that the workflow is attached to the incomplete task list.

Step 8

Ok, now it’s time to see the workflow in action. So go to incomplete task list and create a task with status completed.

Once you click ok, you see the task for some seconds in the incomplete tasks list and then the task is copied to the completed task list and deleted from the incomplete task list.

SharePoint 2010 Interview Questions

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 hives in SharePoint?

Ans. Three New Folders have been added in 12 hive structure. It’s Called 14 hive/root in SharePoint 2010

• User Code – files used to support sandboxed solutions.

• Web Clients – used for the client Object Model.

• Web Services – .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. What’s New with SharePoint Web Parts?

A developer can create two types of web parts using Visual Studio 2010.

     1.       Visual Web parts - Allows you to Drag and Drop the controls from the Toolbox to Web Part Design surface. You can of course write your custom code in the code file. You can also package and deploy your web parts directly to SharePoint from VS by pressing Clt+F5. Visual studio 2010 also provides you with three different views for developing web parts. The views are split view, design view and Source view (as we have in designer 2007).
Note: The Visual Web part project Item basically loads a User Control as a Web Part.                                          
2.   ASP.Net Web Parts - 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 web part inherits from standard ASP.Net web part. For Deployment we can again use ctrl+f5 to deploy this web part.

 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 available are:

 1. Visual Web Part project template.

 2. List definition 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 solutions?

 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 affected by the newly added solution. Users can deploy the below four things as sandboxed solutions:

1. Web Parts.

2. Event Receivers.

 3. List Definitions.

 4. Workflows.

Q. What are Requirements 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 intelligence 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.

SharePoint 2010/2007 Interview Questions with Answers

Q. Where are the files deployed in SharePoint 2007 ?

Ans. Developers generally deploy various files in the in the 12 hive folders that make SharePoint Interface. For e.g. if a Custom Css file needs to be deployed it will go under “C:\Program Files\Common Files\Microsoft Shared\Web Server Extenstions\12\Templates\Layouts\1033\Styles” path. This path is well mapped with Out-of-box SharePoint components and is suppose to contain Custom and Out-of-Box Css files.

Q. How are these files deployed?

Ans. Solution packages or wsp are used to deploy or drop these files in various 12 hive folders. The manifest.xml (solution package file ) contains various tags such as or to drop in these files in the 12 hive. Tags in manifest.xml file are well mapped with the 12 hive folders, so all you need is to provide a virtual location for a folder under Templates to drop your file in Files.

Q. How can you add an existing user control on a SharePoint Page ? Do you need to make any modifications to the control ?

 Ans. You can either use a Custom webpart or a smartPart webpat to load your usercontrol in the page. You can also add a user control to a master page if that’s your requirement. You must drop the signed assembly for the UserControl in GAC and add the usercontrol in _ControlTemplates folder under 12 hive.

Q. If you create a event receiver feature how can you bind it with one specific list.

Ans. We can create a FeatureReceiver and write some code in FeatureActivating method of the FeatureReceiver to assign the specific list to the event receiver feature itself.

Q. How would you pass user credentials while using SharePoint WebService from your Web Part or application.

Ans. The web service needs credentials to be set before making calls. Examples: listService.UseDefaultCredentials = true; // use currently logged on user listService.Credentials = new System.Net.NetworkCredential(“user”, “pass”, “domain”); // use specified user.

Q. What is the difference between SPQuery and SPSiteDataquery ?

Ans. SPQuery is a CAML query used to retrieves items fromone perticular list . SPSiteDataquery on the other hand retrieves items from multiple lists and libraries in the same site collection. you can however, specify the Guid of the Lists for the SPsiteDataQuery to run on.

 Q. How can you display data from a Parent site in a Subsite or Cross sites ?

Ans. Even though, its difficult to do this Out-of-box we have sevral options :

1. Using sharepoint designer – We can use DataviewWebPart and choose to connect to a different site and after creatign a connection, you will be listed with all list and libraries of the parent site or the cross site or site collection.

2. Use Site Lookup column – We can also create a column in the parent site as a Site column of type Lookup and then can add this column in subsites list\library.

 3. Can export a listView webpart from a parent site (ofcourse displaying parent site list data) and import it into any subsite page.

 Q. How do you display an infopath form on any SharePoint page.

 Ans. You need to use xmlformviewer webpart to display the admin uploaded infopath form.

SharePoint 2007 Security Accounts

Great summary on SPS 2007 service accounts:

I’ve been working on a number of MOSS implementations lately, and I always get a lot of questions about what service accounts are needed to get the implementation rolling. Microsoft has a really nice, but very long article on the accounts.more info at  (http://technet2.microsoft.com/Office/en-us/library/f07768d4-ca37-447a-a056-1a67d93ef5401033.mspx?mfr=true), but most of my clients do not have the time or want to read that article. So I put together some basic guidelines on MOSS service accounts…

The following covers the most common service accounts that need to be setup and their typical permissions in order for MOSS to function properly. Note that each deployment is different, so these accounts may differ based upon individual requirements. There are some additional accounts that you may need for other optional services, but they are not mentioned here.

Running MOSS Setup

On every server where MOSS is to be installed, the account you run setup with must belong to the local administrators group. In addition, this account must be a Domain User and be a member of the following SQL server security roles: Logins, Securityadmin & Dbcreator. This account is going to be doing a lot – creating new databases, and also creating new IIS sites – so make sure you have enough permissions! Typically, an account such as the domain administrator is used to run the installation, which addresses all of the security requirements.

SQL Server (SQL_Service)

This account is specified when a new SQL server is being brought online or a new instance installed. It typically is used for running both the SQL Server & SQL Server Agent, however, each can have their own account. For our purposes, we will utilize one account for both SQL Server & the Agent. The account only needs to be a basic Domain Account with no specific permissions set. When SQL Server is installed, all of the other appropriate permissions will be granted to the account.

 Database Access Account / Farm Account (Farm_Service)

This account serves a few roles. The first is that it is used by MOSS to access the databases… it acts as the account by which the server(s) MOSS is installed on communicates back and forth to SQL with (read/write). Additionally, it is used as the identity for the Central Administration application pool & the WSS Timer service. This account needs to be a Domain Account - but note that it is believed to have to be a local admin on every MOSS box - this is not true, as Spence points out very eloquently.

Shared Service Provider (SSP#_Service)

Each shared service provider can run under its own account, therefore, it is desirable to name the account using a number. This way, if your MOSS farm ends up having a large number of SSPs, you can map the SSPs back to their specific service accounts easily. This account is used for the SSP web services & the SSP timer jobs. The account only needs to be a basic Domain Account with no specific permissions set.

Office SharePoint Server Search (Search_Service)

 This account is utilized by all of the Shared Service Provider to crawl local & remote content. This account should be a Domain Account & have local administrator permissions on each MOSS server.

Default Content Access Account (SSP#ContentAccess_Service)

When a shared service provider crawls content, this is the default account used if a specific account (see below) is not specified for the content source being crawled. This account is specific for each individual SSP. This account should be a Domain Account & have read access to the content sources it needs to crawl.

Content Access Account (XXXXContent_Service)

If you have specific content sources that need to be crawled, and you do not want to allow the default content access account to crawl them, then you specify an individual content access account (specified at the time a Crawl Rule is setup). This account is a Domain Account with read permissions specifically on the content source it crawls.

Windows SharePoint Services Search Account (WSSSearch_Service)

 The WSS Services Search is used only to provide search capabilities within the Help content. If this search feature is desired, then this account should be configured as a Domain Account with no specific permissions.

Application Pool Process Account (XXXXPool_Service)

 When each application pool is setup, you must specify an account that will be used for that specific application pool’s identity. This account will be used to access the content databases associated with the web application. It is recommended that a new service account is created for each application pool. This should be a Domain Account with no specific permissions. When the account is specified & SharePoint creates the application pool, it automatically grants the account additional needed permissions Q) What are some of the tools that can be used when backing up a SharePoint 2010 environment? SharePoint farm backup and recovery SQL Server System Center Data Protection Manager

 Q) What Microsoft tool can be used for incremental backups?

System Center Data Protection Manager Managed Metadata Questions

Q) What is Managed Metadata?

 Managed metadata is a hierarchical collection of centrally managed terms that you can define, and then use as attributes for items.

Q) What are Terms and Term Sets?

 A term is a word or a phrase that can be associated with an item.  A term set is a collection of related terms.

Q) How do Terms And Term Sets relate to Managed Metadata?

Managed metadata is a way of referring to the fact that terms and term sets can be created and managed independently from the columns themselves.

Q) Are there different types of Term Sets?

There are Local Term Sets and Global Term Sets, one created within the context of a site collection and the other created outside the context of a site collection, respectively.

Q) How are terms created and used?

There are several ways; however the most common is to use the Term Store Management Tool.

Q) How is Managed Metadata, and the related Term technology used?

 Through the UI, the most common use is through the managed metadata list column which allows you to specify the term set to use. It also related to searching and enhancing the user search experience.

Q) What is a sandboxed solution?

 Components that are deployed to run within the sandboxed process rather than running in the production Internet Information Services (IIS) worker process.

Q) What are some examples of things that might run within the SharePoint sandbox?

Any of the following are acceptable answers:  Web Parts Event receivers Feature receivers Custom Microsoft SharePoint Designer workflow activities Microsoft InfoPath business logic others….

Q) Why are sandboxed solutions used?

 Primarily because they promote high layers of isolation. By default they run within a rights-restricted, isolated process based around Code Access Security (CAS). Isolation is possible to increase with activities like running the sandboxing service on only specific SharePoint 2010 servers.

Q) What is a content source in relation to SharePoint search? What’s the minimum amount of content sources?

 A content source is a set of options that you can use to specify what type of content is crawled, what URLs to crawl, and how deep and when to crawl. You must create at least one content source before a crawl can occur.

Q) What is a search scope?

 A search scope defines a subset of information in the search index. Users can select a search scope when performing a search.

Q) What is a federated location with SharePoint search?

Federated locations provide information that exists outside of your internal network to your end-users.

Q) How does managed metadata affect search?

 Enhances the end-user search experience by mapping crawled properties to managed properties. Managed properties show up in search results and help users perform more successful queries.

Q)  What is query logging in SharePoint 2010?

Collects information about user search queries and search results that users select on their computers to improve the relevancy of search results and to improve query suggestions.

Q) What authentication type does the SharePoint crawler use?

The crawl component requires access to content using NTLM authentication.

Q) Please describe what a Service Application is in SharePoint 2010.

 Service applications in SharePoint 2010 are a set of services that can possibly be shared across Web applications. Some of these services may or may not be shared across the SharePoint 2010 farm. The reason these applications are shared is the overall reduction of resources required to supply the functionality these services cultivate.

Q) Please provide an example of one of these service applications.

Any of the below are acceptable answers:

ü  Access Services

ü  Business Data Connectivity service

ü  Excel Services Application

ü  Managed Metadata service

ü  PerformancePoint Service Application

ü  Search service

ü  Secure Store Service

ü  State service

ü  Usage and Health Data Collection service

ü  User Profile service

ü  Visio Graphics Service

ü  Web Analytics service

ü  Word Automation Services

ü  Microsoft SharePoint Foundation Subscription Settings Service

 Q) What are Service Application Groups used for?

Just provides a logical grouping of services that are scoped to a particular Web Application.

 Q) How are Service Applications deployed in terms of IIS (Internet Information Services)?

 They are provisioned as a single Internet Information Services (IIS) Web site.

Q) Explain how connections are managed with Service Applications.

A virtual entity is used that is referred to as a proxy, due to label in PowerShell.

Q) What are some common examples of SharePoint 2010 services architectures, and what are the advantages of each design?

The three most popular designs are single farms with either a single service application group or multiple service application groups, or Enterprise services farms.

Single farms with a single service application group are generally the most common, and have the advantages of easy deployment, simple service application allocation, effective resource utilization and cohesive management.

Single farms with multiple service application groups is less common, and have the advantage of potential individual management of service applications as well as allowing data isolation, and while being more complex to deploy and maintain allows targeting of sites to particular service applications. Enterprise Service Farms is pretty uncommon as it is a complete farm dedicated to Service Applications but promotes autonomous management and high levels of data isolation.

Q) Are there any other type of relevant service architectures?

Depending on the environment requirements, a specialized farm can also be used in order to deploy specific services tailored to the organizational requirements which can aid in scaling out and conservation of resources.

Q) What is the User Profile service?

Allows configuring and managing User profile properties, Audiences, Profile synchronization settings, organization browsing and management settings, and My Site settings.

 Q) What are User Profiles?

Aggregates properties from diverse identity content sources together to create unified and consistent profiles across an organization, used throughout the SharePoint environment.

Q) What is Excel Services?

Allows sharing, securing, managing, and using Excel 2010 workbooks in a SharePoint Server Web site or document library. Excel Services consists of the Excel Calculation Services (ECS), Microsoft Excel Web Access (EWA), and Excel Web Services (EWS) components.

Q) What is PerformancePoint Services?

Allows users to monitor and analyze a business by building dashboards, scorecards, and key performance indicators (KPIs).

Q) What is Visio Services?

Allows users to share and view Microsoft Visio Web drawings. The service also enables data-connected Microsoft Visio 2010 Web drawings to be refreshed and updated from various data sources.

 Q) What is Access Services?

 Allows users to edit, update, and create linked Microsoft Access 2010 databases that can be viewed and manipulated by using an internet browser, the Access client, or a linked HTML page.

Q) What is the Secure Store Service (SSS)?

 A secure database for storing credentials that are associated with application IDs.

 Q) What is Content Deployment?

Content deployment enables you to copy content from a source site collection to a destination site collection. Backup / DR Questions.

Q) Describe how redundancy can be built into a SharePoint environment. Please be specific in regards to any auxiliary components.

 Multiple front-end web servers (WFE’s) can be deployed and correlated through Windows NLB or anything approach. Application servers can be deployed into the farm for a variety of purposes, depending on organizational requirements. Databases can be clustered or mirrored, again depending on requirements and environment.

 Q) From a basic standpoint, what is the difference between SQL clustering and mirroring?

Clustering provides a failover scenario whereby one or more nodes can be swapped as active depending on whether a node goes down. In mirroring, transactions are sent directly from a principal database and server to a mirror database to establish essentially a replica of the database.

Q) What Is Governance in terms of SharePoint 2010?

Governance is the set of policies, roles, responsibilities, and processes that guide, direct, and control how an organization’s business divisions and IT teams cooperate to achieve business goals.

Q) What are some useful, OOB features of SharePoint that aid with governance of an environment?

 Any of the below are acceptable answers. There are some others but these are the major ones that I generally look for from a candidate:

 Site templates – consistent branding, site structure, and layout can be enforce a set of customizations that are applied to a site definition.

Quotas – limits to the amount of storage a site collection can use.

Locks - prevent users from either adding content to a site collection or using the site collection. Web application permissions and policies – comprehensive security settings that apply to all users and groups for all site collections within a Web application.

Self-service site creation - enables users to create their own site collections, thus must be incorporated into a governance scheme.

Q) Describe the monitoring features that are baked into SharePoint 2010. ?

Diagnostic logging captures data about the state of the system, whereas health and usage data collection uses specific timer jobs to perform monitoring tasks, collecting information about: Performance Counter Fata

ü  Event Log Data

ü  Timer Service Data

ü  Metrics For Site Collections and Sites

ü  Search Usage Data

Q) What is a declarative workflow? Can non-authenticated users participate in workflows?

Workflows created by using Microsoft SharePoint Designer 2010, the default setting enables deployment of declarative workflows. Yes, however you do not give non-authorized users access to the site. The e-mail message and attachments sent from notifications might contain sensitive information.