Top 20 Core Java Interview Questions and Answers from Investment Banks (original) (raw)

Core Java Interview Question Answer
This is a new series of sharing core Java interview questions and answer on the Finance domain and mostly on big Investment banks. Many of these Java interview questions are asked on JP Morgan, Morgan Stanley, Barclays, or Goldman Sachs. Banks mostly asked core Java interview questions from multi-threading, collection, serialization, coding and OOPS design principles. Anybody who is preparing for any Java developer Interview on any Investment bank can be benefited from this set of core Java Interview questions and answers. I have collected these Java questions from my friends and I thought to share them with you all.

I hope this will be helpful for both of us. It's also beneficial to practice some programming interview questions because, in almost all Java interviews, there are at least 1 or 2 coding questions appear. Please share answers for unanswered Java interview questions and let us know how good these Java interview questions are?

If you are seriously preparing for Java Interviews and attending interviews, then I also suggest taking a look at these Java interview online courses and books. This is the Java-specific book modeled on their earlier bestseller, also about programming interviews.

This book contains questions not just from Java but also from related technology stacks like JUnit, Maven, Design Patterns, JVM Internals, Android, and Best practices. Questions are good and answers are crisp and very well explained, which makes it an interesting to read as well.

20+ Core Java Interview Questions Answers

These Java interview questions are a mix of easy, tough, and tricky Java questions e.g. Why multiple inheritance is not supported in Java is one of the tricky questions in java. Most questions are asked on Senior and experienced levels i.e. 3, 4, 5, or 6 years of Java experience e.g. How HashMap works in Java, which is most popular on experienced Java interviews.

By the way, recently I was looking at answers and comments made on Java interview questions given in this post and I found some of them quite useful to include in the main post to benefit all.

By the way apart from blogs and articles, you can also take advantage of some books and online courses, which are specially written for clearing any programming interviews and some focused on Java programming, two books that come to mind are Cracking the Coding Interview and Programming Interviews Exposed.

Both books and courses are focused on programming in general and a lot of other related topics e.g. data structures, algorithms, database, SQL, networking, and behavioral questions, but also contain Java concepts.

Question 1: What’s wrong with using HashMap in the multi-threaded environment? When get() method go to the infinite loop? (answer)
Well, nothing is wrong, it depends upon how you use it. For example, if you initialize the HashMap by just one thread and then all threads are only reading from it, then it's perfectly fine. One example of this is a Map that contains configuration properties.

The real problem starts when at least one of those threads is updating HashMap i.e. adding, changing, or removing any key-value pair. Since put() operation can cause re-sizing and which can further lead to an infinite loop, that's why either you should use Hashtable or ConcurrentHashMap, later is better.

Question 2. Does not overriding hashCode() method has any performance implication? (answer)
This is a good question and open to all, as per my knowledge, a poor hashcode function will result in the frequent collision in HashMap which eventually increases the time for adding an object into HashMap.

From Java 8 onwards though collision will not impact performance as much as it does in earlier versions because after a threshold the linked list will be replaced by the binary tree, which will give you O(logN) performance in the worst case as compared to O(n) of linked list.

Question 3: Does all property of Immutable Object needs to be final? (answer)

Not necessary, as stated above you can achieve the same functionality by making members non-final but private and not modifying them except in the constructor. Don't provide a setter method for them and if it is a mutable object, then don't ever leak any reference for that member.

Remember making a reference variable final, only ensures that it will not be reassigned a different value, but you can still change individual properties of an object, pointed by that reference variable. This is one of the key points, Interviewer likes to hear from candidates.

Question 4: How does substring () inside String works? (answer)

Another good Java interview question, I think the answer is not sufficient, but here it is “Substring creates a new object out of source string by taking a portion of original string”. This question was mainly asked to see if the developer is familiar with the risk of memory leak, which sub-string can create.

Until Java 1.7, substring holds the reference of the original character array, which means even a sub-string of 5 characters long, can prevent 1GB character array from garbage collection, by holding a strong reference.

This issue is fixed in Java 1.7, where the original character array is not referenced anymore, but that change also made the creation of substring a bit costly in terms of time. Earlier it was in the range of O(1), which could be O(n) in the worst case on Java 7.

