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.

An objective person can compartmentalize their feelings, and has to in order to be objective. They cannot let their feelings get in the way of their thought processes. They rely on data and facts, not emotion when considering things. Depending on what the "question" is, they may consider the emotions of themselves and others as "factors" but do not allow them to control their thinking.

If a person is getting all emotional, if they're making fast defensive statements, they're not being objective. They may be "rational" but that is not the same thing as objective.

One of the Merriam Webster definitions of objective is: "expressing or dealing with facts or conditions as perceived without distortion by personal feelings, prejudices, or interpretations"

My Answer: No. I find that objective people, are usually,very difficult to have a sensible discussion with.
Most things in life are subjective and anybody who isn't aware of this, is probably, very young, or very limited in their perception and experience, of life.

A database index is a data structure that improves the speed of operations in a table. Indices can be created using one or more columns, providing the basis for both rapid random lookups and efficient ordering of access to records. The disk space required to store the index is typically less than the storage of the table (since indices usually contain only the key-fields according to which the table is to be arranged, and excludes all the other details in the table), yielding the possibility to store indices into memory from tables that would not fit into it. In a relational databasean index is a copy of part of a table. Some databases extend the power of indexing by allowing indices to be created on functions or expressions. For example, an index could be created on upper(last_name), which would only store the uppercase versions of the last_name field in the index. Another option sometimes supported is the use of "filtered" indices, where index entries are created only for those records that satisfy some conditional expression. A further aspect of flexibility is to permit indexing on user-defined functions, as well as expressions formed from an assortment of built-in functions.

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