Interview Questions

You can prevent a class from overriding in C# by using the sealed keyword; whereas, the NotInheritable keyword is used to prevent a class from overriding in Visual Basic.

This question is designed to see how well you can mediate a situation and handle conflict. You want to come across as someone who can compromise when necessary. An interviewer wants to see that you can not only reach an outcome that is desirable for both sides of a conflict of interest, but also that you can understand where the other person is coming from. Empathy and understanding go a long way in any job and this is a good opportunity to show that you can put yourself in another’s shoes.

A Product Roadmap is a plan that matches short-term and long-term business goals with specific technology solutions to help meet those goals. It is a high-level visual summary that maps out the vision and direction of your product offering over time.

1. A product roadmap communicates the why and what behind what you're building.

2. It's a guiding strategic document as well as a plan for executing the strategy.

3. Roadmapping is the exercise of building a product roadmap. Roadmaps can apply to new products or services or existing offerings.

Generally a business analyst covers several stages in Software Development Life Cycle.

Like:  Client Consulting, Client Requirement Study, Planning for business needs, Business Requirement Documenting, Work on functional requirement, Prepare test data with inputs from end users, Document use case scenarios, Help Testing team with test plan and testing, Help end users with user acceptance testing UAT, Go live and post production support tasks.

The purpose of garbage collection is to identify and discard objects that are no longer needed by a program so that their resources can be reclaimed and reused. A Java object is subject to garbage collection when it becomes unreachable to the program in which it is used.

bcoz interface does not contains any initializers and constructors to initialize its data members.

- Fail-safe approach defines the level that divides the security such that it is safe even in case the system is failed.

- The fail safe approach doesn’t allow an attacker to take the advantage by breaking in the system and crashes out.

- This approach allows the web server to perform the routines even if the system runs out of the memory in case of any attack. 

- The system in attacks doesn’t skip the access to the control check or it doesn’t skip serving any document requested. 

- Fail safe approach can force the web server to run of the memory and have a DoS attack.