An organization is seeking to implement a hot site and wants to maintain a live database server at the backup site. Which of the following solutions will be the best for the organization?

Question

Options

• AElectronic vaulting
• BRemote journaling
• CRemote mirroring
• DTransaction logging

• A
  14% (5)
• B
  3% (1)
• C
  77% (27)
• D
  6% (2)

Explanation

Remote mirroring is the correct choice because it creates a real-time, synchronous copy of the entire database at the backup site - meaning the hot site's database server is always live, current, and immediately usable in the event of a failover.

Electronic vaulting (A) bulk-transfers data backups to an offsite location on a schedule (like nightly), so it's not real-time and would result in data loss between transfers. Remote journaling (B) ships transaction logs to the remote site at intervals, but those logs still need to be applied to a local database - the remote DB isn't instantly live. Transaction logging (D) is a local recovery mechanism that records database changes for rollback/replay purposes; it's not a replication strategy at all.

Memory tip: Think of the word "mirror" - a mirror reflects exactly what's in front of it in real time. Remote mirroring = real-time replica = hot site ready. If the answer involves "live" or "immediate," mirror is your word.

No community discussion yet for this question.