Q: 15
A customer is designing a multi-site VMware Cloud Foundation (VCF) and vSAN Data Protection (DP)
architecture to ensure business continuity. The customer's support team must validate the failover
and recovery processes before being allowed to deploy into production.
Which two validation activities should be included in the strategy to meet the objective? (Choose
two.)
Options
Discussion
B and D imo
C or D for me. Testing generic best practices (C) and running failover tests (D) both sound valid, but I thought C would help reduce mistakes if everyone follows the same approach. Not 100 percent sure though, could be missing the need for deep dependency checks.
B/D tbh, that covers both app dependencies and real failover testing.
Had something like this in a mock, B and D fit best. You need to actually check dependencies and connectivity between sites (B), plus run both planned and unplanned failover tests (D) to be sure recovery really works. Pretty sure about this combo but open if someone sees it differently.
I don't think it's A or E. B and D cover the real validation steps: checking dependencies/connectivity and running actual failover tests, not just relying on config or annual reviews. Anyone see a reason to pick C over B?
B/D tbh, they're the only ones that line up with validating pre-prod failover and recovery.
Gotta disagree with C here. Both B and D are solid since you really need to check app dependencies and actually run through failover scenarios, not just go with standard best practices. Pretty sure that's what VMware expects for pre-prod validation, but open to discuss.
I'd say C and D.
Isn't C just simplifying too much? Validation needs actual failover testing and application/dependency checks, not just best practices.
Call it B and D. I see C could trip people up since best practices are tempting, but for actual pre-prod validation you need to look at dependencies and actually test failover. Makes more sense to me, unless I'm missing something.
Be respectful. No spam.
