3V0-32.23 · Question #22
A customer wants to implement vRealize Suite Lifecycle Manager (vRSLCM) as a part of a new SDDC deployment. - The customer has two physical data centers and number of branch offices. - The customer…
The correct answer is C. Deploy a vRSLCM appliance on a vSAN stretched cluster. Deploying a single vRSLCM appliance on a vSAN stretched cluster (option C) is correct because vRSLCM is a single-node appliance - it cannot be natively clustered - and a vSAN stretched cluster spans both physical data centers, providing automatic failover if one site goes down…
Question
A customer wants to implement vRealize Suite Lifecycle Manager (vRSLCM) as a part of a new SDDC deployment.
- The customer has two physical data centers and number of branch
offices.
- The customer has recently purchased Hyper-converged Infrastructure
(HCI) hardware that has to be implemented and configured.
- The customer has a target availability Service Level Agreement (SLA)
of 99.99%, measured quarterly, for the management components. Which recommendation should the architect make to achieve the requirements?
Options
- ADeploy a 3-node vRSLCM cluster on a vSAN stretched cluster
- BDeploy a vRSLCM appliance in one DC and replicate it to the second DC
- CDeploy a vRSLCM appliance on a vSAN stretched cluster
- DDeploy a vRSLCM appliance on a vSAN cluster
How the community answered
(54 responses)- A11% (6)
- B2% (1)
- C81% (44)
- D6% (3)
Explanation
Deploying a single vRSLCM appliance on a vSAN stretched cluster (option C) is correct because vRSLCM is a single-node appliance - it cannot be natively clustered - and a vSAN stretched cluster spans both physical data centers, providing automatic failover if one site goes down. This architecture leverages the newly purchased HCI hardware and delivers the cross-site redundancy needed to meet a 99.99% availability SLA (roughly 13 minutes of allowable downtime per quarter).
Option A is wrong because vRSLCM has no supported multi-node cluster mode; a "3-node vRSLCM cluster" is not a valid deployment option regardless of underlying infrastructure.
Option B is wrong because replication is a DR strategy, not an HA strategy - failover from replication involves manual steps and recovery time that would easily exceed the 13-minute quarterly budget, violating the SLA.
Option D is wrong because a standard vSAN cluster is confined to a single DC; a complete site outage would take down the appliance with it, which fails the cross-site availability requirement.
Memory tip: The keyword is "stretch" - whenever you see 99.99% SLA + two physical data centers + HCI, think stretched cluster for site-level resilience. If the product is an appliance (like vRSLCM), it rides the stretched cluster rather than forming its own.
Topics
Community Discussion
No community discussion yet for this question.