Optimistic concurrency control in DBMS Theory - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is optimistic concurrency control?

Optimistic concurrency control is a method used in databases to handle multiple users trying to change data at the same time. It assumes conflicts are rare and checks for conflicts only when saving changes.

beginner

How does optimistic concurrency control differ from pessimistic concurrency control?

Optimistic concurrency control allows users to work without locking data first, checking for conflicts later. Pessimistic concurrency control locks data before use to prevent conflicts.

beginner

When is optimistic concurrency control most effective?

It works best when conflicts between users are rare, so most changes can be saved without waiting or blocking others.

beginner

What happens if a conflict is detected in optimistic concurrency control?

The system rejects the conflicting change and asks the user to reload the latest data and try again.

intermediate

Name a common technique used to detect conflicts in optimistic concurrency control.

A common technique is to use a version number or timestamp for data. When saving, the system checks if the version has changed since it was read.

What does optimistic concurrency control assume about data conflicts?

A Conflicts are ignored completely

B Conflicts happen often and must be prevented by locking

C No conflicts can ever happen

D Conflicts are rare and checked only at save time

Optimistic concurrency control assumes conflicts are rare and checks for them only when saving changes.

Which of the following is a key feature of optimistic concurrency control?

A Checking for conflicts after changes are made

B Ignoring data versioning

C Preventing all concurrent access

D Locking data before use

Optimistic concurrency control checks for conflicts after changes are made, not before.

What is a common way to detect conflicts in optimistic concurrency control?

A Using data locks

B Using version numbers or timestamps

C Ignoring user changes

D Allowing multiple writes without checks

Version numbers or timestamps help detect if data was changed by someone else before saving.

What happens if a conflict is found during save in optimistic concurrency control?

A The change is saved anyway

B The system blocks all users

C The change is rejected and user must retry

D The system deletes the data

If a conflict is detected, the system rejects the change and asks the user to try again.

Optimistic concurrency control is best suited for which scenario?

A Rare conflict environments

B Single user systems

C High conflict environments

D Systems without data changes

It works best when conflicts are rare, allowing smooth concurrent work.

Explain optimistic concurrency control and how it manages data conflicts.

Think about how users work on data and what happens when they save.

Describe a situation where optimistic concurrency control is better than pessimistic concurrency control.

Consider when locking data might slow things down unnecessarily.