RBS Java Programming Interview Questions

Upasana | August 10, 2019 | 2 min read | 1,344 views | investment banking

In this article we will focus on java programming interview questions that are frequently covered in RBS investment banking interviews.

The main focus of Java Interviews in RBS for investment banking domain is on:

Core Java: multi-threading & concurrency concepts, executor framework, object oriented programming, inheritance, exception handling, generics and collections.
Algorithms and data structures: time and space complexity of algorithms, sorting algorithms, hashing data structures, binary trees, etc.
Design patterns: Singleton, factory method, Flyweight, Decorator, Chain of responsibility, Strategy and Visitor design patterns.
RDBMS concepts: Type of indexes, Left and Right Joins, Outer and Inner Join, Sharding, Query optimization.
Puzzles

Written Test Java Questions

What is the strategy to handle ConcurrentModificationException in your Java program?
What will be behavior of a Java Program where infinite recursion takes place with limited Stack memory? Does the program complete or Stackoverflow exception is thrown?
Comparable vs Comparator? when should I choose one over the another?
How will you remove duplicate records from a database table? Will group by clause help?

How does serialization takes place in Java? What is purpose of externalizable interface? What are transient variables?
Why most of methods in Collections class declared as static?
What is difference between overloading and overriding? What is hiding of members and methods - both static and instance one?
Method overloading rules in Java
What is ThreadLocal class used for?
What is purpose of Classloader provided by Java? What is effect of multiple classloaders on Singleton Class?
NoClassDefFoundError vs ClassNotFoundException?
What is proxy design pattern? What is it’s practical usage?

How will you design a caching implementation where items in cache needs to be expired (deleted from memory) after age of 5 minutes irrespective of the access timing?
Normally its not a good practice to add additional thread for cache cleanup, so better is to cleanup resource using clever mechanisms during the access time. It lowers complexity and resource usage at some extra cost of access time. Google Guava library does something similar in its cache library.
How will you design your own custom thread pool in Java? Don’t use the one provided by JDK.
What do you understand by Producer Consumer Problem?

Buy my ebook for complete question bank

Most of these questions has been answered in my eBook "Cracking the Core Java Interview" updated on June 2018, that you can buy from this link: