Question 1

A GIS data administrator needs to restrict access to some fields in a feature class from unauthorized users. Which method should the data administrator use?

Accepted Answer

C

Explanation: A database view is a stored SQL query that functions as a virtual table. A data administrator can create a view that selects only a specific subset of fields (columns) from the source feature class's business table. By granting user permissions on this view while revoking or denying permissions on the underlying base table, access to the sensitive fields is effectively restricted at the database level. This is a standard, robust security practice for implementing column-level security in an enterprise geodatabase, ensuring unauthorized users cannot access the restricted data regardless of the client application used.

Question 2

A GIS data manager needs to allow editors to see changes made to the default version in their child versions without reconciling. How should the GIS data manager register the dataset?

Accepted Answer

A

Explanation: The question's premise is technically inaccurate, as editors in child versions must reconcile to see changes from the default version, regardless of the versioning type. However, interpreting the question's likely intent—to allow other applications or non-versioned users to see changes made to the default version—the correct answer is A. Registering a dataset as traditional versioned with the "move edits to base" option ensures that once edits are posted to the default version, they are written directly to the base business tables. This makes the changes immediately visible to any client or application reading the non-versioned state of the data, without requiring them to access a specific version.

Question 3

AGIS data administrator needs to prepare data for use in offline workflows. Which database operation must the data administrator perform?

Accepted Answer

C

Explanation: 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.

Question 4

A GIS database administrator needs to identify any performance issues with a nightly load process.
Upon further research, the database administrator discovers the following:
• A table with 20 million rows is reloaded each night
• This existing table is truncated before an Append is executed
• There are three attributes in addition to objectid and geometry, one of which is a unique text
identifier
• The unique index is removed before Append and created again after Append
• The Append operation takes 120 minutes to complete
What should the administrator recommend?

Accepted Answer

B

Explanation: The most significant performance bottleneck when appending a large volume of spatial data (20 million rows) is the continuous, row-by-row maintenance of the spatial index. Each inserted feature requires a computationally expensive update to the complex grid structure of the spatial index. The established best practice for bulk data loading is to drop the spatial index before the operation, append the data to the table, and then rebuild the index once. This single, holistic index creation process is vastly more efficient than millions of individual index updates. The scenario already correctly follows this practice for the attribute index, making the spatial index the remaining and most impactful element to address.

Question 5

A GIS analyst needs to visualize a centralized folder of imagery with multiple images in ArcGIS Pro.
The administrator needs to prepare for this imagery to be accessed across the organization within
the enterprise geodatabase.
Which storage mechanism should be used?

Accepted Answer

C

Explanation: A mosaic dataset is the optimal storage mechanism for this scenario. It is a data model within an enterprise geodatabase specifically designed to manage, view, and query large collections of raster and image data. It stores metadata and references to the source imagery (which can remain in a centralized folder) rather than the pixels themselves. This allows for dynamic mosaicking, on-the-fly processing, and efficient serving of imagery as a single layer across an organization, which directly meets the administrator's requirements for enterprise-wide access.

Question 6

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?

Accepted Answer

B

Explanation: The post operation fails because the target version, Default, is set to protected. A protected version can only be modified by its owner or a geodatabase administrator. Posting edits from a child version is considered a modification of the parent version. Since the editor is not the owner of the Default version, they lack the necessary permissions to complete the post. The standard workflow in this scenario is for the editor to perform the reconcile to check for conflicts, and then have a user with the appropriate permissions—the owner of Default or a geodatabase administrator—perform the post.

Question 7

All editors reconcile and post their versions daily. Other users create read-only versions for analysis
purposes, so they do not reconcile and post those versions. The geodatabase administrator
compresses the geodatabase nightly. For several months, performance steadily worsens.
Which action should be taken?

Accepted Answer

A

Explanation: The steady performance degradation is caused by the unreconciled read-only versions. In a versioned geodatabase, each version maintains a lineage of database states back to its creation. The nightly COMPRESS operation can only remove states and associated delta table records that are no longer referenced by any version's lineage. Because the read-only versions are never reconciled, they hold references to very old database states. This prevents the COMPRESS operation from cleaning up the state tree and moving records from the delta (A and D) tables to the base tables. Over months, this leads to an increasingly large and complex state tree, which severely degrades query performance for all users. Reconciling these versions updates their lineage to a more current state, allowing COMPRESS to be effective.

Question 8

A telecommunications company implements branch versioning for their organization. The default
version is the published version that portal users see and editors can post edits to.
Which version access level should be set?

Accepted Answer

B

Explanation: The Protected access level is the correct and most secure setting for the default version in a production enterprise environment. This configuration allows all portal users to view the data, fulfilling its role as the published version. Critically, it restricts direct editing and the ability to post changes to only the version owner (typically a data administrator) and the geodatabase administrator. This prevents general editors from modifying the authoritative default version directly, thereby ensuring data integrity. It enforces a controlled workflow where edits from named versions are reviewed and then formally posted by an authorized user, which is a standard best practice.

Question 9

