MENU
An organization uses a two-way replica to share edits for a polygon feature class with a field office. After months of synchronizing edits, a schema change takes place using the following workflow;
* A new field called a legal_area is added to a polygon feature class in the parent geodatabase
* An editor uses the Calculate Geometry tool to calculate legal_area for each polygon
* The child geodatabase does not have the legal_area field in the polygon feature class
* The parent geodatabase synchronizes the replica to the child geodatabase
What happens during synchronization?
Understanding the Scenario:
A two-way replica exists between a parent geodatabase and a child geodatabase to share edits.
A schema change (adding the legal_area field) occurs in the parent geodatabase but is not applied to the child geodatabase.
The parent synchronizes the replica, attempting to push changes that include edits to the new field.
Replica Synchronization Behavior:
Schema Changes and Replication: Replication does not automatically synchronize schema changes such as adding new fields. Schema updates need to be manually applied to both parent and child geodatabases before synchronization.
Conflict during Synchronization: If schema changes (like adding a field) are made in the parent geodatabase but not replicated in the child geodatabase, synchronization attempts to apply edits referencing the missing field. This results in an error because the child geodatabase does not recognize the new field.
Reference:
Esri Documentation: Schema Changes and Replication.
Error Handling in Synchronization: Guidance on managing synchronization issues due to schema mismatches.
Why the Correct Answer is A: During synchronization, an error occurs because the legal_area field does not exist in the child geodatabase. Synchronization cannot succeed unless both replicas have compatible schemas.