QUESTION: 21

The GIS administrator does not have the database administrator credentials and needs to create an enterprise geodatabase for storage of vector dat

The database administrator will provide a database with the appropriate users and permissions for use.
Which tool should the GIS administrator use?
Create Feature Dataset
Enable Enterprise Geodatabase
Create Enterprise Geodatabase

Answer(s): B

Explanation:

Understanding the Scenario:
The GIS administrator lacks database administrator credentials but requires an enterprise geodatabase for vector data storage. In this setup, the database administrator (DBA) is responsible for preparing the database, including setting up users and permissions, while the GIS administrator is tasked with enabling it as an enterprise geodatabase.
Tool Selection Overview:
Create Feature Dataset:
This tool is for creating a logical grouping of related feature classes inside an existing geodatabase. It is unrelated to enabling or creating an enterprise geodatabase.
Enable Enterprise Geodatabase:
This tool is used when a database has already been created and configured by the DBA, and the GIS administrator needs to enable it as an enterprise geodatabase. It adds geodatabase system tables and functionality to the database. This aligns with the scenario described.
Create Enterprise Geodatabase:
This tool creates a new database and configures it as an enterprise geodatabase in one step.

However, this tool requires database administrator credentials, which the GIS administrator in this scenario does not have.
Key Steps to Enable an Enterprise Geodatabase:
Preparation by DBA:
The DBA sets up the database, ensuring the appropriate users and permissions are in place. They also provide connection details to the GIS administrator.
Using the Enable Enterprise Geodatabase Tool:
Navigate to ArcGIS Pro or ArcGIS Enterprise tools.
Open the Enable Enterprise Geodatabase tool.
Specify the database connection file for the target database. Provide the authorization file (a valid ArcGIS Server Enterprise license file) to enable geodatabase functionality.

Execute the tool to add system tables, stored procedures, and geodatabase functionality to the database.

Reference:

ArcGIS Pro Documentation on Enable Enterprise Geodatabase. Esri Enterprise Geodatabase Concepts: Official Esri documentation provides comprehensive details on the role of DBAs and GIS administrators in setting up enterprise geodatabases. ArcGIS Enterprise Licensing Guide: Detailed information about authorization files for enabling geodatabases.
Why the Correct Answer is B:
The tool "Enable Enterprise Geodatabase" is specifically designed for situations where the database setup is handled by a DBA, and the GIS administrator is responsible only for enabling geodatabase capabilities. Since the GIS administrator does not have DBA credentials, they cannot use the "Create Enterprise Geodatabase" tool, which would require those credentials to create and configure a new database.

Reveal Solution Next Question

QUESTION: 22

A GIS administrator needs to simultaneously grant access for multiple users of a branch versioned feature class in an enterprise geodatabase.
How should permissions be granted?

To a role
To a list
To a group

Answer(s): A

Explanation:

Understanding the Scenario:
The GIS administrator wants to simultaneously grant access to multiple users for a branch-versioned feature class in an enterprise geodatabase. Managing permissions for individual users can be inefficient, especially for larger teams, making roles a better solution.
Why Grant Permissions to a Role:
Role-Based Access Control (RBAC):
In enterprise geodatabases, assigning permissions to a role allows administrators to define access levels once and apply them to multiple users who are members of that role. This simplifies management and ensures consistent permission levels across users.
Branch Versioning Considerations:
In branch versioned datasets, role-based permissions ensure that all users working with the feature class can access, edit, or view data as needed without individual customization.
Steps to Assign Permissions to a Role:
Create a role in the database or use an existing one. Assign permissions for the branch versioned feature class to the role (e.g., read, edit, or administrative permissions).
Add users to the role.
All users in the role inherit the permissions automatically.

Reference:

Esri Documentation: Best practices for managing permissions in enterprise geodatabases: Managing Users and Roles.
Branch Versioning Overview: Information on the unique requirements for branch versioned data:
Branch Versioning.
Why the Correct Answer is A:
Using roles allows the GIS administrator to efficiently grant and manage access for multiple users at once. Options like lists or groups are not applicable in the context of enterprise geodatabases, as roles are the standard mechanism for assigning permissions.

Reveal Solution Next Question

QUESTION: 23

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?

Remove the objectid index before Append
Remove the spatial index before Append
Add a unique key index before Append

Answer(s): B

Explanation:

Understanding the Scenario:
The database administrator wants to improve the performance of a nightly data load process, which involves truncating and appending a large table with geometry and several attributes. The current Append operation takes 120 minutes, and indexes are re-created after the data is loaded.
Identifying the Bottleneck:
Spatial indexes speed up query performance but can significantly slow down data loading operations like Append.

When loading large datasets, maintaining the spatial index during the operation forces constant updates, leading to performance degradation.
Recommended Optimization:
Removing the Spatial Index:
Before the Append operation, drop the spatial index to eliminate overhead during data insertion. After the Append operation completes, recreate the spatial index to restore query performance. This approach ensures that the Append process only focuses on inserting records without additional computational load from maintaining the spatial index.
Steps to Implement the Recommendation:
Drop the spatial index using the appropriate database management command or tool.
Execute the Append process.
Rebuild the spatial index once the Append process is complete.

Reference:

Esri Documentation: Best practices for large data loads: Managing Indexes. Spatial Index Concepts: Understanding how spatial indexes impact data loading operations.
Why the Correct Answer is B:
Removing the spatial index before appending large datasets can significantly reduce the time required for data insertion. Options A (removing the objectid index) and C (adding a unique key index) are irrelevant because the objectid index is system-managed and the unique key index creation would not improve the performance of the Append operation.

Reveal Solution Next Question

QUESTION: 24

ArcGIS Pro users must be able to use the Undo and Redo buttons while editing a dataset. At the same time, SQL users must be able to edit this dataset.
How should the ArcGIS data administrator configure this dataset?

Nonversioned editing
Traditional versioning
Branch versioning

Answer(s): B

Explanation:

Understanding the Scenario:
ArcGIS Pro users need Undo/Redo functionality, which is available in versioned workflows. SQL users also need to edit the dataset, requiring direct access to the database tables. These requirements point to a need for a versioning method that supports both ArcGIS client workflows and SQL-based edits.
Versioning Methods Overview:
Nonversioned Editing:
Nonversioned editing allows direct editing of the database but does not support Undo/Redo functionality in ArcGIS Pro, making it unsuitable for this scenario.
Traditional Versioning:
Supports Undo/Redo functionality for ArcGIS Pro users. Stores edits in delta tables (adds and deletes) to manage versions. SQL users can access and edit the base tables, making it compatible with their needs.

Branch Versioning:
Branch versioning supports modern workflows and web services but requires a service-based approach for editing. It does not allow direct SQL edits, making it unsuitable for this scenario.
Steps to Implement Traditional Versioning:
Enable traditional versioning on the dataset in the enterprise geodatabase. Ensure appropriate permissions are set for SQL users to access and edit the base tables. ArcGIS Pro users will work in the versioned environment, allowing Undo/Redo operations during their edits.

Reference:

Esri Documentation: Understanding Versioning.
Traditional Versioning Concepts: Best practices for using traditional versioning with multiple user types.

Why the Correct Answer is B:
Traditional versioning fulfills both requirements: Undo/Redo functionality for ArcGIS Pro users and SQL accessibility for direct edits.

Reveal Solution Next Question

Free EGMP2201 Exam Braindumps (page: 6)

QUESTION: 21

Explanation:

Reference:

QUESTION: 22

Explanation:

Reference:

QUESTION: 23

Explanation:

Reference:

QUESTION: 24

Explanation:

Reference: