3V0-32.23 · Question #52
An architect is completing the physical design for a vRealize Operation (vROps) solution for a customer. The customer has only provided the following information for their existing environment…
The correct answer is A. The vROps cluster will be configured as High Availability. B. The RTO of the vROps solution will be 4 hours. A and B are correct because vROps is a management component, so the customer's stated 4-hour RTO applies directly to it (B), and to actually achieve that RTO, the architect must assume HA will be configured - HA directly impacts cluster sizing by requiring additional nodes (A)…
Question
An architect is completing the physical design for a vRealize Operation (vROps) solution for a customer. The customer has only provided the following information for their existing environment:
- 500 Virtual Machines
- 2 VMware vCenter Servers
- 10 VMware vSphere Horsts
- 20 Datastores
- Live data should be stored within the vROps solution for 6 months
- The RTO for all existing management components is 4 hours
- The RTO for all existing management components is 1 hour
Which two assumptions could the architect make when sizing the vROps cluster? (Choose two.)
Options
- AThe vROps cluster will be configured as High Availability.
- BThe RTO of the vROps solution will be 4 hours.
- CThe resource profile of a virtual machine will be, on average, 1 vCPU and 2 GB RAM.
- DThe minimum data retention within vRealize Operations Cluster will be 12 months.
- EThe RPO of the vROps solution will be 1 hour.
How the community answered
(42 responses)- A79% (33)
- C2% (1)
- D12% (5)
- E7% (3)
Explanation
A and B are correct because vROps is a management component, so the customer's stated 4-hour RTO applies directly to it (B), and to actually achieve that RTO, the architect must assume HA will be configured - HA directly impacts cluster sizing by requiring additional nodes (A).
Why the distractors are wrong:
- C - No VM resource profile data was provided; assuming 1 vCPU / 2 GB RAM is unsupported speculation and would produce an unreliable sizing result.
- D - The customer explicitly stated 6 months of live data retention; doubling it to 12 months contradicts the given requirements.
- E - While the customer's RPO is 1 hour, RPO governs backup frequency/recovery point, not cluster node count. It does not drive vROps cluster sizing the way RTO does, and vROps HA does not inherently guarantee a 1-hour RPO without additional backup tooling.
Memory tip: Think of it as a chain - RTO stated for management components → vROps inherits that RTO (B) → to meet that RTO, HA must be assumed → HA affects sizing (A). RPO and retention are real concerns, but neither directly determines how many nodes you need in the cluster.
Topics
Community Discussion
No community discussion yet for this question.