Interview Questions

Java Collections Framework provides a well designed set of interfaces and classes that support operations on a collections of objects. The most basic interfaces that reside in the Java Collections Framework are:

Collection, which represents a group of objects known as its elements.

Set, which is a collection that cannot contain duplicate elements.

List, which is an ordered collection and can contain duplicate elements.

Map, which is an object that maps keys to values and cannot contain duplicate keys.

The main difference lies in the motive of the two parties. The main motive of the hedger is to hedge(minimize) the risk from the occurence of some events. 

The motive of the speculator is to gamble in the market in order to make the profit by buying/selling the derivative products.

Java uses primitive data types and hence is not a pure object oriented language.

In contrast to investment, consumption is relatively stable.

Business facts or measures and foreign keys are persisted in fact tables which are referred as candidate keys in dimension tables. Additive values are usually provided by the fact tables which acts as independent variables by which dimensional attributes are analyzed.

Attributes that are used to constrain and group data for performing data warehousing queries are persisted in the dimension tables.

sort() , rsort(), asort()
ksort()   , usort()
arsort()  , uksort()
natsort() , natcasesort()
array_multisort()

Internal marketing is the process of motivating and empowering the employees of a company to work as a team for the overall well-being of the customers and thereby the company itself. This is actually the core to succes of a company. A harmonised effort  within the company is an utmost necessity to provide customers with services at a desired level. If a firm doesn't deliver the service it promises in its marketing campaign, it will fail for sure. And it only can keep that promise when all of its employees at all levels realise what actually it is going to deliver. 

 Test scenarios are derived from requirement documents. We follow each and every functionality (called business rules) mentioned in the requirement document. One functionality can have multiple business rules. For example, let us say in there is one requirement called “Login”. This “Login” may have various scenarios. For example, one scenario is, enter the right User ID and wrong password. The system should display an error message. Another scenario would be to enter wrong User ID and right Password. The system should display an error message. The third scenario could be to enter the right User Name and right Password. The system should allow the user to get into the system. This is how the test cases are derived from the requirement documents or from the Use Cases.