Not a Transaction Redundancy Implementation

A.

Three concepts are used to create a level of fault tolerance and redundancy in transaction processing.

They are Electronic vaulting, remote journaling and database shadowing provide redundancy at the transaction level.

Electronic vaulting is accomplished by backing up system data over a network.

The backup location is usually at a separate geographical location known as the vault site.

Vaulting can be used as a mirror or a backup mechanism using the standard incremental or differential backup cycle.

Changes to the host system are sent to the vault server in real-time when the backup method is implemented as a mirror.

If vaulting updates are recorded in real-time, then it will be necessary to perform regular backups at the off-site location to provide recovery services due to inadvertent or malicious alterations to user or system data.

Journaling or Remote Journaling is another technique used by database management systems to provide redundancy for their transactions.

When a transaction is completed, the database management system duplicates the journal entry at a remote location.

The journal provides sufficient detail for the transaction to be replayed on the remote system.

This provides for database recovery in the event that the database becomes corrupted or unavailable.

There are also additional redundancy options available within application and database software platforms.

For example, database shadowing may be used where a database management system updates records in multiple locations.

This technique updates an entire copy of the database at a remote location.

Reference used for this question: Hernandez CISSP, Steven (2012-12-21)

Official (ISC)2 Guide to the CISSP CBK, Third Edition ((ISC)2 Press) (Kindle Locations 20403-20407)

Auerbach Publications.

Kindle Edition.

and Hernandez CISSP, Steven (2012-12-21)

Official (ISC)2 Guide to the CISSP CBK, Third Edition ((ISC)2 Press) (Kindle Locations 20375-20377)

Auerbach Publications.

Kindle Edition.

Transaction redundancy refers to the process of maintaining multiple copies of the same data, usually for the purpose of ensuring data availability and integrity in the event of hardware or software failures. There are several ways to implement transaction redundancy, and the question is asking which of the given options is not a transaction redundancy implementation.

A. On-site mirroring is a transaction redundancy implementation. It involves duplicating data in real-time between two or more disks or storage devices located on the same site. If one disk fails, the other disk(s) can immediately take over and ensure data availability.

B. Electronic vaulting is also a transaction redundancy implementation. It involves backing up data to an off-site location on a regular basis, usually via electronic means such as the internet or a dedicated network connection. This ensures that if the primary site experiences a disaster such as a fire or flood, the off-site backup can be used to restore data and operations.

C. Remote journaling is another form of transaction redundancy implementation. It involves sending transaction logs from a primary site to a remote site on a regular basis. The remote site maintains a copy of the logs and can use them to recover data in the event of a primary site failure.

D. Database shadowing is a transaction redundancy implementation that involves maintaining a secondary copy of the database on a different system. Changes made to the primary database are also made to the secondary database in real-time, ensuring that the secondary database is always up-to-date.

Therefore, the correct answer is none of the above. All the given options are transaction redundancy implementations.