Explain the difference between revisions, version history, and rollback in content management.

Explain the difference between revisions, version history, and rollback in content management.

• A. Revisions are saved changes; version history tracks all changes over time; rollback restores a previous revision/version to recover content.
• B. Revisions are undo history; version history is automatic backups; rollback permanently deletes current changes.
• C. Revisions are authentication events; version history logs errors; rollback re updates the database schema.
• D. Revisions encrypt changes; version history compares changes; rollback exports content.

Answer: (A)

In content management, these terms describe how edits are saved and how you can move back to a previous state. A revision is a saved change to the content—the page at a specific moment captured as an individual snapshot. Version history is the complete log of those snapshots over time, showing every saved revision with details like when it happened and who made the edit. Rollback is the action that restores the content to a prior snapshot from that history, effectively reverting to an earlier state. Choosing the described option is best because it aligns exactly with how these features work together: each saved edit is a revision, the collection of all those edits forms the version history, and rollback uses that history to recover earlier content. The other options mix up concepts (for example, treating revisions as undo history, or rollback as deleting changes, or implying encryption or schema updates) and don’t reflect how revisions, version history, and rollback function in typical CMS workflows.

In content management, these terms describe how edits are saved and how you can move back to a previous state. A revision is a saved change to the content—the page at a specific moment captured as an individual snapshot. Version history is the complete log of those snapshots over time, showing every saved revision with details like when it happened and who made the edit. Rollback is the action that restores the content to a prior snapshot from that history, effectively reverting to an earlier state.

Choosing the described option is best because it aligns exactly with how these features work together: each saved edit is a revision, the collection of all those edits forms the version history, and rollback uses that history to recover earlier content. The other options mix up concepts (for example, treating revisions as undo history, or rollback as deleting changes, or implying encryption or schema updates) and don’t reflect how revisions, version history, and rollback function in typical CMS workflows.