What occurs when a System Architect rolls back a revision?

When a System Architect rolls back a revision, a new version of the revision is created internally. This process allows for the previous state of the application or component to be reinstated while retaining a record of the changes made. By creating a new revision, the system maintains a version history that can be useful for tracking the evolution of the application, facilitating better management of changes over time, and enabling further modifications or updates if required.

This approach supports best practices in version control, ensuring that any rollback action does not result in the irreversible loss of data or structure within the application. Other options suggest outcomes that either misrepresent the rollback process or imply deletion, which does not occur in this context. Thus, the creation of a new internal revision maintains the integrity and continuity of the system architecture.