Firewalls can't protect very well against things like viruses or malicious software (malware). There are too many ways of encoding binary files for transfer over networks, and too many different architectures and viruses to try to search for them all. In other words, a firewall cannot replace security-consciousness on the part of your users. In general, a firewall cannot protect against a data-driven attack--attacks in which something is mailed or copied to an internal host where it is then executed.

Alternate Answer:
Properly configured firewalls can limit the propagation of worms - a form of malware.  Typically, firewalls are edge or parameter devices (separates network zones) and most viruses and malware targets end points (user workstations and servers).

There are 3 main uses for the static.
1. If you declare within a function:
It retains the value between function calls

2.If it is declared for a function name:
By default function is extern..so it will be visible from other files. if the function declaration is as static, it is invisible for the outer files

3.Static for global variables:
By default we can use the global variables from outside files If it is static global..that variable is limitied to with in the file

Start with the present and tell why you are well qualified for the position. Remember that the key to all successful interviewing is to match your qualifications to what the interviewer is looking for. In other words you must sell what the buyer is buying. This is the single most important strategy in job hunting.

So, before you answer this or any question it's imperative that you try to uncover your interviewer's greatest need, want, problem or goal.
To do so, make you take these two steps:
Do all the homework you can before the hr interview to uncover this person's wants and needs (not the generalized needs of the industry or company)

As early as you can in the interview, ask for a more complete description of what the position entails. You might say: "I have a number of accomplishments I'd like to tell you about, but I want to make the best use of our time together and talk directly to your needs. To help me do, that, could you tell me more about the most important priorities of this position? All I know is what I (heard from the recruiter, read in the classified ad, etc.)"

Then, ALWAYS follow-up with a second and possibly, third question, to draw out his needs even more. Surprisingly, it's usually this second or third question that unearths what the interviewer is most looking for.

You might ask simply, "And in addition to that?..." or, "Is there anything else you see as essential to success in this position?:

This process will not feel easy or natural at first, because it is easier simply to answer questions, but only if you uncover the employer's wants and needs will your answers make the most sense. Practice asking these key questions before giving your answers, the process will feel more natural and you will be light years ahead of the other job candidates you're competing with.

After uncovering what the employer is looking for, describe why the needs of this job bear striking parallels to tasks you've succeeded at before. Be sure to illustrate with specific examples of your responsibilities and especially your achievements, all of which are geared to present yourself as a perfect match for the needs he has just described.

The .NET Framework 3.5 provides the foundation for building connected and appealing applications, productively, on a wide variety of systems from the device to the data center.

Microsoft continues to support developers using the .NET Framework platform by providing support for applications built in previous versions to the 3.5 release, so existing applications built for .NET Framework 2.0 or .NET Framework 3.0 will continue to work.

The .NET Framework 3.5 adds new features in several major technology areas:

• Deep integration of Language Integrated Query (LINQ) and data awareness.
• Support for Web 2.0 AJAX-style applications and services in ASP.NET and WCF.
• Full tooling support for WF, Windows Communication Foundation (WCF), and Windows Presentation Foundation (WPF), including the new workflow-enabled services technology.
• New classes in the base class library (BCL) for the .NET Framework 3.5 address the most common customer requests.

In n-tier architecture the entire application is divided in several pieces. These pieces can be logical or physical. Each piece performs a specific task such as displaying user interface or data access. There can be any number of tiers or layers of such pieces. Hence, the name n-tier (Note that many times the terms tier and layer are used interchangeably). However, most commonly applications have 3 distinct tiers or layers. They are:

• Presentation Layer
• Business Logic Layer
• Data Access Layer

As you can guess, presentation layer is nothing but a piece of software that deals with user interface of your application. Displaying data to the end user and allow them to interface with it is the core functionality of this layer.

In most of the cases the data entered by the end user needs some kind of validation or further processing. This is the responsibility of Business Logic Layer.

Finally, your application data needs to be stored and retrieved in some data store (RDBMS, XML etc.). This task is handled by Data Access Layer.

In short, the process works like this:

• User requests for some application data.
• The data access layer retrieves the data and is forwarded to the presentation layer via business logic layer. Sometimes data access layer gives this data directly to presentation layer.
• Presentation layer receives the data to be displayed via business logic layer.
• The user changes the data and initiates the appropriate action (such as insert, or update).
• The business logic layer validates the data submitted by the user.
• If the data is valid it is handed over to data access layer for updating into the database.

Advantages of N-Tier ArchitectureAt first glance this division of tasks may seem to be unnecessary. However, it gives following benefits:

• The applications gets divided in logically isolated pieces reducing tight coupling between the UI, business processes and database.
• Change in the underlying database and data access methods do not have any effect on the presentation layer or client application.
• Client application no longer has SQL statements embedded in it. This makes it de-coupled from rest of the application.
• Table and column names can be effectively eliminated from the client-side code.
• The client application is unaware from where data comes (location transparency).
• It becomes easier to modify or extend your application, without breaking or recompiling the client-side code.

The downside of n-tier architecture is that you need to create many isolated classes and pieces of software. However, benefits of n-tier applications will far outweigh its disadvantage.