Question 5: Can you write critical section code for the singleton? (answer)
This core Java question is a follow-up of the previous question and expecting the candidate to write Java singleton using double-checked locking. Remember to use the volatile variable to make Singleton thread-safe. Here is the code for critical section of a thread-safe Singleton pattern using double checked locking idiom:

public class Singleton {

private static volatile Singleton _instance;

/**
 * Double checked locking code on Singleton
 * @return Singelton instance
 */
public static Singleton getInstance() {
    if (_instance == null) {
        synchronized (Singleton.class) {
            if (_instance == null) {
                _instance = new Singleton();
            }
        }
    }
    return _instance;
}

}

Question 6: How do you handle error conditions while writing stored procedures or accessing stored procedures from java? (answer)

This is one of the tough Java interview questions and it's open for all, my friend didn't know the answer so he didn't mind telling me. My take is that stored procedure should return an error code if some operation fails but if the stored procedure itself fails then catching SQLException is the only choice.

Question 7 : What is difference between Executor.submit() and Executer.execute() method ? (answer)

This Java interview question is from my list of Top 15 Java multi-threading question answers, It's getting popular day by day because of the huge demand for Java developers with good concurrency skills. The answer to this Java interview question is that former returns an object of Future which can be used to find results from worker thread)

There is a difference when looking at exception handling. If your tasks throw an exception and if it was submitted with executing this exception will go to the uncaught exception handler (when you don't have provided one explicitly, the default one will just print the stack trace to System.err).

If you submitted the task with submit() any thrown exception, checked exception or not, is then part of the task's return status. For a task that was submitted with submitting and that terminates with an exception, the Future.get() will re-throw this exception, wrapped in an ExecutionException.

Question 8: What is the difference between a factory and abstract factory patterns? (answer)

Abstract Factory provides one more level of abstraction. Consider different factories each extended from an Abstract Factory and responsible for the creation of different hierarchies of objects based on the type of factory. E.g. AbstractFactory extended by AutomobileFactory, UserFactory, RoleFactory, etc. Each individual factory would be responsible for the creation of objects in that genre.

Here is a UML diagram of factory and abstract factory pattern:

Question 9: What is Singleton? is it better to make the whole method synchronized or only critical section synchronized? (answer)

Singleton in Java is a class with just one instance in whole Java application, for example, java.lang.Runtime is a Singleton class. Creating Singleton was tricky prior Java 4 but once Java 5 introduced Enum its very easy. see my article How to create thread-safe Singleton in Java for more details on writing Singleton using the enum and double checked locking which is the purpose of this Java interview question.

Question 10: Can you write code for iterating over HashMap in Java 4 and Java 5? (answer)
Tricky one but he managed to write using while and a for loop. Actually, there are four ways to iterate over any Map in Java, one involves using keySet() and iterating over key and then using get() method to retrieve values, which is bit expensive.

The second method involves using entrySet() and iterating over them either by using for each loop or while with Iterator.hasNext() method. This one is a better approach because both key and value object are available to you during Iteration and you don't need to call get() method for retrieving the value, which could give the O(n) performance in case of huge linked list at one bucket. See my post 4 ways to iterate over Map in Java for detailed explanation and code examples.

Question 11 : When do you override hashCode() and equals()? (answer)
Whenever necessary especially if you want to do an equality check based upon business logic rather than object equality e.g. two employee objects are equal if they have the same emp_id, despite the fact that they are two different objects, created by a different parts of the code. Also overriding both these methods are a must if you want to use them as key in HashMap.

Now as part of the equals-hashcode contract in Java, when you override equals, you must override hashcode as well, otherwise, your object will not break invariant of classes e.g. Set, Map which relies on equals() method for functioning properly. You can also check my post 5 tips on equals in Java to understand subtle issue which can arise while dealing with these two methods.

Question 12:. What will be the problem if you don't override hashCode() method? (answer)
If you don't override the equals method, then the contract between equals and hashcode will not work, according to which, two objects which are equal to equals() must have the same hashcode. In this case, another object may return different hashCode and will be stored in that location, which breaks the invariant of the HashMap class because they are not supposed to allow duplicate keys.

When you add the object using the put() method, it iterates through all Map.Entry object present in that bucket location, and update value of the previous mapping, if Map already contains that key. This will not work if the hashcode is not overridden.

Question 13 : Is it better to synchronize critical section of getInstance() method or whole getInstance() method? (answer)
The answer is only a critical section because if we lock the whole method that every time someone calls this method, it will have to wait even though we are not creating any object. In other words, synchronization is only needed, when you create an object, which happens only once.

Once an object has been created, there is no need for any synchronization. In fact, that's very poor coding in terms of performance, as the synchronized methods reduce performance up to 10 to 20 times.

Here is a UML diagram of the Singleton pattern:

By the way, there are several ways to create a thread-safe singleton in Java, which you can also mention as part of this question or any follow-up.

Question 14: Where does equals() and hashCode() method comes in the picture during the get() operation? (answer)
This core Java interview question is a follow-up of a previous Java question and the candidate should know that once you mention hashCode, people are most likely ask, how they are used in HashMap.

When you provide a key object, first its hashcode method is called to calculate bucket location. Since a bucket may contain more than one entry as a linked list, each of those Map.Entry object is evaluated by using equals() method to see if they contain the actual key object or not.

Questions 15: How do you avoid deadlock in Java? (answer)
You can avoid deadlock by breaking circular wait conditions. In order to do that, you can make arrangements in the code to impose the ordering on the acquisition and release of locks. If the lock will be acquired in a consistent order and released in just the opposite order, there would not be a situation where one thread is holding a lock that is acquired by another and vice-versa. See the detailed answer for the code example and a more detailed explanation.

Question 16: What is the difference between creating String as new() and literal? (answer)
When we create the string with a new() Operator, it’s created in heap and not added into string pool while String created using literal are created in String pool itself which exists in the PermGen area of heap.

String str = new String("Test")

does not put the object str in the String pool, we need to call String.intern() method which is used to put them into the String pool explicitly. It's only when you create String object as String literal e.g. String s = "Test" Java automatically put that into String pool.

By the way, there is a catch here Since we are passing arguments as "Test", which is a string literal, it will also create another object as "Test" on the string pool. This is the one point, which has gone unnoticed until knowledgeable readers of the Javarevisited blog suggested it. To learn more about the difference between String literal and String object, see this article.

Here is a nice image that shows this difference quite well:

Question 17: What is an Immutable Object? Can you write Immutable Class? (answer)
Immutable classes are Java classes whose objects can not be modified once created. Any modification in Immutable object results in a new object. For example, String is immutable in Java.

Mostly Immutable classes are also final in Java, in order to prevent subclasses from overriding methods, which can compromise Immutability. You can achieve the same functionality by making members non-final but private and not modifying them except in the constructor.

Apart from the obvious, you also need to make sure that, you should not expose the internals of an Immutable object, especially if it contains a mutable member. Similarly, when you accept the value for the mutable member from the client e.g. java.util.Date, use clone() method keep a separate copy for yourself, to prevent the risk of malicious client modifying mutable reference after setting it.

The Same precaution needs to be taken while returning value to a mutable member, return another separate copy to the client, never return original reference held by Immutable class. You can see my post How to create an Immutable class in Java for step-by-step guides and code examples.

Question 18: Give the simplest way to find out the time a method takes for execution without using any profiling tool? (answer)
Read the system time just before the method is invoked and immediately after the method returns. Take the time difference, which will give you the time taken by a method for execution.

To put it in code…

long start = System.currentTimeMillis (); method (); long end = System.currentTimeMillis ();

System.out.println (“Time taken for execution is ” + (end – start));

Remember that if the time taken for execution is too small, it might show that it is taking zero milliseconds for execution. Try it on a method which is big enough, in the sense the one which is doing a considerable amount of processing

Question 19: Which two methods do you need to implement to use any Object as a key in HashMap? (answer)
In order to use any object as a Key in HashMap or Hashtable, it must implement the equals and hashcode method in Java. Read How HashMap works in Java for a detailed explanation of how the equals and hashcode method is used to put and get an object from HashMap.

Question 20: How would you prevent a client from directly instantiating your concrete classes? For example, you have a Cache interface and two implementation classes MemoryCache and DiskCache, How do you ensure there is no object of these two classes is created by the client using the new() keyword.

I leave this question for you to practice and think about before I give the answer. I am sure you can figure out the right way to do this, as this is one of the important decisions to keep control of classes in your hand, great from a maintenance perspective.

I am also very grateful to my readers who have generously contributed several good questions from Java Interviews for both beginners and experienced developers alike. I have already answered many of these questions in this blog and you can easily find a relevant post by using the search box at the top right corner of this page.