Q: 20
Which factor most directly influences RTO in DR design?
Options
Discussion
B . The others are just distractors, patch panels aren't a core RTO driver in DR design.
Maybe D for this one. If you have too many patch panels, cabling gets messy and that could slow things down during DR when you're trying to trace connections or fix an issue. I think that's still a physical bottleneck to getting systems back up fast. Not positive but seems logical in some setups, right?
B tbh. Automation and where your backup data lives are what actually cuts down your recovery time. Official guides and practice exams always emphasize those two for RTO, not stuff like patch panels or rack color. Anyone disagree?
Nah, I think it's B. The other options are more distractions but automation and data location really set your RTO.
So wouldn't automation let you recover fast even if your data is farther away, or does proximity matter more than orchestration?
What if the data is replicated offsite but high latency links slow down access, wouldn’t that stretch RTO even with automation? Seems like proximity could be the real tie breaker here, not just orchestration speed.
Its D, since patch panels could impact physical connectivity during recovery. A is just a trap.
B tbh, but I'd checked a practice exam-automation and where your data sits really decide how fast you come back online. Official guides usually hit RTO with those factors so pretty sure this is the go-to pick.
Wouldn't A actually matter if the whole ops team went for coffee at failover? A
Be respectful. No spam.
