Key details for this exam, checked against the published exam outline
Each question shows the correct answer and an explanation of why it is right
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?
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.
The GIS administrator does not have the database administrator credentials and needs to create an enterprise geodatabase for storage of vector dat
a. The database administrator will provide a database with the appropriate users and permissions for use.
Which tool should the GIS administrator use?
Understanding the Scenario: The GIS administrator lacks database administrator credentials but requires an enterprise geodatabase for vector data storage. In this setup, the database administrator (DBA) is responsible for preparing the database, including setting up users and permissions, while the GIS administrator is tasked with enabling it as an enterprise geodatabase.
Tool Selection Overview:
Create Feature Dataset: This tool is for creating a logical grouping of related feature classes inside an existing geodatabase. It is unrelated to enabling or creating an enterprise geodatabase.
Enable Enterprise Geodatabase: This tool is used when a database has already been created and configured by the DBA, and the GIS administrator needs to enable it as an enterprise geodatabase. It adds geodatabase system tables and functionality to the database. This aligns with the scenario described.
Create Enterprise Geodatabase: This tool creates a new database and configures it as an enterprise geodatabase in one step. However, this tool requires database administrator credentials, which the GIS administrator in this scenario does not have.
Key Steps to Enable an Enterprise Geodatabase:
Preparation by DBA: The DBA sets up the database, ensuring the appropriate users and permissions are in place. They also provide connection details to the GIS administrator.
Using the Enable Enterprise Geodatabase Tool:
Navigate to ArcGIS Pro or ArcGIS Enterprise tools.
Open the Enable Enterprise Geodatabase tool.
Specify the database connection file for the target database.
Provide the authorization file (a valid ArcGIS Server Enterprise license file) to enable geodatabase functionality.
Execute the tool to add system tables, stored procedures, and geodatabase functionality to the database.
Reference:
ArcGIS Pro Documentation on Enable Enterprise Geodatabase.
Esri Enterprise Geodatabase Concepts: Official Esri documentation provides comprehensive details on the role of DBAs and GIS administrators in setting up enterprise geodatabases.
ArcGIS Enterprise Licensing Guide: Detailed information about authorization files for enabling geodatabases.
Why the Correct Answer is B: The tool ''Enable Enterprise Geodatabase'' is specifically designed for situations where the database setup is handled by a DBA, and the GIS administrator is responsible only for enabling geodatabase capabilities. Since the GIS administrator does not have DBA credentials, they cannot use the ''Create Enterprise Geodatabase'' tool, which would require those credentials to create and configure a new database.
An organization has a requirement to allow editing of feature classes in mobile and web apps. A database administrator will need to add indexes to feature classes to improve performance on common queries.
Where should these feature classes be stored?
Understanding the Scenario:
The organization requires feature classes to be editable in mobile and web apps.
Performance optimization through indexing is also needed for common queries.
Feature Class Storage Options:
Enterprise Geodatabase:
Supports multiuser environments, making it suitable for mobile and web app editing.
Allows indexing at the database level, which improves query performance for large datasets.
Provides robust versioning, replication, and sync capabilities for mobile workflows.
File Geodatabase:
Supports single-user access and lacks enterprise-grade indexing and multiuser editing capabilities.
Does not meet the requirements for web and mobile app editing.
Mobile Geodatabase:
Optimized for mobile apps but does not support the enterprise-level indexing and multiuser workflows required for this scenario.
Steps for Storing and Optimizing Feature Classes:
Store the feature classes in an enterprise geodatabase.
Create indexes on frequently queried columns to optimize performance for mobile and web app queries.
Use tools like ArcGIS Pro to publish feature services for mobile and web app editing.
Reference:
Esri Documentation: Enterprise Geodatabases Overview.
Indexing for Performance Optimization: Guidelines for improving query performance in enterprise environments.
Why the Correct Answer is A: Enterprise geodatabases are the only storage option that supports multiuser editing in mobile and web apps and provides advanced indexing capabilities. File and mobile geodatabases lack the necessary functionality for this use case.
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?
Scenario Overview:
Five feature classes are added to a feature dataset, which is registered as versioned without the move-edits-to-base option.
Afterward, another feature class is added to the same feature dataset.
Users encounter errors when trying to edit any feature class in the feature dataset.
Cause of the Problem: When a feature dataset is registered as versioned, all feature classes within it must maintain consistency in their versioning state. Adding a new feature class to a previously versioned feature dataset can disrupt the synchronization, causing errors during editing.
Solution:
Unregister as versioned on the feature dataset: This removes versioning from all feature classes in the dataset, resetting their versioning state.
Register the feature dataset as versioned again: This ensures all feature classes, including the newly added one, are correctly registered with the same versioning state. (ArcGIS Documentation: Registering Datasets as Versioned)
Alternative Options:
Option B: Registering the feature dataset again would not resolve the issue because versioning conflicts persist unless the entire feature dataset is unregistered and re-registered.
Option C: Switching to the move-edits-to-base option is unnecessary and alters the editing workflow, which may not align with the current setup or user needs.
Thus, the administrator should unregister the feature dataset as versioned and re-register it to resolve the errors.
A GIS administrator needs to simultaneously grant access for multiple users of a branch versioned feature class in an enterprise geodatabase.
How should permissions be granted?
Understanding the Scenario: The GIS administrator wants to simultaneously grant access to multiple users for a branch-versioned feature class in an enterprise geodatabase. Managing permissions for individual users can be inefficient, especially for larger teams, making roles a better solution.
Why Grant Permissions to a Role:
Role-Based Access Control (RBAC): In enterprise geodatabases, assigning permissions to a role allows administrators to define access levels once and apply them to multiple users who are members of that role. This simplifies management and ensures consistent permission levels across users.
Branch Versioning Considerations: In branch versioned datasets, role-based permissions ensure that all users working with the feature class can access, edit, or view data as needed without individual customization.
Steps to Assign Permissions to a Role:
Create a role in the database or use an existing one.
Assign permissions for the branch versioned feature class to the role (e.g., read, edit, or administrative permissions).
Add users to the role.
All users in the role inherit the permissions automatically.
Reference:
Esri Documentation: Best practices for managing permissions in enterprise geodatabases: Managing Users and Roles.
Branch Versioning Overview: Information on the unique requirements for branch versioned data: Branch Versioning.
Why the Correct Answer is A: Using roles allows the GIS administrator to efficiently grant and manage access for multiple users at once. Options like lists or groups are not applicable in the context of enterprise geodatabases, as roles are the standard mechanism for assigning permissions.
65 questions covering all exam domains, starting from $20
Exam domains verified against: Official Esri EGMP2201 exam guide, last checked September 2026.
Design geodatabases that align with organizational needs. Develop geodatabase strategy including data association options in normalized models and appropriate methods for storing and serving data.
Sample question from this domain above: Q2
Create, enable, and set up enterprise geodatabases with secure data models. Configure distributed data systems for efficient access and management across the organization.
Handle data migration using various loading options and SQL techniques. Ensure smooth workflows for data migration and geodatabase upgrades.
Troubleshoot and resolve performance issues using system table data. Create and manage indexes, address versioning problems, and optimize database performance.
Common questions about the exam itself
