매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
Enterprise Geodata Management Professional 2201 온라인 연습
최종 업데이트 시간: 2025년06월06일
당신은 온라인 연습 문제를 통해 Esri EGMP2201 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 EGMP2201 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 65개의 시험 문제와 답을 포함하십시오.
정답:
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.
정답:
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.
정답:
Explanation:
Scenario Overview:
Users experience slowing performance across the geodatabase, particularly for edits and drawing when adding 10,000 records.
The organization performs weekly maintenance tasks:
Rebuilding indexes and statistics
Compressing the geodatabase
Removing orphaned connections
Why Reconcile and Post Versions?
Slow performance in traditional versioning often results from excessive unreconciled versions and a bloated state tree.
Reconciling and posting versions reduces the number of states, enabling geodatabase compression to fully collapse redundant states and improve performance. (ArcGIS Documentation: Reconcile and Post)
Alternative Options:
Option A: Change to use Default version
This bypasses versioning workflows and does not address the root cause of performance degradation.
Option B: Update records via Python
Using Python to update records does not resolve issues caused by unreconciled versions or state tree inefficiencies.
Thus, the correct action is to reconcile and post versions, ensuring the geodatabase state tree is optimized and performance is restored.
정답:
Explanation:
Scenario Overview:
An editor updates 500,000 records in a child version of the Default version using a field calculation.
Another editor updates the Default version, and the child version is reconciled with Default.
What Happens During Reconciliation?
In traditional versioning, edits to feature classes are stored in the Adds and Deletes tables.
During reconciliation:
Changes in the child version that differ from the Default version are duplicated in the Adds and Deletes tables to track the differences.
This allows conflicts to be detected and resolved while preserving all edits.
(ArcGIS Documentation: Traditional Versioning Workflow)
Alternative Options:
Option B: They will be migrated to the Base table
Migration to the base table occurs only when changes are posted and the geodatabase is compressed.
Option C: They will be removed from the States repository table
The States repository table tracks state transitions and is unaffected during reconciliation.
Thus, during reconciliation, the 500,000 records are duplicated in the Adds and Deletes tables to manage and detect conflicts.
정답:
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.
정답:
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.
정답:
Explanation:
Scenario Overview:
The organization has a web service that must always be available.
The service reads data from a feature class in an enterprise geodatabase. The GIS administrator needs to update the schema of the feature class.
Why Disable Schema Locking?
By default, ArcGIS services enforce schema locking to ensure data consistency while the service is active. This prevents any modifications to the feature class schema (e.g., adding fields, altering attributes) while the service is running.
Disabling schema locking allows schema updates to occur without disrupting the service's availability.
(ArcGIS Documentation: Schema Locking)
Steps to Disable Schema Locking:
Access the ArcGIS Server Manager.
Locate the web service and open its service properties.
In the advanced settings, disable the schema locking option.
Perform the required schema updates (e.g., adding fields or modifying the feature class).
Re-enable schema locking if necessary for normal operation.
Alternative Options:
Option B: Run the Alter Field geoprocessing tool
This tool modifies fields but cannot execute schema changes while schema locks are active. Option C: Delete the spatial index
Deleting the spatial index is unrelated to schema changes and could degrade query performance. Thus, the correct workflow is to disable schema locking on the service to allow schema changes without disrupting the web service.
정답:
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.
정답:
Explanation:
Scenario Overview:
The GIS data administrator is unable to upgrade the geodatabase because editors have active sessions and are working on editing workflows.
Active connections lock the geodatabase, preventing upgrades or maintenance operations.
Solution:
Editors must disconnect from their active session to allow the geodatabase upgrade to proceed.
Disconnecting ensures no locks are held on the database objects.
The administrator can also use Geodatabase Administration tools to manually disconnect all users if necessary.
(ArcGIS Documentation: Disconnect Users)
Alternative Options:
Option A: Reconcile and post edit versions is unnecessary as the issue is related to active database sessions, not data versioning.
Option C: Saving edits and stopping editing sessions alone does not close the database connection, leaving locks in place.
Therefore, editors must disconnect from their active session for the geodatabase upgrade to proceed.
정답:
Explanation:
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.
정답:
Explanation:
Scenario Overview:
The analyst creates a join between a large dataset and a nonspatial table to calculate an attribute field.
An error occurs, indicating that the join field is not indexed.
Cause of the Problem:
Joins between datasets rely on indexed fields to optimize the join operation. Without an index, the
system must perform a full table scan, which can lead to errors or slow performance when working
with large datasets.
Solution:
Running the Add Attribute Index tool creates an index on the join field, enabling efficient joining operations.
(ArcGIS Documentation: Attribute Indexes)
Steps to Resolve:
Open the Add Attribute Index tool in ArcGIS Pro.
Select the nonspatial table as the input dataset.
Choose the field used in the join operation as the field to index.
Run the tool to create the attribute index.
Alternative Options:
Option A: Add Spatial Index is irrelevant for nonspatial data.
Option C: Rebuild Indexes reorganizes existing indexes but cannot create new ones, which is required here.
Thus, the analyst should run the Add Attribute Index tool to resolve the error.
정답:
Explanation:
Scenario Overview:
Editors reconcile and post daily, but read-only versions created for analysis are not reconciled or posted.
The geodatabase is compressed nightly, but performance continues to degrade.
Cause of the Problem:
Unreconciled versions, including read-only ones, persist in the state tree, preventing the geodatabase compression from fully collapsing unused states.
Over time, this results in a bloated state tree and worsened performance.
Solution:
Reconciling and posting the read-only versions ensures that the state tree is cleared of unnecessary versions, enabling compression to collapse the database to its optimal state. (ArcGIS Documentation: Reconcile and Post)
Alternative Options:
Option B: Creating a database view provides a read-only representation of data but does not address the underlying issue of unresolved states in the state tree.
Option C: Disabling editor tracking is unrelated to state tree performance issues and has no impact on the reconciliation or compression processes.
Therefore, reconciling the read-only versions will significantly improve performance.
정답:
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.
정답:
Explanation:
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.
정답:
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.