Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

VMware 2V0-72.22 Exam - Topic 11 Question 67 Discussion

Refer to the exhibit.How can a Spring Bean be created from this LegacySingleton class?
A) Call LegacySingleton.getInstance() from within a @Bean method and return the instance.
B) Return an instance of LegacySingleton using the new keyword from a @Bean method.
C) It is not possible without modifying the LegacySingleton class, the constructor must be public.
D) Modify the LegacySingleton class by adding the @Autowired annotation to the instance variable.

VMware 2V0-72.22 Exam - Topic 11 Question 67 Discussion

Actual exam question for VMware's 2V0-72.22 exam
Question #: 67
Topic #: 11
[All 2V0-72.22 Questions]

Refer to the exhibit.

How can a Spring Bean be created from this LegacySingleton class?

Show Suggested Answer Hide Answer
Suggested Answer: A

by Heike at Feb 08, 2025, 06:53 PM

Limited Time Offer

25%

Off

Get Premium 2V0-72.22 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Matilda
10 months ago
Wait, is it really not possible without changing the constructor? That sounds odd!
upvoted 0 times
...
Merilyn
10 months ago
D seems like overkill, why modify the class?
upvoted 0 times
...
Jamal
10 months ago
C makes sense, can't create a bean with a private constructor.
upvoted 0 times
...
Zana
11 months ago
I think B could work too, but it's not ideal.
upvoted 0 times
...
Margery
11 months ago
A is definitely the way to go!
upvoted 0 times
...
Kandis
11 months ago
I feel like modifying the LegacySingleton class is a bit too much for this question, so I would lean towards option A as well.
upvoted 0 times
...
Lynda
11 months ago
I practiced a similar question where we had to create a bean from a singleton class, and I think we called a method to get the instance, like in option A.
upvoted 0 times
...
Dell
11 months ago
I'm not entirely sure, but I remember something about needing a public constructor for Spring to create beans. Maybe option C is correct?
upvoted 0 times
...
Brandon
12 months ago
I think option A makes the most sense since we can use the singleton pattern to get the instance.
upvoted 0 times
...
Hollis
12 months ago
I think the answer is to call the LegacySingleton.getInstance() method from within a @Bean method. That way, I can return the existing singleton instance to the Spring context.
upvoted 0 times
...
Leonor
12 months ago
I'm a bit confused on this one. The question mentions modifying the LegacySingleton class, but I'm not sure if that's the best approach. I'll need to review the Spring Bean lifecycle and how to handle existing singletons.
upvoted 0 times
...
Carman
12 months ago
Okay, let's see. The key here is that the LegacySingleton class is a singleton, so I'll need to find a way to leverage that in the Spring context.
upvoted 0 times
...
Keneth
12 months ago
Hmm, this looks like a tricky one. I'll need to think carefully about the Spring Bean creation process and how it interacts with the LegacySingleton class.
upvoted 0 times
...
Mitsue
2 years ago
Hold up, did anyone else notice the exhibit is just a picture of a dog? I'm so distracted now, I forgot the question. What were we talking about again?
upvoted 0 times
Filiberto
1 year ago
D) Modify the LegacySingleton class by adding the @Autowired annotation to the instance variable.
upvoted 0 times
...
Genevieve
1 year ago
C) It is not possible without modifying the LegacySingleton class, the constructor must be public.
upvoted 0 times
...
Wilda
1 year ago
B) Return an instance of LegacySingleton using the new keyword from a @Bean method.
upvoted 0 times
...
Anthony
2 years ago
A) Call LegacySingleton.getInstance() from within a @Bean method and return the instance.
upvoted 0 times
...
...
Becky
2 years ago
You know, if this was a real-world problem, I'd just rewrite the whole darn thing from scratch. Screw legacy code! Option D is my pick.
upvoted 0 times
...
Joana
2 years ago
C'mon, really? We can't modify the class? That's just lazy. Option B all the way!
upvoted 0 times
Selma
2 years ago
You're right, we can't modify the class. The correct answer is A) Call LegacySingleton.getInstance() from within a @Bean method and return the instance.
upvoted 0 times
...
Margurite
2 years ago
Option B is not the correct way to create a Spring Bean from this LegacySingleton class.
upvoted 0 times
...
...
Myrtie
2 years ago
I think option A is the way to go. Calling getInstance() from a @Bean method seems like the cleanest approach.
upvoted 0 times
Helene
2 years ago
User2: Yes, calling getInstance() from a @Bean method is the cleanest way to create a Spring Bean from LegacySingleton.
upvoted 0 times
...
Annita
2 years ago
User1: I agree, option A is the most appropriate solution here.
upvoted 0 times
...
...
Skye
2 years ago
But wouldn't adding the @Autowired annotation to the instance variable also work? That's option D.
upvoted 0 times
...
Annamaria
2 years ago
I disagree, I believe the answer is C. We need to modify the LegacySingleton class to make the constructor public.
upvoted 0 times
...
Skye
2 years ago
I think the answer is A, because we can call LegacySingleton.getInstance() from a @Bean method.
upvoted 0 times
...

Save Cancel