The goal of database security is to ensure that only authorized users can perform authorized activities at authorized times.

Two transactions that run concurrently and generate results that are consistent with the results that would have occurred if they had run separately are referred to as serializable transactions.

Resource locking is a process to prevent multiple applications from obtaining copies of the same record when the record is about to be changed.

A phantom read occurs when a transaction rereads data it has previously read and finds modifications or deletions caused by a committed transaction.

The lost update problem is when User A reads data that have been processed by a portion of a transaction from User B.

The transaction log contains a copy of every database record (or page) after it has changed. These records are called before images.

The overall responsibility of the DBA is to facilitate the development and use of the database.

A transaction is a series of actions to be taken on the database so that either all of them are performed successfully or none of them are performed at all.

Database administration refers to a function that applies to the entire organization.

The size of the lock is referred to as the lock granularity.

A point of synchronization between the database and the transaction log is generally referred to as a stop point.

Locks placed by command are implicit locks.

A durable transaction is one in which all committed changes are permanent.

An ACID transaction is one that is atomic, consistent isolated, and durable.

An exclusive lock locks the item from change but not from read.