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

VMware Exam 1V0-31.21 Topic 9 Question 76 Discussion

Actual exam question for VMware's 1V0-31.21 exam
Question #: 76
Topic #: 9
[All 1V0-31.21 Questions]

An administrator has been tasked with ensuring that all deployments for a development project are automatically shutdown and deleted 30 days after they created in an effort to reclaim unused resources.

Which type of policy should the administrator create to achieve this goal?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Ilene
2 days ago
Lease, lease, lease! This is a no-brainer. They might as well have asked, 'What's the best way to ensure your cloud resources don't become a never-ending money pit?' Lease FTW!
upvoted 0 times
...
Gertude
3 days ago
Resource quota? Really? That's for managing limits, not automatically deleting resources. Approval? No way, who wants to wait for someone to approve shutdowns? A all the way!
upvoted 0 times
...
Leota
5 days ago
Hmm, I'm not so sure. Day 2 Action might also work, but it doesn't feel as straightforward as just setting a lease. I'll go with A on this one.
upvoted 0 times
...
Myong
9 days ago
Definitely option A - Lease. That's the perfect way to ensure resources are automatically shut down and deleted after a set time period. Gotta keep those cloud costs in check, am I right?
upvoted 0 times
...
Izetta
18 days ago
I'm not sure, but I think a Day 2 Action policy could also work for this scenario.
upvoted 0 times
...
Nadine
23 days ago
I agree with Lennie. A Lease policy would automatically shutdown and delete deployments after 30 days.
upvoted 0 times
...
Lennie
26 days ago
I think the administrator should create a Lease policy for this.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77