We can create four different types of input forms for workflow
1. An association form
2. An initiation form
3. A modification form
4. A task edit form

RunWithElevatedPrivileges (RWEP) executes the specified method with Full Control rights even if the user does not otherwise have Full Control. In Other words The RunWithElevatedPrivileges (RWEP) method enables you to supply a delegate that runs a subset of code in the context of an account with higher privileges than the current user.
A delegate method that is to run with elevated rights. This method runs under the Application Pool identity, which has site collection administrator privileges on all site collections hosted by that application pool.
The example shows the syntax that is required to define an anonymous method in the call to RunWithElevatedPrivileges.
SPSecurity.RunWithElevatedPrivileges(delegate()
{
// implementation details omitted
});

The main differences between SharePoint List and Library
1. A list is a collection of information that you share with team members.
Document libraries are collections of files that you can share with team members on a Web based on Microsoft Windows SharePoint Services. For example, you can create a library of common documents for a project, and team members can use their Web browsers to find the files, read them, and make comments.
2 We can attach multiple documents to one list item, but in document library there will be only one attachment.
3. In the List the title of the document is NOT indexed. So an end user would not be able to search on the title of the document. Example: I attached a document titled "Copy of Test SPDoc.doc" but after incremental indexing I get no results searching on the word "SPDoc." But we can perform searching by title in Document Library.

4. With a list we only can SPAttachmentCollection.Add(string, byte) only accepting a byte , means the attachment must fit entirely in one continuous block memory. It this is something you do with large file , your server memory may become fragmented.
With a document library we can SPFileCollection.add(string, stream) – The document library Accept a stream, means the content can be in memory, or disk or even a TCP/IP socket.
5. We can't display the name of the attached document in the List. We only see the paperclip that signifies the attachment. Whereas in document Library we are able to see Ttile of attachment or we can modify it.
6. We can’t check in and Check out in List whereas we can check in and check out in library.
7. We can have only major versioning in List whereas in document library we have both major and minor versioning.
7. We can publish a InfoPath Form Template in document library, and this problem arises when we submit the Form in different place

SharePoint 2010 introduces new feature sandbox solution.Here are major difference between sandbox solution and farm solution.

1.The scope of sandbox solution is site collection where as The scope of farm level solution is farm level.

2.Sandboxed solutions, which are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe)Whereas Sandboxed solutions, which are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe)

3.Sandbox run code that can only affect the site collection of the solution.The process runs under a CAS policy that restricts programmatic access to any resource outside the sandbox.Whereas Farm Solution run code that can affect the whole farm.

4.Sandbox Never restart the IIS application pool.If you run any code it will affect only the site collection of the solution. Whereas If you deploy any feature or retract any feature the whole application pool got recycled in farm solution.

5.Sandboxed solutions are uploaded and activated whereas Farm solutions are installed and deployed.

6.we can’t create VISUAL web parts in Sandbox solutions whereas VISUAL web parts can be created in farm solution.

7.When the Sandboxed Solution property is set to True, selecting Build\Deploy Solution deploys the solution to the site collection Solution Gallery.whereas When the Sandboxed Solution property is set to False, selecting Build\Deploy will deploy the solution to the Farm Solution Gallery.

Web Parts is a highly customizable windows that shows information within SharePoint website

Web Parts are located within the web part zones

There are many different built-in web parts categories and types.

Can display data from various sources such as

Lists
search results
forms
other webpages

Yes it is possible to integrate active directory users to a SharePoint websites.

There are two places where the SharePoint designer can be managed SharePoint 2010

1) In central administration
2) In site collection administration

SharePoint designer setting page allows the following

1) Disable SharePoint designer completely
2) Different pages from being detached
3) Hide master pages and page layouts
4) Hide the website URL structure

The main use of sharePoint designer 2010 are

1) Edit pages in advanced mode
2) customise master pages and Page Layouts
3) Edit any file in the website structure

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.