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

- Free Preparation Discussions

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

Actual exam question for VMware's 2V0-72.22 exam

Question #: 26
Topic #: 11

[All 2V0-72.22 Questions]

Which is the correct approach to register for a bean destruction callback?

AAnnotate the callback method with @PostDestroy.

BAnnotate the callback method with @PreDestroy.

CAdd the @Lazy annotation to the bean configuration.

DConfigure the bean instance to use prototype scope.

Show Suggested Answer

Suggested Answer: C

by Donette at Feb 24, 2023, 06:08 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Lonna

11 months ago

Wait, can you really use prototype scope for this? Sounds off.

upvoted 0 times

...

Rima

11 months ago

I agree with A, but I’m surprised it’s not more commonly known.

upvoted 0 times

...

Phuong

11 months ago

C makes no sense here, @Lazy is for initialization.

upvoted 0 times

...

Hui

11 months ago

I thought it was B, @PreDestroy is for cleanup before destruction, right?

upvoted 0 times

...

Myrtie

11 months ago

Definitely A, @PostDestroy is the way to go!

upvoted 0 times

...

Nu

12 months ago

I don’t think C or D are related to destruction callbacks, but I can’t recall the exact definitions right now.

upvoted 0 times

...

Nathan

12 months ago

I feel like I’ve seen @PostDestroy used in examples, but I’m confused about whether it’s for cleanup or initialization.

upvoted 0 times

...

Roy

12 months ago

I remember practicing a question about lifecycle annotations, and I think @PreDestroy was mentioned a lot. So maybe B is the right choice?

upvoted 0 times

...

Princess

12 months ago

I think the correct answer might be A, but I’m not entirely sure if it’s specifically for destruction callbacks.

upvoted 0 times

...

Paz

12 months ago

Okay, let's break this down. If the primary Delivery Controllers are turned off, the VDAs should re-register with the passive data center. And GSLB should redirect connections there as well. I think I've got a good handle on this.

upvoted 0 times

...

Alisha

12 months ago

This question seems straightforward, but I want to make sure I understand the key details before answering. The company's earnings and the P/E ratios of similar companies are provided, so I'll need to calculate the company's valuation and compare it to the current share price.

upvoted 0 times

...

Jose

12 months ago

Hmm, I'm a little unsure about this one. I'll need to think through the differences between authority, involvement, influence, and interest to make sure I select the right answer.

upvoted 0 times

...

Odette

12 months ago

I'm a bit uncertain about A—doesn't the budget compare actuals to previous plans rather than just acting as a variable mechanism?

upvoted 0 times

...

Cruz

12 months ago

Okay, let's think this through. The key requirements are data stored on multiple nodes in separate geographic locations, with the ability to read from the secondary location. I believe Geo-redundant storage would be the best fit here.

upvoted 0 times

...

Lou

1 year ago

I'd like to register a bean destruction callback for my sense of humor. It seems to be self-destructing after reading these answer choices.

upvoted 0 times

Cassie

1 year ago

C) Add the @Lazy annotation to the bean configuration.

upvoted 0 times

...

Cortney

1 year ago

B) Annotate the callback method with @PreDestroy.

upvoted 0 times

...

Alease

1 year ago

A) Annotate the callback method with @PostDestroy.

upvoted 0 times

...

...

Sharee

1 year ago

D) Prototype scope? What does that have to do with bean destruction callbacks? Clearly, I need to review my Spring annotations.

upvoted 0 times

...

Antonette

1 year ago

C) @Lazy? Really? That's not related to bean destruction at all. Gotta be more careful with these tricky options.

upvoted 0 times

Felicidad

1 year ago

D) Configure the bean instance to use prototype scope.

upvoted 0 times

...

Rosenda

1 year ago

B) Annotate the callback method with @PreDestroy.

upvoted 0 times

...

Precious

1 year ago

A) Annotate the callback method with @PostDestroy.

upvoted 0 times

...

...

Dierdre

1 year ago

Hmm, I was wondering if @PostDestroy would work, but you're right, @PreDestroy is the way to go. Thanks for the clarification!

upvoted 0 times

Sharen

1 year ago

Hmm, I was wondering if @PostDestroy would work, but you're right, @PreDestroy is the way to go. Thanks for the clarification!

upvoted 0 times

...

Alesia

1 year ago

B) Annotate the callback method with @PreDestroy.

upvoted 0 times

...

Cyndy

1 year ago

A) Annotate the callback method with @PreDestroy.

upvoted 0 times

...

...

Tenesha

1 year ago

B) Annotate the callback method with @PreDestroy. That's the correct way to register a bean destruction callback.

upvoted 0 times

Maynard

1 year ago

A) Annotate the callback method with @PostDestroy.

upvoted 0 times

...

Derick

1 year ago

B) Annotate the callback method with @PreDestroy.

upvoted 0 times

...

...

Jeannine

1 year ago

But doesn't @PreDestroy ensure that the callback method is called before the bean is destroyed?

upvoted 0 times

...

Glen

1 year ago

I disagree, I believe the correct approach is to configure the bean instance to use prototype scope.

upvoted 0 times

...

Jeannine

1 year ago

I think the correct approach is to annotate the callback method with @PreDestroy.

upvoted 0 times

...