Singleton Pattern — Concept Check
Questions on Singleton Pattern. Singleton ensures a class has exactly one instance. Java offers several implementations — from simple to thread-safe and serialization-safe.
Questions in this quiz
8 questions on Singleton Pattern — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.A developer is using the eager initialization singleton pattern in a Java application. What is a potential downside of this approach?
- AVulnerable to reflection attacks
- BDifficult to implement
- CRequires complex synchronization
- DInstance created even if never used
2.In a multi-threaded environment, which singleton implementation minimizes synchronization overhead while ensuring thread safety?
- APrototype scope
- BDouble-checked locking
- CLazy with synchronized
- DEager initialization
3.A developer claims that using an enum singleton in Java can lead to multiple instances during serialization. What is the reality?
- AEnum singleton is not recommended for serialization
- BEnum singleton is serialization-safe
- CEnum singleton creates multiple instances
- DEnum singleton requires manual serialization handling
4.Which approach allows lazy initialization of a singleton without explicit synchronization?
- AEager initialization
- BInitialization-on-demand holder
- CEnum singleton
- DDouble-checked locking
5.In a Spring application, what is the default scope for beans, and how does it relate to the singleton pattern?
- ASingleton scope, one instance per ClassLoader
- BPrototype scope, requires manual singleton implementation
- CPrototype scope, creates new instance per injection
- DSingleton scope, one instance per ApplicationContext
6.A developer notices that a singleton service in a Spring application is not behaving as expected. What could be a likely reason?
- AEnum singleton is not used
- BLazy initialization is causing delays
- CPrototype scope is used instead of singleton
- DSingleton scope is not thread-safe
7.Why is the enum singleton pattern considered robust against reflection attacks?
- AEnums cannot be instantiated via reflection
- BEnums require complex synchronization
- CEnums are lazily initialized
- DEnums are not subject to serialization issues
8.A developer uses synchronized lazy initialization for a singleton. What is a common performance issue with this approach?
- ARequires complex initialization logic
- BSynchronized access slows down every call
- CInstance created at class load time
- DInstance may not be thread-safe