support@Free-Braindumps.com
Register Login
Cisco
CompTIA
ISC
EC-Council
EXIN
Fortinet
ITIL
Juniper
Microsoft
VMware
Avaya
SAP
Google
NVIDIA
Salesforce
Amazon
Palo Alto Networks
ISC2
Splunk
ServiceNow
All Vendors
  1. Home
  2. Exams
  3. Esri
  4. EGMP2201

Esri EGMP2201 Exam Prep
Enterprise Geodata Management Professional 2201 (Page 3 )

Updated On: 5-Sep-2026
Page 2 of 14
PDF with 65 Questions

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?

  1. Change the access level of the child version from protected to public
  2. Ask the owner of Default to perform the reconcile and post for the editor
  3. Create a one-way replica from the child version and synchronize to Default

Answer(s): B

Explanation:

In traditional versioning within an enterprise geodatabase, the Default version often represents the published state of the database. Setting the Default version to protected ensures that while all users can view it, only the geodatabase administrator or the version owner can edit it directly or post changes to it.
ArcGIS Pro
In the scenario provided, the editor follows these steps:
Default Version Set to Protected: This restricts editing and posting privileges to the geodatabase administrator or the version owner.
Creation of a Child Version from Default: The editor creates a new version branching from Default. Child Version Set to Protected: This means only the editor (as the owner) or the geodatabase administrator can edit this child version.
Edits Saved to the Child Version: The editor makes and saves changes within this child version. Attempt to Reconcile and Post to Default: The editor successfully reconciles but encounters an error during the post operation.
The error during the post operation arises because, with the Default version set to protected, the editor lacks the necessary permissions to post changes directly to it. Only the geodatabase administrator or the owner of the Default version possesses the authority to perform this action.
ArcGIS Pro
Analysis of Options:
Option A: Changing the access level of the child version from protected to public does not grant the editor the required permissions to post to the protected Default version. Option B: Requesting the owner of the Default version (typically the geodatabase administrator) to perform the reconcile and post is appropriate. This individual has the necessary permissions to post changes to the protected Default version.
Option C: Creating a one-way replica and synchronizing is an unnecessary and complex approach for this situation.
Therefore, the editor should ask the owner of Default to perform the reconcile and post to ensure the changes are integrated into the Default version.



A GIS administrator needs to facilitate the collaboration of two teams of GIS analysts in two different offices. Each office needs a copy of the data in its own enterprise geodatabase. and analysts in both offices will edit the same feature classes. Changes will be synchronized nightly. The GIS administrator needs to set up the information infrastructure so that both teams can work together.
What should the administrator use to meet the requirements?

  1. Geodatabase replication
  2. Database replication
  3. Distributed collaboration

Answer(s): A

Explanation:

To facilitate collaboration between two teams of GIS analysts located in different offices, each requiring a copy of the data in their own enterprise geodatabase with the ability to edit the same feature classes and synchronize changes nightly, geodatabase replication is the appropriate solution.

Understanding Geodatabase Replication:

Geodatabase replication is a data distribution method in ArcGIS that allows you to create copies of data across two or more geodatabases. This enables multiple users to work with the same datasets in different locations, with the ability to synchronize changes to ensure consistency.
ARCGIS PRO

Types of Geodatabase Replication:

There are three types of geodatabase replication:

One-Way Replication: Changes are sent in a single direction--from the parent to the child replica.

Two-Way Replication: Changes are synchronized in both directions between the parent and child replicas. This is suitable when multiple editors need to update the same datasets in different locations.

Checkout/Check-in Replication: Data is checked out to a child replica for editing and then checked back in to the parent replica.

In this scenario, two-way replication is ideal, as it allows both teams to edit the same feature classes and synchronize changes nightly, ensuring that both geodatabases remain consistent.
ARCGIS PRO

Alternative Options:

Database Replication: This refers to replicating entire databases at the DBMS level.
While it can synchronize data, it doesn't account for the geodatabase-specific behaviors, rules, and relationships managed by ArcGIS. Therefore, it may not be suitable for scenarios requiring synchronization of geodatabase-specific functionalities.

Distributed Collaboration: This is a framework in ArcGIS Enterprise that allows sharing of content, such as maps, layers, and apps, across multiple ArcGIS Enterprise deployments or between ArcGIS Enterprise and ArcGIS Online. However, it doesn't provide the fine-grained control over data editing and synchronization required in this scenario.
GEODATABASE RESOURCES

Therefore, to meet the requirements of both teams being able to edit the same feature classes in their respective enterprise geodatabases and synchronize changes nightly, geodatabase replication is the most appropriate solution.



Slow performance is observed on a query of an indexed attribute on a large feature class in an enterprise geodatabase.
- A SOL trace reveals that the attribute index is not being used in the query - The indexed attribute values have a high degree of uniqueness - The delta tables do not have very many rows
Which tool should be used to resolve this issue?

  1. Rebuild Indexes
  2. Compress Geodatabase
  3. Analyze Datasets

Answer(s): A

Explanation:

When experiencing slow performance on a query of an indexed attribute in a large feature class within an enterprise geodatabase, and a SQL trace reveals that the attribute index is not being utilized despite the attribute values having a high degree of uniqueness and the delta tables containing few rows, the appropriate action is to rebuild the indexes.

