Esri EGMP2201 Enterprise Geodata Management Professional 2201 Exam Practice Test

Answer : C

Understanding the Scenario:

A user saves a connection file with read/write credentials and creates layer files for visualization.

Viewers access these layer files, potentially exposing the saved credentials.

Key Issue with the Workflow:

Saved Credentials in Connection File: Connection files can store usernames and passwords for convenience, but when shared, the credentials grant others the same level of access as the original user.

Impact of Read/Write Credentials: Viewers can inadvertently perform edits (e.g., add/delete fields or modify data) because the layer files inherit the permissions of the stored connection file.

Steps to Resolve the Issue:

Avoid saving credentials in the connection file or use a connection with read-only access for shared layers.

Use proper publishing workflows to share layers with predefined permissions via feature or map services.

Reference:

Esri Documentation: Sharing Layer Files.

Managing User Access in ArcGIS: Best practices for securing connection files and controlling access levels.

Why the Correct Answer is C: Sharing layer files with stored credentials inadvertently grants viewers the same level of access as the user who created the connection file. This results in viewers being able to perform edits, violating intended data security policies.

Answer : C

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.

Answer : B

Understanding the Scenario:

The feature class cannot have archiving enabled.

Archiving tracks changes over time and requires specific configurations in versioned datasets.

Key Constraints for Enabling Archiving:

Archiving can only be enabled for feature classes registered as versioned without moving edits to base.

Versioned with move edits to base: This configuration directly edits the base table, bypassing the delta tables (adds and deletes) used in traditional versioning. Since archiving relies on delta tables to track changes, this configuration is incompatible with archiving.

Branch Versioned with Editor Tracking: Branch versioning supports editor tracking and web-based workflows but does not currently support archiving.

Steps to Correct the Configuration:

Re-register the feature class as versioned without moving edits to base.

Enable archiving after re-registration.

Reference:

Esri Documentation: Archiving Requirements.

Why the Correct Answer is B: When a feature class is registered as versioned with move edits to base, it does not maintain delta tables, making it incompatible with archiving.

Answer : A

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.

Answer : D

Understanding the Scenario:

The query filters rows based on inspector_name and sorts the results by inspection_date.

Creating an index optimizes data retrieval by reducing the number of rows scanned during the query execution.

Key Considerations for Indexing:

Primary Filter Column: The inspector_name column is the primary filter in the WHERE clause. Indexing this column ensures quick identification of rows matching the filter condition.

Sort Optimization: The ORDER BY inspection_date clause benefits from indexing inspection_date as the second column in a composite index, which accelerates sorting for the filtered results.

Index Selection:

A composite index on inspector_name and inspection_date enables efficient query execution:

inspector_name ensures fast filtering.

inspection_date optimizes sorting.

Indexing unrelated columns like facility_type is unnecessary, as it is not part of the query.

Steps to Create the Index:

In the enterprise geodatabase, use the database management tools or SQL commands to create a composite index:

CREATE INDEX idx_facility_inspections

ON facility_inspections (inspector_name, inspection_date);

Reference:

Esri Documentation: Creating and Managing Indexes.

SQL Indexing Best Practices: Guidelines for composite index creation to optimize queries.

Why the Correct Answer is D: A composite index on inspector_name and inspection_date directly addresses the query structure, optimizing both the WHERE filter and the ORDER BY clause.

Answer : A

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.

Answer : B

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.