Esri EGMP2201 Dumps Questions Answers

In a branch versioning workflow where thedefault versionis the published version that users see and editors can post edits to, setting the access level toProtectedis the best choice.

1. What Does the Protected Access Level Do?

TheProtectedaccess level allows users to view and query the version but restricts editing to authorized users only.

This ensures that only authorized editors can post changes to the default version, maintaining data integrity while allowing portal users to access the published version.

2. Why Not Other Options?

Public:

A public version allows anyone with appropriate permissions to edit the version. This could lead to uncontrolled changes and data integrity issues.

Private:

A private version restricts access to the version to only the owner and specific users, which is unsuitable when the default version is meant to be the published version visible to all portal users.

Steps to Configure Protected Access Level:

OpenArcGIS ProorArcGIS Enterprise Manager.

Navigate to the version management settings for the default version.

Set theAccess LeveltoProtected.

Ensure that editors with appropriate privileges are assigned to post changes to the default version.

References from Esri Documentation and Learning Resources:

Version Access Levels in Branch Versioning

Branch Versioning Workflows

Conclusion:

Setting the default version toProtectedensures a balance between providing access to portal users and restricting edits to authorized personnel.

Scenario Overview:

A one-way replica from parent to child geodatabase is created for a single feature class.

The data owner adds anew attribute fieldin the parent geodatabase, calculates values, and attempts to synchronize the replica.

The new field and its values do not appear in the child replica, even after manually adding the field to the child geodatabase.

Why Recreate the Replica?

The issue arises becauseschema changes(e.g., adding new fields) are not automatically propagated in one-way replication workflows. Synchronization only applies to data changes, not schema updates.

To ensure the schema changes are recognized, thereplica pair must be recreatedwith the updated schema.(ArcGIS Documentation: Geodatabase Replication and Schema Changes)

Steps to Resolve the Issue:

Unregister the Replica:Remove the existing replica pair from both the parent and child geodatabases.

Recreate the Replica:Create a new one-way replica between the parent and child geodatabases. This new replica will include the updated schema.

Synchronize Changes:Perform synchronization to transfer data, including the new field and calculated values, to the child geodatabase.

Alternative Options:

Option A:Enabling replica tracking does not address schema synchronization and would not resolve the issue.

Option B:Running Feature Compare is helpful for analyzing schema differences but does not propagate schema changes.

Thus, the data owner mustunregister the replica pairs, recreate the replica with the updated schema, and synchronize changesto resolve the issue.

The issue arises because the standard database view is based on the base table of the points feature class, which does not include edits made in child versions. To resolve this, the database view must reference aversioned viewto reflect changes in the Default version.

1. What Is a Versioned View?

Aversioned viewis created when a feature class is registered as versioned.

It allows querying and editing versioned data, including edits made in the Default version and child versions.

A standard database view does not account for the Adds and Deletes delta tables used in versioning, which is why edits are not visible.

2. Why Alter the View to Use a Versioned View?

By modifying the standard database view to reference the versioned view, the published web layer will reflect changes made in the Default version, including ongoing edits.

This ensures that updates to the points feature class are visible in the web layer without requiring manual intervention.

3. Why Not Other Options?

Have All Editors Reconcile and Post Points Edits to Default:

While this ensures edits are moved to the Default version, it requires continuous manual reconciliation and posting, which is impractical for a frequently edited dataset.

Rebuild Indexes and Calculate Database Statistics on Points:

These actions improve query performance but do not address the core issue of the standard view not reflecting versioned edits.

Steps to Alter the View:

Identify the versioned view associated with the points feature class. It typically has a name like points_EVW.

Modify the SQL for the existing view to reference the versioned view:

CREATE OR REPLACE VIEW points_web AS

SELECT FROM points_EVW;

Update the web layer to use the modified view as the data source.

Test the web layer to confirm that edits made to the Default version are now visible.

References from Esri Documentation and Learning Resources:

Versioned Views in Enterprise Geodatabases

Publishing Data from Views

Conclusion:

To ensure edits made to the points feature class are visible in the web layer, thedatabase view should be altered to reference the versioned view, which accounts for edits in the Default version.