Esri Enterprise Geodata Management Professional 2201 EGMP2201 Exam Questions

Answer : A

Scenario Overview:

The organization has ArcGIS Enterprise and requires versioned editing.

The project mandates tracking which user deleted a feature from the default version.

Why Branch Versioned Editing?

Branch versioning supports versioned editing workflows and integrates seamlessly with editor tracking, including operations like tracking who deleted a feature.

It is ideal for web-based workflows in ArcGIS Enterprise and allows for direct interaction with feature services.

The default version remains accessible for analysis while enabling the organization to track user edits, including feature deletions. (ArcGIS Documentation: Branch Versioning)

Alternative Options:

Option B: Traditional versioned editing supports versioned workflows but does not inherently track who deletes features unless additional workflows are implemented (e.g., custom fields or triggers).

Option C: Nonversioned editing does not support versioning workflows or user tracking.

Thus, branch versioned editing is the best workflow to support versioned editing while tracking deleted features.

Answer : C

Scenario Overview:

The GIS data administrator needs to prepare data for offline workflows.

Offline workflows allow users to take data offline for use in disconnected environments, typically for field operations.

Why Enable Sync?

Sync must be enabled on the feature service to allow offline workflows. This capability ensures that edits made offline can later be synchronized with the enterprise geodatabase.

When sync is enabled, data can be downloaded for offline use in supported applications like ArcGIS Field Maps, and changes can be synchronized back to the geodatabase.

(ArcGIS Documentation: Sync)

Alternative Options:

Option A: Enable Archiving

Archiving tracks historical edits but is not required for offline workflows.

Option B: Add Global IDs

While Global IDs are required for enabling sync, adding them alone does not fully configure the dataset for offline workflows.

Thus, to prepare data for offline workflows, the administrator must enable sync on the dataset.

Answer : A

Scenario Overview:

Editors reconcile and post daily, but read-only versions created for analysis are not reconciled or posted.

The geodatabase is compressed nightly, but performance continues to degrade.

Cause of the Problem:

Unreconciled versions, including read-only ones, persist in the state tree, preventing the geodatabase compression from fully collapsing unused states.

Over time, this results in a bloated state tree and worsened performance.

Solution:

Reconciling and posting the read-only versions ensures that the state tree is cleared of unnecessary versions, enabling compression to collapse the database to its optimal state.

(ArcGIS Documentation: Reconcile and Post)

Alternative Options:

Option B: Creating a database view provides a read-only representation of data but does not address the underlying issue of unresolved states in the state tree.

Option C: Disabling editor tracking is unrelated to state tree performance issues and has no impact on the reconciliation or compression processes.

Therefore, reconciling the read-only versions will significantly improve performance.

Answer : C

Scenario Overview:

Editors are spending multiple hours resolving conflicts during reconciliation.

Key points:

Conflicts are detected by attribute (not by object).

Traditional versioning is used.

Weekly compression and weekly reconcile/post workflows are in place.

Why Reconcile and Post Daily?

Conflicts occur when multiple editors make overlapping edits. The longer versions remain unreconciled, the more conflicts accumulate, leading to time-consuming resolution.

Daily reconciliation and posting minimizes the number of changes between the parent and child versions, reducing the likelihood and volume of conflicts.

(ArcGIS Documentation: Reconcile and Post)

Key Benefits of Daily Reconciliation:

Fewer Changes to Compare: With fewer edits accumulated in each version, conflict detection is faster.

Less Complex Conflicts: Simplifies resolution since changes are smaller and more recent.

Improved Editor Productivity: Editors spend less time resolving conflicts, freeing up time for other tasks.

Alternative Options:

Option A: Detect conflicts by object

While this may reduce conflict granularity, it can lead to overwriting valid edits at the object level, which may not be acceptable in collaborative workflows.

Option B: Compress the geodatabase daily

Compression reduces the state tree and improves performance but does not directly reduce the number of conflicts during reconciliation.

Therefore, implementing daily reconciliation and posting is the most effective way to reduce conflicts and improve editing efficiency.

Answer : A

Scenario Overview:

The organization has a web service that must always be available.

The service reads data from a feature class in an enterprise geodatabase.

The GIS administrator needs to update the schema of the feature class.

Why Disable Schema Locking?

By default, ArcGIS services enforce schema locking to ensure data consistency while the service is active. This prevents any modifications to the feature class schema (e.g., adding fields, altering attributes) while the service is running.

Disabling schema locking allows schema updates to occur without disrupting the service's availability. (ArcGIS Documentation: Schema Locking)

Steps to Disable Schema Locking:

Access the ArcGIS Server Manager.

Locate the web service and open its service properties.

In the advanced settings, disable the schema locking option.

Perform the required schema updates (e.g., adding fields or modifying the feature class).

Re-enable schema locking if necessary for normal operation.

Alternative Options:

Option B: Run the Alter Field geoprocessing tool

This tool modifies fields but cannot execute schema changes while schema locks are active.

Option C: Delete the spatial index

Deleting the spatial index is unrelated to schema changes and could degrade query performance.

Thus, the correct workflow is to disable schema locking on the service to allow schema changes without disrupting the web service.

Answer : A

Understanding the Scenario:

The regional office lacks access to ArcGIS Enterprise, ArcGIS Online accounts, or an enterprise geodatabase.

Data must be distributed in a format that the regional office can use independently of enterprise-level systems.

Data Distribution Solutions Overview:

Geodatabase Replication:

Geodatabase replication allows data to be exported and shared with external systems, such as file or personal geodatabases.

Replicas can be set up in a disconnected mode, enabling regional offices to work with the data offline.

Distributed Collaboration: Distributed collaboration facilitates sharing data and content between ArcGIS Enterprise and ArcGIS Online environments. It is unsuitable for offices without these systems.

Partnered Collaborations: Partnered collaborations extend distributed collaboration to partner organizations, but they also require ArcGIS Online accounts, making them incompatible with this scenario.

Steps to Implement Geodatabase Replication:

Create a one-way replica of the data in a format compatible with the regional office's systems (e.g., file geodatabase).

Transfer the replica to the regional office via portable media or secure file sharing.

Set up periodic updates if the data needs to be refreshed.

Reference:

Esri Documentation: Geodatabase Replication.

Disconnected Workflows: Best practices for sharing data in offline environments.

Why the Correct Answer is A: Geodatabase replication is the most suitable solution for sharing data with a regional office that lacks enterprise-level systems. Distributed and partnered collaborations require ArcGIS Enterprise or ArcGIS Online accounts, which are unavailable in this scenario.

Answer : C

Understanding the Scenario:

The request involves creating a view that dynamically combines data from a versioned feature class and a nonspatial table.

The data needs to be from a child version and updated dynamically.

Key Considerations:

Versioned Feature Class: Standard feature classes in versioned geodatabases store edits in delta tables (adds and deletes). Accessing data from a specific version requires using the versioned view, which includes these edits.

Dynamic Updates: Views created on the versioned view ensure that the data reflects the most current version edits.

Steps to Create the View:

Identify the versioned view for the feature class (created automatically during versioning).

Create a SQL query to join the versioned view and the nonspatial table on the appropriate key(s).

Save the SQL query as a database view.

Reference:

Esri Documentation: Versioned Views.

Creating Views with Versioned Data: Guidelines for joining versioned views with other tables in SQL.

Why the Correct Answer is C: Using the versioned view ensures that data reflects edits from the specified child version. Joining this view with the nonspatial table meets the requirement for dynamic updates. Options A and B would not provide data from the versioned child version dynamically.