Free Esri EGMP2201 Exam Dumps August 2026

Understanding the Scenario:

Editors need to isolate their edits so that changes are not immediately visible to others.

Edits must be reviewed before becoming public, indicating a requirement for a structured approval process.

The organization aims to reduce the number of RDBMS users, which suggests centralized management of access and permissions.

Editing Models Overview:

Branch Versioning: Designed for web-based workflows and does not require direct RDBMS access for each editor. However, edits made in branch versioning are inherently collaborative and are not isolated unless explicitly controlled through a branch-per-user workflow, which adds complexity.

Traditional Versioning:

Supports isolated editing through private versions.

Editors can create their own versions, make changes, and submit them for review by reconciling and posting to the default version.

Direct access to the RDBMS is centralized, reducing the need for individual RDBMS users.

Nonversioned Editing: Does not support isolated edits or versioned workflows, making it unsuitable for this scenario.

Steps to Implement Traditional Versioning:

Register the feature class as versioned in the enterprise geodatabase.

Allow editors to create private versions for making isolated edits.

Implement a workflow for reconciling and posting edits after review.

Reference:

Esri Documentation: Traditional Versioning.

Why the Correct Answer is B: Traditional versioning meets all requirements: it isolates edits, allows for review before posting, and reduces the number of RDBMS users through centralized version management. Branch versioning is web-centric and lacks the structured review process, while nonversioned editing does not support isolation or versioning.

Understanding the Scenario:

The query filters rows based on inspector_name and sorts the results by inspection_date.

Creating an index optimizes data retrieval by reducing the number of rows scanned during the query execution.

Key Considerations for Indexing:

Primary Filter Column: The inspector_name column is the primary filter in the WHERE clause. Indexing this column ensures quick identification of rows matching the filter condition.

Sort Optimization: The ORDER BY inspection_date clause benefits from indexing inspection_date as the second column in a composite index, which accelerates sorting for the filtered results.

Index Selection:

A composite index on inspector_name and inspection_date enables efficient query execution:

inspector_name ensures fast filtering.

inspection_date optimizes sorting.

Indexing unrelated columns like facility_type is unnecessary, as it is not part of the query.

Steps to Create the Index:

In the enterprise geodatabase, use the database management tools or SQL commands to create a composite index:

CREATE INDEX idx_facility_inspections

ON facility_inspections (inspector_name, inspection_date);

Reference:

Esri Documentation: Creating and Managing Indexes.

SQL Indexing Best Practices: Guidelines for composite index creation to optimize queries.

Why the Correct Answer is D: A composite index on inspector_name and inspection_date directly addresses the query structure, optimizing both the WHERE filter and the ORDER BY clause.

To identify which user was responsible for creating each feature in a global enterprise geodatabase, enabling editor tracking is the appropriate strategy.

1. What is Editor Tracking?

Editor tracking records metadata about feature creation and updates, including:

Who created or updated a feature.

When the feature was created or updated.

This information is stored in four additional fields:

Creator

Creation Date

Editor

Edit Date

2. Advantages of Editor Tracking

Automatically tracks and populates user and timestamp fields for feature edits.

Requires no manual intervention by users, ensuring accuracy and consistency.

Works seamlessly in multi-user environments, including enterprise geodatabases.

3. Why Not Other Options?

Add a Global ID:

Global IDs are used to uniquely identify features but do not track user edits or changes.

Use Relationship Classes:

Relationship classes establish connections between features or tables. They are not designed to record user actions or metadata.

Steps to Enable Editor Tracking:

Open ArcGIS Pro and connect to the enterprise geodatabase.

Right-click the feature class or dataset and select Manage > Enable Editor Tracking.

Specify the fields for storing creator, editor, creation date, and edit date.

Save and apply the changes.

Reference from Esri Documentation and Learning Resources:

Editor Tracking---ArcGIS Pro Documentation

Tracking Edits in Enterprise Geodatabases

Conclusion:

Enabling editor tracking is the most effective strategy to identify which user created each feature in a global enterprise geodatabase.

Scenario Overview:

The user requires a standard database view of the roads feature class that resides in a different geodatabase from the primary enterprise geodatabase.

The roads feature class is frequently edited, and the user needs the view to recognize updates immediately.

Replica Types in ArcGIS:

One-way replication with the full model is suitable for scenarios where the parent geodatabase sends updates to the child geodatabase, and all schema and data changes are synchronized.

In the full model, the child database retains versioning and acknowledges updates as they occur in the parent database, enabling the user to see immediate updates in their standard view. (ArcGIS Documentation: Geodatabase Replication Types)

Key Features of the Full Model:

Synchronizes both schema and data changes.

Suitable for feature classes with frequent edits.

Ensures that the standard database view reflects updates immediately upon synchronization.

Alternative Options:

Option A: The simple model in one-way replication supports data-only synchronization and does not update schema changes, making it insufficient for dynamic environments.

Option C: Two-way replication is unnecessary since the edits occur only in the parent geodatabase.

Thus, one-way replication with the full model is the appropriate choice to meet the requirement.

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.

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.

To restrict access to specific fields in a feature class, the GIS data administrator should use a database view.

1. What is a Database View?

A database view is a virtual table created by a SQL query. It displays data from one or more tables or feature classes, but only the specified fields and rows are accessible.

Views allow the administrator to control the fields and records visible to users without altering the underlying data.

2. Why Use a Database View?

Provides fine-grained control over data access by limiting which fields (or rows) are visible to specific users.

Helps enforce data security policies in multi-user environments.

Can be shared as a read-only layer or with restricted update permissions, depending on the use case.

3. Why Not Other Options?

Layer File:

A layer file (*.lyr) only defines how data is symbolized and displayed. It does not restrict field access at the database level. Unauthorized users can still access hidden fields through direct database connections.

Query Layer:

A query layer allows for custom SQL queries when displaying data in ArcGIS but is not a security measure. Users can modify or bypass the query to access all fields.

Steps to Create a Database View:

Use SQL to define the view, specifying only the required fields:

CREATE VIEW restricted_view AS

SELECT field1, field2

FROM feature_class

WHERE <condition>;

Grant permissions to the view for authorized users while restricting access to the base table.

Publish the view in ArcGIS as a read-only layer if needed.

Reference from Esri Documentation and Learning Resources:

Creating and Using Database Views

Data Security in Enterprise Geodatabases

Conclusion:

A database view is the most effective method to restrict access to specific fields in a feature class, ensuring data security while providing flexibility in data sharing.

Understanding the Scenario:

An enterprise geodatabase feature dataset is accidentally deleted.

The organization needs to recover the dataset to its original state.

Available Technologies:

High Availability: High availability setups (e.g., failover systems) ensure continuous access to geodatabases during hardware or software failures. However, high availability does not restore accidentally deleted data.

Backup: A backup is a snapshot of the geodatabase taken at a specific point in time. It allows administrators to restore deleted datasets or recover from data loss scenarios.

Archiving: Archiving tracks historical edits in versioned geodatabases but does not provide recovery for accidentally deleted datasets.

Steps to Recover the Dataset:

Identify the most recent backup of the enterprise geodatabase.

Restore the geodatabase or extract the specific feature dataset from the backup.

Verify the restored data and synchronize it with ongoing updates if necessary.

Reference:

Esri Documentation: Backup and Restore.

Best Practices for Data Protection: Guidelines for implementing regular backups to prevent data loss.

Why the Correct Answer is B: A backup is the most reliable solution for recovering an accidentally deleted feature dataset. High availability ensures uptime but does not address data recovery, and archiving tracks edits rather than preserving entire datasets.