Understanding Indexes in Enterprise Geodatabases:

Indexes are critical for enhancing query performance in databases. They allow the database management system (DBMS) to locate and retrieve data efficiently. Over time, as data is inserted, updated, or deleted, indexes can become fragmented or outdated, leading to suboptimal query performance.
ARCGIS PRO

Rebuilding Indexes:

The Rebuild Indexes tool in ArcGIS Pro is designed to rebuild existing attribute or spatial indexes in enterprise geodatabases. This process reorganizes the index structure, ensuring that the DBMS can effectively utilize the indexes during query execution.
ARCGIS PRO

Steps to Rebuild Indexes:

Access the Rebuild Indexes Tool:

In ArcGIS Pro, navigate to the Analysis tab and click on Tools. In the Geoprocessing pane, search for and select the Rebuild Indexes tool.
Configure the Tool Parameters:

Input Database Connection: Specify the connection to your enterprise geodatabase. Include System Tables: Decide whether to include system tables in the rebuild process. Including system tables can help maintain the overall health of the geodatabase but may increase processing time.
Execute the Tool:

Click Run to initiate the index rebuilding process. Monitor the progress and ensure the process completes without errors.
Alternative Options:

Compress Geodatabase: The Compress operation reduces the size of the geodatabase by removing redundant states and versions.
While it can improve performance, it doesn't directly address index fragmentation.
Analyze Datasets: The Analyze Datasets tool updates database statistics, which helps the DBMS optimize query execution plans. However, if indexes are fragmented, analyzing datasets alone may not resolve performance issues.

Given the symptoms described--specifically, the attribute index not being used in queries--the most effective solution is to rebuild the indexes to ensure they are properly structured and utilized by the DBMS during query execution.



A wells feature class has one row per well. A well_inspections table has one row for each time a well was inspected. All inspection dates need to be displayed as labels clustered around each well on the map.
Which kind of association should be used to meet this requirement?

  1. Join
  2. Relate
  3. Relationship class

Answer(s): B

Explanation:

Scenario Overview:

The wells feature class has one row per well.
The well_inspections table has one row for each inspection of a well. Inspection dates from the well_inspections table need to be displayed as labels clustered around each well on the map.
The goal is to establish a connection between these two datasets without permanently joining them, as the data is being displayed dynamically (inspection dates are clustered around the wells).

Relates in Geodatabases:

A relate is a type of table association in which tables are linked by a common key field but remain separate.
Relates allow for dynamic queries to retrieve related records without duplicating or permanently associating the data.
Using a relate, you can query all inspection dates for a specific well dynamically, display them on the map as labels, and preserve the integrity of both the wells and inspections datasets.
(ArcGIS Documentation: Relates)
Alternative Options:

Option A: Join
A join merges two tables into one virtual table, based on a shared key. However, this approach is static and inappropriate for displaying dynamically clustered labels since the tables would need to be rejoined after every update.

Option C: Relationship Class
A relationship class is a more permanent association that enforces rules between two datasets. It is ideal for maintaining relationships between data but is unnecessary for dynamically labeling inspection dates on the map.
Thus, a relate is the most efficient and appropriate option for this scenario.



Multiple editors in a web application need to collaboratively edit the same dataset using the following requirements:
- Each editor works in isolation until they come to a good stopping point - The editor shares their edits with the other editors at this point

- The editor again goes into isolation to continue editing until the next stopping point is reached - At any point, an editor can choose to see the edits that other editors have shared without sharing their own edits
How should the dataset be registered?

  1. Branch versioned
  2. Traditional versioned with editor tracking enabled
  3. Traditional versioned with the option to move edits to base

Answer(s): A

Explanation:

Scenario Overview:
Multiple editors need to collaboratively edit the same dataset using a web application.
Requirements:
Editors work in isolation until they reach a stopping point.
Edits are shared with others at the stopping point.
Editors can view shared edits without sharing their own.
Branch Versioning in Enterprise Geodatabases:
Branch versioning is specifically designed for collaborative editing in web-based workflows. It supports isolated editing by creating branches for each editor and allows users to reconcile and post changes at their discretion.
Editors can choose to reconcile shared changes without posting their own edits, fulfilling the requirement to view shared edits without sharing their own.
(ArcGIS Documentation: Branch Versioning)
Key Features of Branch Versioning:
Supports Web Applications: Designed to work seamlessly with feature services, enabling real-time collaborative editing.
Isolation: Each editor can edit independently in their branch. Reconciliation: Editors can reconcile and view changes made by others without posting their edits. Flexible Sharing: Editors control when to post edits.
Alternative Options:
Option B: Traditional versioned with editor tracking enabled:
Traditional versioning supports isolated editing, but it does not provide the flexibility to view shared changes without posting your own edits.
It is also not as well-suited for web-based collaborative workflows.

Option C: Traditional versioned with the option to move edits to base:
Moving edits to base bypasses versioning workflows entirely and is not designed for collaborative editing.
Thus, branch versioning is the optimal solution for the requirements of this collaborative editing workflow in a web application.



  PDF
Viewing page 3 of 14
Viewing questions 11 - 15 out of 65 questions


Post your Comments and Discuss Esri EGMP2201 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!