Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Esri EGMP2201 Exam - Topic 4 Question 27 Discussion

Actual exam question for Esri's EGMP2201 exam
Question #: 27
Topic #: 4
[All EGMP2201 Questions]

AGIS data administrator is creating new feature classes within an enterprise geodatabase using the following workflow:

* Five feature classes are added to a feature dataset

* The feature dataset is registered as versioned without the move-edits-to-base option

* Then another feature class is added to the same feature dataset

Users receive error messages when trying to edit any of the feature classes within the feature dataset.

What should the administrator do?

Show Suggested Answer Hide Answer
Suggested Answer: A

Scenario Overview:

Five feature classes are added to a feature dataset, which is registered as versioned without the move-edits-to-base option.

Afterward, another feature class is added to the same feature dataset.

Users encounter errors when trying to edit any feature class in the feature dataset.

Cause of the Problem: When a feature dataset is registered as versioned, all feature classes within it must maintain consistency in their versioning state. Adding a new feature class to a previously versioned feature dataset can disrupt the synchronization, causing errors during editing.

Solution:

Unregister as versioned on the feature dataset: This removes versioning from all feature classes in the dataset, resetting their versioning state.

Register the feature dataset as versioned again: This ensures all feature classes, including the newly added one, are correctly registered with the same versioning state. (ArcGIS Documentation: Registering Datasets as Versioned)

Alternative Options:

Option B: Registering the feature dataset again would not resolve the issue because versioning conflicts persist unless the entire feature dataset is unregistered and re-registered.

Option C: Switching to the move-edits-to-base option is unnecessary and alters the editing workflow, which may not align with the current setup or user needs.

Thus, the administrator should unregister the feature dataset as versioned and re-register it to resolve the errors.


Contribute your Thoughts:

0/2000 characters

Currently there are no comments in this discussion, be the first to comment!


Save Cancel