An organization uses a two-way replica to share edits for a polygon feature class with a field office.
After months of synchronizing edits, a schema change takes place using the following workflow;
• A new field called a legal_area is added to a polygon feature class in the parent geodatabase
• An editor uses the Calculate Geometry tool to calculate legal_area for each polygon
• The child geodatabase does not have the legal_area field in the polygon feature class
• The parent geodatabase synchronizes the replica to the child geodatabase
What happens during synchronization?

Accepted Answer

A

Explanation: Geodatabase replication requires that the schema of the replicated datasets be identical across all replicas for data synchronization to succeed. In this scenario, a new field (legalarea) was added to the feature class in the parent geodatabase but not in the child. When the parent attempts to synchronize, it will try to send data edits related to this new field. The child geodatabase's feature class lacks the corresponding legalarea field to receive these edits. This schema mismatch prevents the synchronization process from applying the changes, resulting in a failure and an error message.

Question 10

AGIS data administrator needs to migrate the enterprise geodatabase to another server and wants to
have the following changes:
• New enterprise geodatabase name
• Changed Repository tables owner from SDE to DBO
Which migration workflow should be used?

Accepted Answer

B

Explanation: The required changes—a new geodatabase name and altering the repository owner from SDE to DBO—are fundamental configuration settings established during the geodatabase's initial creation. The only workflow that accommodates these specific changes is to create a new, empty enterprise geodatabase on the target server. During this process, the administrator can define the new name and use the "Enable Enterprise Geodatabase" tool to specify 'DBO' as the geodatabase administrator, which in turn creates the repository tables in the DBO schema. After the new geodatabase is correctly configured, data from the old geodatabase can be migrated into it using methods like XML workspace documents or copy/paste operations.

Question 11

A GIS analyst creates a database view. When the database view is loaded into the map, performance is suboptimal. Which workflow should the analyst use?

Accepted Answer

C

Explanation: Registering a database view with an enterprise geodatabase is the correct workflow to improve performance. This process adds the view to the geodatabase's system tables and, most importantly, defines a unique identifier (ObjectID) field. ArcGIS clients rely on a unique ObjectID for fast feature retrieval, selection, and rendering. Without a registered ObjectID, ArcGIS must scan the view on the fly to identify rows, leading to the suboptimal performance described. Registration allows ArcGIS to leverage database indexes and perform optimized spatial and attribute queries, directly addressing the performance bottleneck.

Question 12

A GIS administrator creates a SQL command to update values in a feature class. In a test
environment, the command is run against the feature class table. All the values do not seem to get
updated.
Which configuration is causing this issue?

Accepted Answer

B

Explanation: In a traditionally versioned geodatabase, edits are not applied directly to the business (base) table. Instead, they are stored in associated delta tables: the adds (A) table and the deletes (D) table. When a user or application views a version, ArcGIS constructs the representation by combining data from the base table with the changes recorded in the delta tables. A direct SQL UPDATE command on the base table bypasses this versioning mechanism. It only modifies rows in the base table. Consequently, any features that have been previously edited within a version (and thus have entries in the delta tables) will not reflect the changes made by the direct SQL command, as the information in the delta tables takes precedence. This results in an apparently incomplete update.

Question 13

An organization has a web service that must always be available. This service reads data from a
feature class in an enterprise geodatabase. The GIS administrator needs to update the schema of the
feature class.
Which workflow should be used?

Accepted Answer

A

Explanation: Enterprise geodatabases use locks to manage access and prevent conflicts. A running web service places a shared lock on its source data, which prevents any operation requiring an exclusive schema lock, such as altering a field. To meet the high-availability requirement (the service must always be available), the intended workflow is to disable schema locking on the service itself. This setting allows the service to temporarily release its lock, enabling an administrator to acquire the necessary exclusive lock to perform schema updates using tools like Alter Field. The service continues to run during this process.

Question 14

A GIS analyst creates a join relationship between a large dataset and a nonspatial table to calculate
an attribute field. Upon building the join, the analyst receives an error message stating that the join
field in the join table is not indexed.
Which tool should the analyst run?

Accepted Answer

B

Explanation: The error message "the join field... is not indexed" explicitly identifies the problem. An attribute index is a data structure that dramatically improves the speed of queries and joins based on attribute fields. When joining large tables, ArcGIS Pro requires or strongly recommends an index on the join field of the join table to perform the operation efficiently. The Add Attribute Index tool is the correct geoprocessing tool to create this necessary index on the specified attribute column, thereby resolving the error and allowing the join to proceed.

Question 15

An organization needs to reduce the number of RDBMS users. ArcGIS Enterprise and ArcGIS Pro are
implemented. Editors need to isolate edits and ensure that edits are reviewed before becoming
public.
Which editing model should the GIS administrator implement?

Accepted Answer

A

Explanation: Branch versioning is the correct model as it is designed for a service-based architecture, which is a key aspect of ArcGIS Enterprise. Editors interact with the data through a feature service, authenticating with their ArcGIS Enterprise named user accounts rather than requiring individual RDBMS user accounts. This directly addresses the primary requirement to reduce the number of RDBMS users. Furthermore, branch versioning provides the necessary functionality for editors to work in isolated versions and allows for a formal review and approval process before edits are merged into the default public version.

Free Esri EGMP2201 Actual Exam Questions