Practice Free EGMP2201 Exam Online Questions
Question #31
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?
- A . Disable schema locking on the service
- B . Run the Alter Field geoprocessing tool
- C . Delete the spatial index
Correct Answer: A
A
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.
A
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.
Question #31
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?
- A . Disable schema locking on the service
- B . Run the Alter Field geoprocessing tool
- C . Delete the spatial index
Correct Answer: A
A
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.
A
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.
Question #33
A user plans to use a standard database view of a roads feature class from a geodatabase that is different from the primary enterprise geodatabase. Roads is frequently edited in the parent geodatabase, so the user needs to regularly synchronize and have the view recognize all incoming edits immediately.
Which replica type should be used?
- A . One-way replica with the simple model
- B . One-way replica with the full model
- C . Two-way replication simple model
Correct Answer: B
B
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.
B
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.
Question #33
A user plans to use a standard database view of a roads feature class from a geodatabase that is different from the primary enterprise geodatabase. Roads is frequently edited in the parent geodatabase, so the user needs to regularly synchronize and have the view recognize all incoming edits immediately.
Which replica type should be used?
- A . One-way replica with the simple model
- B . One-way replica with the full model
- C . Two-way replication simple model
Correct Answer: B
B
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.
B
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.
Question #35
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?
- A . Enterprise geodatabase
- B . File geodatabase
- C . Mobile geodatabase
Correct Answer: A
A
Explanation:
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.
A
Explanation:
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.
Question #36
A GIS analyst needs to share a large repository of lidar data with the organization. This lidar data will
have surface constraints applied for breaklines.
Which type of dataset should the GIS analyst use?
- A . Mosaic dataset
- B . Feature dataset
- C . LAS dataset
Correct Answer: C
C
Explanation:
Understanding the Scenario:
The GIS analyst needs to share a large repository of lidar data.
The data includes surface constraints like breaklines, which are used to enforce terrain or surface
rules.
Dataset Types Overview: Mosaic Dataset:
Designed for managing large collections of raster data, such as imagery or elevation grids. It is not specifically optimized for lidar point cloud data.
Feature Dataset:
A container for related feature classes in a geodatabase. It is unrelated to managing lidar data or surface constraints.
LAS Dataset:
A specialized dataset designed for managing lidar point clouds. It supports point classification, surface constraints (like breaklines), and efficient querying or visualization of lidar data.
Steps to Create and Share a LAS Dataset:
Create a LAS dataset in ArcGIS Pro and add lidar files (LAS or ZLAS format).
Define surface constraints (breaklines) in the LAS dataset properties.
Share the LAS dataset as a service or package for organizational access.
Reference: Esri Documentation: LAS Datasets.
Managing Breaklines in LAS Datasets: Instructions for incorporating surface constraints.
Why the Correct Answer is C:
LAS datasets are explicitly designed for managing and sharing lidar data with surface constraints like breaklines. Mosaic and feature datasets are unsuitable for this purpose.
C
Explanation:
Understanding the Scenario:
The GIS analyst needs to share a large repository of lidar data.
The data includes surface constraints like breaklines, which are used to enforce terrain or surface
rules.
Dataset Types Overview: Mosaic Dataset:
Designed for managing large collections of raster data, such as imagery or elevation grids. It is not specifically optimized for lidar point cloud data.
Feature Dataset:
A container for related feature classes in a geodatabase. It is unrelated to managing lidar data or surface constraints.
LAS Dataset:
A specialized dataset designed for managing lidar point clouds. It supports point classification, surface constraints (like breaklines), and efficient querying or visualization of lidar data.
Steps to Create and Share a LAS Dataset:
Create a LAS dataset in ArcGIS Pro and add lidar files (LAS or ZLAS format).
Define surface constraints (breaklines) in the LAS dataset properties.
Share the LAS dataset as a service or package for organizational access.
Reference: Esri Documentation: LAS Datasets.
Managing Breaklines in LAS Datasets: Instructions for incorporating surface constraints.
Why the Correct Answer is C:
LAS datasets are explicitly designed for managing and sharing lidar data with surface constraints like breaklines. Mosaic and feature datasets are unsuitable for this purpose.
Question #37
An organization has an enterprise geodatabase used for editing and public use. Editors are experiencing performance issues during peak hours. The GIS data administrator needs to make sure that the editing and public usage do not affect each other.
Which action should be taken?
- A . Build new feature datasets
- B . Separate permissions for public services
- C . Create separate database instances
Correct Answer: C
C
Explanation:
To ensure that editing and public usage do not affect each other, the best approach is to create separate database instances for these purposes.
C
Explanation:
To ensure that editing and public usage do not affect each other, the best approach is to create separate database instances for these purposes.
Question #37
An organization has an enterprise geodatabase used for editing and public use. Editors are experiencing performance issues during peak hours. The GIS data administrator needs to make sure that the editing and public usage do not affect each other.
Which action should be taken?
- A . Build new feature datasets
- B . Separate permissions for public services
- C . Create separate database instances
Correct Answer: C
C
Explanation:
To ensure that editing and public usage do not affect each other, the best approach is to create separate database instances for these purposes.
C
Explanation:
To ensure that editing and public usage do not affect each other, the best approach is to create separate database instances for these purposes.
Question #39
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?
- A . Export to shapefile
- B . Join to another feature class
- C . Register with geodatabase
Correct Answer: C
C
Explanation:
When a database view performs poorly in a map, registering it with the geodatabase can significantly improve performance.
C
Explanation:
When a database view performs poorly in a map, registering it with the geodatabase can significantly improve performance.
Question #40
A GIS data administrator needs to load a large amount of data into a version, verify its quality, and then reconcile and post this version to default. The data administrator needs to create the fewest number of rows in the database.
Which versioning method should be used?
- A . Traditional versioning without the archiving option
- B . Traditional versioning with the archiving option
- C . Branch versioning
Correct Answer: A
A
Explanation:
To minimize the number of rows created in the database while performing versioning workflows (loading, quality checking, reconciling, and posting), Traditional versioning without the archiving option is the best choice.
A
Explanation:
To minimize the number of rows created in the database while performing versioning workflows (loading, quality checking, reconciling, and posting), Traditional versioning without the archiving option is the best choice.