What is the consequence of merging the sandbox that contains semantic model extensions?

• A. There is no rollback once merged.
• B. You can revert to the previous version at any time.
• C. A parallel sandbox is created automatically.
• D. Merging triggers an automatic validation pass.

Answer: (A)

Merging a sandbox that contains semantic model extensions is effectively a final integration step; once the merge is done, there isn’t a built-in rollback available for that merge. The changes become part of the target model, and undoing them typically requires restoring from a prior backup or reapplying the previous state in a new or separate process. This emphasizes why pre-merge validation and having a rollback plan are important.

The other options aren’t inherent consequences of merging. Reverting to a previous version isn’t automatic within the merge flow—you’d need an external backup or versioned snapshot to restore. A parallel sandbox isn’t created automatically as a result of the merge. And an automatic validation pass isn’t guaranteed simply by merging; validation steps are usually performed as separate checks before or alongside the merge, not as an automatic post-merge outcome.