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?
All editors reconcile and post their versions daily. Other users create read -only versions for analysis purposes, so they do not reconcile and post those versions. The geodatabase administrator compresses the geodatabase nightly. For several months, performance steadily worsens. Which action should be taken?
A GIS analyst creates a join relationship between a large dataset and a nonspatial table to calculate an attribute field. Upon building the join, the analyst receives an error message stating that the join field <value> in the join table <value> is not indexed. Which tool should the analyst run?
A user plans to use a standard database view of a roads feature class from a geodatabase that is different from the primary enterprise geodatabase. Roads is frequently edited in the parent geodatabase, so the user needs to regularly synchronize and have the view recognize all incoming edits immediately. Which replica type should be used?
A GIS data administrator is unable to upgrade the geodatabase while editors have active sessions and are working on editing workflows. What should the editors do?
An editor connects to an enterprise geodatabase to edit a feature class that uses traditional versioning. The editor uses the following workflow: • The Default version is set lo protected • A new child version is created from Default • The child version is set to protected • Edits are saved to the child version • The editor tries to reconcile and post to Default The reconcile is successful, but the post operation fails with an error. What should the editor do?
