A DevOps Engineer is executing an online backup and wants to ensure consistency. This is a newer AEM version that uses Oak as a repository with multiversion concurrency control. What setting is no longer required to be set before performing a backup to ensure consistency?

A DevOps Engineer is executing an online backup and wants to ensure consistency. This is a newer AEM version that uses Oak as a repository with multiversion concurrency control. What setting is no longer required to be set before performing a backup to ensure consistency?

• A. Blocking the replication queues
• B. Blocking the repository reads
• C. Blocking the repository writes
• D. Blocking the repository queues

Answer: (C)

Oak uses multiversion concurrency control, which gives you a consistent view of the repository at a specific point in time even while many operations are happening. For online backups, the backup process can read from a fixed revision and stream a consistent snapshot without needing to pause ongoing writes. That’s why blocking repository writes is no longer required to ensure a consistent backup. The system’s MVCC mechanism provides the necessary snapshot guarantees, so you don’t have to stop writes to achieve consistency.

Oak uses multiversion concurrency control, which gives you a consistent view of the repository at a specific point in time even while many operations are happening. For online backups, the backup process can read from a fixed revision and stream a consistent snapshot without needing to pause ongoing writes. That’s why blocking repository writes is no longer required to ensure a consistent backup. The system’s MVCC mechanism provides the necessary snapshot guarantees, so you don’t have to stop writes to achieve consistency.