3V0-32.23 · Question #9
A company has recently completed an audit and has found that there are many virtual machines in their production environment which no longer appear to be in use. To prevent this from happening in…
The correct answer is B. Create a lease policy with the organization scope, setting 90 days lease, 365 total lease and. Option B is correct because it uses organization scope, which applies the lease policy across all projects as a company-wide default - this is what enables the "case-by-case override" behavior, since lower-level (project or deployment) settings can override an…
Question
A company has recently completed an audit and has found that there are many virtual machines in their production environment which no longer appear to be in use. To prevent this from happening in future, the company is deploying vRealize Automation and would like all provisioned VMs to meet following requirements:
- VMs to have a default lease of 90 days and no more than 365 days
- Lease policy can be overridden on case by case basis
- Upon initial lease expiry, the VM should be kept for 10 days after
which they will be destroyed Which policy design will meet the technical requirements?
Options
- ACreate a lease policy with the organization scope, setting 90 days lease, 365 total lease and
- BCreate a lease policy with the organization scope, setting 90 days lease, 365 total lease and
- CCreate a lease policy with the project scope, setting 90 days lease, 365 total lease and grace
- DCreate a lease policy with the project scope, setting 90 days lease, 365 total lease and grace
How the community answered
(29 responses)- A14% (4)
- B76% (22)
- C3% (1)
- D7% (2)
Explanation
Option B is correct because it uses organization scope, which applies the lease policy across all projects as a company-wide default - this is what enables the "case-by-case override" behavior, since lower-level (project or deployment) settings can override an organization-level policy. It correctly configures a 90-day default lease, a 365-day maximum total lease, and a 10-day grace period, which keeps the VM alive after initial expiry before it is permanently destroyed.
Option A is wrong because, while it also uses organization scope, it likely omits the 10-day grace period, meaning VMs would be destroyed immediately upon lease expiry rather than after 10 days.
Options C and D are wrong because they use project scope, which would only apply the policy to a single project rather than the entire production environment - a company-wide requirement demands organization-level scope. Additionally, project-scoped policies cannot be overridden at a lower level in the same flexible way.
Memory tip: Think "Org scope = company-wide umbrella with holes (overrides); grace period = the VM's last chance." If the question mentions company-wide defaults + per-case overrides, always choose organization scope; if it mentions a survival window after expiry, that's a grace period setting.
Topics
Community Discussion
No community discussion yet for this question.