Esri Exam EGMP2201 Topic 2 Question 2 Discussion

Geometric networks are not supported in branch versioning or workflows where edits are moved directly to the base table. Therefore, traditional versioning without move edits to base is the only viable option for implementing an offline mobile editing workflow with feature classes that participate in a geometric network.

1. Why Use Traditional Versioning Without Move Edits to Base?

Support for Geometric Networks:

Geometric networks are only compatible with traditional versioning workflows. Branch versioning does not support geometric networks, and using the 'move edits to base' option bypasses the versioning framework required for geometric networks.

Offline Mobile Editing:

Traditional versioning supports creating replicas that allow offline editing and subsequent synchronization. This workflow is critical for mobile editing scenarios.

2. Why Not Other Options?

Branch Versioning:

Branch versioning is designed for feature services and web-based workflows but does not support geometric networks.

Traditional Versioning with Move Edits to Base:

This option moves edits directly to the base table, which is incompatible with geometric networks and versioning workflows that require offline editing.

Steps to Configure Traditional Versioning Without Move Edits to Base:

Register the feature classes and datasets (including geometric networks) with traditional versioning in ArcGIS Pro.

Create a replica to support offline editing workflows.

Synchronize edits back to the geodatabase after offline editing, reconcile, and post to integrate changes into the Default version.

Reference from Esri Documentation and Learning Resources:

Traditional Versioning Overview

Geometric Networks and Versioning

Conclusion:

Using traditional versioning without move edits to base is the only method that supports offline mobile editing workflows while maintaining compatibility with geometric networks.