Practice Free EGMP2201 Exam Online Questions
Question #1
A GIS data administrator needs to store color, model, and size attributes for different kinds of valves.
Pick lists should only show permitted combinations of color, model, and size.
Which geodatabase capability should be configured?
- A . Domains
- B . Subtypes with domains
- C . Contingent values
Correct Answer: C
C
Explanation:
Scenario Overview:
The administrator needs to store attributes for valves (e.g., color, model, and size).
Pick lists must display only valid combinations of these attributes.
Why Contingent Values?
Contingent values allow geodatabases to enforce specific, dependent attribute combinations. For example, if certain sizes are only valid for specific models and colors, contingent values ensure only permitted combinations are displayed in pick lists. (ArcGIS Documentation: Contingent Values)
How Contingent Values Work:
Attribute domains are defined for individual fields (e.g., color, model, size).
Contingent value rules are configured to establish relationships between the fields, restricting invalid combinations.
When editing data, pick lists dynamically adjust based on contingent value rules, showing only valid options.
Alternative Options:
Option A: Domains
Attribute domains enforce constraints on individual fields but cannot define dependencies between fields.
Option B: Subtypes with domains
Subtypes group features into categories with distinct domain rules but do not support interdependent attribute combinations.
Thus, contingent values are the appropriate geodatabase capability to configure pick lists for valid attribute combinations.
C
Explanation:
Scenario Overview:
The administrator needs to store attributes for valves (e.g., color, model, and size).
Pick lists must display only valid combinations of these attributes.
Why Contingent Values?
Contingent values allow geodatabases to enforce specific, dependent attribute combinations. For example, if certain sizes are only valid for specific models and colors, contingent values ensure only permitted combinations are displayed in pick lists. (ArcGIS Documentation: Contingent Values)
How Contingent Values Work:
Attribute domains are defined for individual fields (e.g., color, model, size).
Contingent value rules are configured to establish relationships between the fields, restricting invalid combinations.
When editing data, pick lists dynamically adjust based on contingent value rules, showing only valid options.
Alternative Options:
Option A: Domains
Attribute domains enforce constraints on individual fields but cannot define dependencies between fields.
Option B: Subtypes with domains
Subtypes group features into categories with distinct domain rules but do not support interdependent attribute combinations.
Thus, contingent values are the appropriate geodatabase capability to configure pick lists for valid attribute combinations.
Question #1
A GIS data administrator needs to store color, model, and size attributes for different kinds of valves.
Pick lists should only show permitted combinations of color, model, and size.
Which geodatabase capability should be configured?
- A . Domains
- B . Subtypes with domains
- C . Contingent values
Correct Answer: C
C
Explanation:
Scenario Overview:
The administrator needs to store attributes for valves (e.g., color, model, and size).
Pick lists must display only valid combinations of these attributes.
Why Contingent Values?
Contingent values allow geodatabases to enforce specific, dependent attribute combinations. For example, if certain sizes are only valid for specific models and colors, contingent values ensure only permitted combinations are displayed in pick lists. (ArcGIS Documentation: Contingent Values)
How Contingent Values Work:
Attribute domains are defined for individual fields (e.g., color, model, size).
Contingent value rules are configured to establish relationships between the fields, restricting invalid combinations.
When editing data, pick lists dynamically adjust based on contingent value rules, showing only valid options.
Alternative Options:
Option A: Domains
Attribute domains enforce constraints on individual fields but cannot define dependencies between fields.
Option B: Subtypes with domains
Subtypes group features into categories with distinct domain rules but do not support interdependent attribute combinations.
Thus, contingent values are the appropriate geodatabase capability to configure pick lists for valid attribute combinations.
C
Explanation:
Scenario Overview:
The administrator needs to store attributes for valves (e.g., color, model, and size).
Pick lists must display only valid combinations of these attributes.
Why Contingent Values?
Contingent values allow geodatabases to enforce specific, dependent attribute combinations. For example, if certain sizes are only valid for specific models and colors, contingent values ensure only permitted combinations are displayed in pick lists. (ArcGIS Documentation: Contingent Values)
How Contingent Values Work:
Attribute domains are defined for individual fields (e.g., color, model, size).
Contingent value rules are configured to establish relationships between the fields, restricting invalid combinations.
When editing data, pick lists dynamically adjust based on contingent value rules, showing only valid options.
Alternative Options:
Option A: Domains
Attribute domains enforce constraints on individual fields but cannot define dependencies between fields.
Option B: Subtypes with domains
Subtypes group features into categories with distinct domain rules but do not support interdependent attribute combinations.
Thus, contingent values are the appropriate geodatabase capability to configure pick lists for valid attribute combinations.
Question #3
A user wants to share a frequently edited points feature class as a web layer. The points contain sensitive attributes and will be read-only for online viewers.
The following workflow is applied:
• Points is registered as versioned
• A standard database view is created for points, which hides the sensitive attributes
• The view is published as a web layer from the Default version
As the points feature class is edited throughout the week, edits are not visible in the web layer.
What should the GIS administrator do?
- A . Have all editors reconcile and post points edits to Default
- B . Rebuild indexes and calculate database statistics on points
- C . Alter the view to use a versioned view as the source
Correct Answer: C
C
Explanation:
The issue arises because the standard database view is based on the base table of the points feature class, which does not include edits made in child versions. To resolve this, the database view must reference a versioned view to reflect changes in the Default version.
C
Explanation:
The issue arises because the standard database view is based on the base table of the points feature class, which does not include edits made in child versions. To resolve this, the database view must reference a versioned view to reflect changes in the Default version.
Question #4
A GIS administrator needs to make a synchronized copy of a branch versioned dataset. Editing must be performed on both copies.
How should the data be replicated?
- A . Distributed collaboration
- B . Geodatabase replication
- C . DBMS replication
Correct Answer: B
B
Explanation:
Scenario Overview:
The GIS administrator needs to create a synchronized copy of a branch versioned dataset.
Both copies must allow editing.
Why Geodatabase Replication?
Geodatabase replication supports the creation of synchronized copies of datasets while allowing edits in both the parent and child geodatabases.
For branch versioned data, replication ensures that edits made in either the parent or child
geodatabase can be synchronized using a two-way replica.
(ArcGIS Documentation: Geodatabase Replication)
Key Features of Geodatabase Replication for This Scenario:
Two-way replication enables editing on both sides while synchronizing changes.
Supports branch versioning, ensuring versioned workflows remain intact.
Maintains schema consistency across both geodatabases.
Alternative Options:
Option A: Distributed Collaboration
Collaboration is suitable for sharing data across ArcGIS Enterprise environments but does not support
active synchronization for editing on both sides.
Option C: DBMS Replication
DBMS-level replication handles raw data replication but does not preserve geodatabase-specific functionalities, such as branch versioning.
Thus, geodatabase replication is the correct method for synchronizing and editing branch versioned datasets in both geodatabases.
B
Explanation:
Scenario Overview:
The GIS administrator needs to create a synchronized copy of a branch versioned dataset.
Both copies must allow editing.
Why Geodatabase Replication?
Geodatabase replication supports the creation of synchronized copies of datasets while allowing edits in both the parent and child geodatabases.
For branch versioned data, replication ensures that edits made in either the parent or child
geodatabase can be synchronized using a two-way replica.
(ArcGIS Documentation: Geodatabase Replication)
Key Features of Geodatabase Replication for This Scenario:
Two-way replication enables editing on both sides while synchronizing changes.
Supports branch versioning, ensuring versioned workflows remain intact.
Maintains schema consistency across both geodatabases.
Alternative Options:
Option A: Distributed Collaboration
Collaboration is suitable for sharing data across ArcGIS Enterprise environments but does not support
active synchronization for editing on both sides.
Option C: DBMS Replication
DBMS-level replication handles raw data replication but does not preserve geodatabase-specific functionalities, such as branch versioning.
Thus, geodatabase replication is the correct method for synchronizing and editing branch versioned datasets in both geodatabases.
Question #4
A GIS administrator needs to make a synchronized copy of a branch versioned dataset. Editing must be performed on both copies.
How should the data be replicated?
- A . Distributed collaboration
- B . Geodatabase replication
- C . DBMS replication
Correct Answer: B
B
Explanation:
Scenario Overview:
The GIS administrator needs to create a synchronized copy of a branch versioned dataset.
Both copies must allow editing.
Why Geodatabase Replication?
Geodatabase replication supports the creation of synchronized copies of datasets while allowing edits in both the parent and child geodatabases.
For branch versioned data, replication ensures that edits made in either the parent or child
geodatabase can be synchronized using a two-way replica.
(ArcGIS Documentation: Geodatabase Replication)
Key Features of Geodatabase Replication for This Scenario:
Two-way replication enables editing on both sides while synchronizing changes.
Supports branch versioning, ensuring versioned workflows remain intact.
Maintains schema consistency across both geodatabases.
Alternative Options:
Option A: Distributed Collaboration
Collaboration is suitable for sharing data across ArcGIS Enterprise environments but does not support
active synchronization for editing on both sides.
Option C: DBMS Replication
DBMS-level replication handles raw data replication but does not preserve geodatabase-specific functionalities, such as branch versioning.
Thus, geodatabase replication is the correct method for synchronizing and editing branch versioned datasets in both geodatabases.
B
Explanation:
Scenario Overview:
The GIS administrator needs to create a synchronized copy of a branch versioned dataset.
Both copies must allow editing.
Why Geodatabase Replication?
Geodatabase replication supports the creation of synchronized copies of datasets while allowing edits in both the parent and child geodatabases.
For branch versioned data, replication ensures that edits made in either the parent or child
geodatabase can be synchronized using a two-way replica.
(ArcGIS Documentation: Geodatabase Replication)
Key Features of Geodatabase Replication for This Scenario:
Two-way replication enables editing on both sides while synchronizing changes.
Supports branch versioning, ensuring versioned workflows remain intact.
Maintains schema consistency across both geodatabases.
Alternative Options:
Option A: Distributed Collaboration
Collaboration is suitable for sharing data across ArcGIS Enterprise environments but does not support
active synchronization for editing on both sides.
Option C: DBMS Replication
DBMS-level replication handles raw data replication but does not preserve geodatabase-specific functionalities, such as branch versioning.
Thus, geodatabase replication is the correct method for synchronizing and editing branch versioned datasets in both geodatabases.
Question #4
A GIS administrator needs to make a synchronized copy of a branch versioned dataset. Editing must be performed on both copies.
How should the data be replicated?
- A . Distributed collaboration
- B . Geodatabase replication
- C . DBMS replication
Correct Answer: B
B
Explanation:
Scenario Overview:
The GIS administrator needs to create a synchronized copy of a branch versioned dataset.
Both copies must allow editing.
Why Geodatabase Replication?
Geodatabase replication supports the creation of synchronized copies of datasets while allowing edits in both the parent and child geodatabases.
For branch versioned data, replication ensures that edits made in either the parent or child
geodatabase can be synchronized using a two-way replica.
(ArcGIS Documentation: Geodatabase Replication)
Key Features of Geodatabase Replication for This Scenario:
Two-way replication enables editing on both sides while synchronizing changes.
Supports branch versioning, ensuring versioned workflows remain intact.
Maintains schema consistency across both geodatabases.
Alternative Options:
Option A: Distributed Collaboration
Collaboration is suitable for sharing data across ArcGIS Enterprise environments but does not support
active synchronization for editing on both sides.
Option C: DBMS Replication
DBMS-level replication handles raw data replication but does not preserve geodatabase-specific functionalities, such as branch versioning.
Thus, geodatabase replication is the correct method for synchronizing and editing branch versioned datasets in both geodatabases.
B
Explanation:
Scenario Overview:
The GIS administrator needs to create a synchronized copy of a branch versioned dataset.
Both copies must allow editing.
Why Geodatabase Replication?
Geodatabase replication supports the creation of synchronized copies of datasets while allowing edits in both the parent and child geodatabases.
For branch versioned data, replication ensures that edits made in either the parent or child
geodatabase can be synchronized using a two-way replica.
(ArcGIS Documentation: Geodatabase Replication)
Key Features of Geodatabase Replication for This Scenario:
Two-way replication enables editing on both sides while synchronizing changes.
Supports branch versioning, ensuring versioned workflows remain intact.
Maintains schema consistency across both geodatabases.
Alternative Options:
Option A: Distributed Collaboration
Collaboration is suitable for sharing data across ArcGIS Enterprise environments but does not support
active synchronization for editing on both sides.
Option C: DBMS Replication
DBMS-level replication handles raw data replication but does not preserve geodatabase-specific functionalities, such as branch versioning.
Thus, geodatabase replication is the correct method for synchronizing and editing branch versioned datasets in both geodatabases.
Question #7
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?
- A . Unregister as versioned on the feature dataset and then register as versioned again
- B . Register as versioned on the feature dataset one additional time
- C . Switch the editing workflow to versioned editing with the move-edits-to-base option
Correct Answer: A
A
Explanation:
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
Explanation:
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.
Question #8
A data owner creates a one-way replica parent-to-child for a single feature class to share data from a production geodatabase to a public-facing geodatabase.
• The data owner synchronizes once a week to share updated data
• In time, the data owner wants to add a new attribute field/field type and calculates new attribute values
• The data owner synchronizes the replicas, but the new field and values are not present in the child replica
• In the public-facing geodatabase, the data owner adds the same attribute field and field type
• The data owner synchronizes the replicas again, and the values are not replicated in the child replica
How should the data owner resolve this issue?
- A . Unregister the replica pair?, run Enable Replica Tracking and Synchronize Change?
- B . Unregister the replica pairs, run Feature Compare and Synchronize Changes
- C . Unregister the replica pairs, recreate the replica, and Synchronize Changes
Correct Answer: C
C
Explanation:
Scenario Overview:
A one-way replica from parent to child geodatabase is created for a single feature class.
The data owner adds a new attribute field in the parent geodatabase, calculates values, and attempts to synchronize the replica.
The new field and its values do not appear in the child replica, even after manually adding the field to
the child geodatabase.
Why Recreate the Replica?
The issue arises because schema changes (e.g., adding new fields) are not automatically propagated in one-way replication workflows. Synchronization only applies to data changes, not schema updates. To ensure the schema changes are recognized, the replica pair must be recreated with the updated schema.
(ArcGIS Documentation: Geodatabase Replication and Schema Changes)
Steps to Resolve the Issue:
Unregister the Replica: Remove the existing replica pair from both the parent and child geodatabases.
Recreate the Replica: Create a new one-way replica between the parent and child geodatabases. This
new replica will include the updated schema.
Synchronize Changes: Perform synchronization to transfer data, including the new field and
calculated values, to the child geodatabase.
Alternative Options:
Option A: Enabling replica tracking does not address schema synchronization and would not resolve the issue.
Option B: Running Feature Compare is helpful for analyzing schema differences but does not propagate schema changes.
Thus, the data owner must unregister the replica pairs, recreate the replica with the updated schema, and synchronize changes to resolve the issue.
C
Explanation:
Scenario Overview:
A one-way replica from parent to child geodatabase is created for a single feature class.
The data owner adds a new attribute field in the parent geodatabase, calculates values, and attempts to synchronize the replica.
The new field and its values do not appear in the child replica, even after manually adding the field to
the child geodatabase.
Why Recreate the Replica?
The issue arises because schema changes (e.g., adding new fields) are not automatically propagated in one-way replication workflows. Synchronization only applies to data changes, not schema updates. To ensure the schema changes are recognized, the replica pair must be recreated with the updated schema.
(ArcGIS Documentation: Geodatabase Replication and Schema Changes)
Steps to Resolve the Issue:
Unregister the Replica: Remove the existing replica pair from both the parent and child geodatabases.
Recreate the Replica: Create a new one-way replica between the parent and child geodatabases. This
new replica will include the updated schema.
Synchronize Changes: Perform synchronization to transfer data, including the new field and
calculated values, to the child geodatabase.
Alternative Options:
Option A: Enabling replica tracking does not address schema synchronization and would not resolve the issue.
Option B: Running Feature Compare is helpful for analyzing schema differences but does not propagate schema changes.
Thus, the data owner must unregister the replica pairs, recreate the replica with the updated schema, and synchronize changes to resolve the issue.
Question #9
A GIS data administrator frequently changes the map based on definition queries. A noticeable lag occurs when changing the parameter value of the definition query.
Which action should be taken?
- A . Add Attribute Index
- B . Add Spatial Index
- C . Recalculate Extent
Correct Answer: A
A
Explanation:
Scenario Overview:
The GIS data administrator is experiencing lag when changing the parameter value of a definition query.
Definition queries dynamically filter data based on attribute values. Slow performance often indicates inefficient attribute searches.
Solution: Add Attribute Index
An attribute index allows the database to quickly locate rows based on values in the indexed column, significantly improving query performance.
When definition queries rely on non-indexed fields, the database must scan the entire dataset to filter records, leading to noticeable delays.
By creating an attribute index on the fields used in the definition query, the database can optimize filtering, reducing lag.
(ArcGIS Documentation: Attribute Indexes)
Steps to Add Attribute Index:
In ArcGIS Pro, open the Attribute Indexes tool.
Select the feature class or table used in the definition query.
Specify the field(s) that the definition query is based on.
Click Run to create the index.
Alternative Options:
Option B: Add Spatial Index
Spatial indexes optimize spatial queries (e.g., finding features within an area). This does not address
attribute-based definition query lag.
Option C: Recalculate Extent
Recalculating the extent corrects boundary discrepancies in spatial datasets but has no impact on attribute query performance.
Thus, adding an attribute index is the correct action to resolve lag in definition queries.
A
Explanation:
Scenario Overview:
The GIS data administrator is experiencing lag when changing the parameter value of a definition query.
Definition queries dynamically filter data based on attribute values. Slow performance often indicates inefficient attribute searches.
Solution: Add Attribute Index
An attribute index allows the database to quickly locate rows based on values in the indexed column, significantly improving query performance.
When definition queries rely on non-indexed fields, the database must scan the entire dataset to filter records, leading to noticeable delays.
By creating an attribute index on the fields used in the definition query, the database can optimize filtering, reducing lag.
(ArcGIS Documentation: Attribute Indexes)
Steps to Add Attribute Index:
In ArcGIS Pro, open the Attribute Indexes tool.
Select the feature class or table used in the definition query.
Specify the field(s) that the definition query is based on.
Click Run to create the index.
Alternative Options:
Option B: Add Spatial Index
Spatial indexes optimize spatial queries (e.g., finding features within an area). This does not address
attribute-based definition query lag.
Option C: Recalculate Extent
Recalculating the extent corrects boundary discrepancies in spatial datasets but has no impact on attribute query performance.
Thus, adding an attribute index is the correct action to resolve lag in definition queries.
Question #10
An organization has ArcGIS Enterprise. A new project requires versioned editing with the ability to show which user deleted a feature from the default version.
Which editing workflow should be used?
- A . Branch versioned editing
- B . Traditional versioned editing
- C . Nonversioned editing
Correct Answer: A
A
Explanation:
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.
A
Explanation:
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.