AGIS data manager realizes that archiving cannot be enabled for a feature class. An investigation reveals that the problem is in the feature class configuration. How was the feature class registered?
Correct Answer: B
Understanding the Scenario: * The feature class cannot havearchiving enabled. * Archiving tracks changes over time and requires specific configurations in versioned datasets. Key Constraints for Enabling Archiving: * Archiving can only be enabled for feature classes registered asversioned without moving edits to base. * Versioned with move edits to base:This configuration directly edits the base table, bypassing the delta tables (adds and deletes) used in traditional versioning. Since archiving relies on delta tables to track changes, this configuration is incompatible with archiving. * Branch Versioned with Editor Tracking:Branch versioning supports editor tracking and web-based workflows but does not currently support archiving. Steps to Correct the Configuration: * Re-register the feature class asversioned without moving edits to base. * Enable archiving after re-registration. References: * Esri Documentation: Archiving Requirements. * Versioning and Archiving Compatibility: Best practices for configuring datasets for archiving. Why the Correct Answer is B:When a feature class is registered asversioned with move edits to base, it does not maintain delta tables, making it incompatible with archiving.
