Esri EGMP2201 Exam Dumps

In traditional versioning within an enterprise geodatabase, the Default version often represents the published state of the database. Setting the Default version to protected ensures that while all users can view it, only the geodatabase administrator or the version owner can edit it directly or post changes to it.

ArcGIS Pro

In the scenario provided, the editor follows these steps:

Default Version Set to Protected: This restricts editing and posting privileges to the geodatabase administrator or the version owner.

Creation of a Child Version from Default: The editor creates a new version branching from Default.

Child Version Set to Protected: This means only the editor (as the owner) or the geodatabase administrator can edit this child version.

Edits Saved to the Child Version: The editor makes and saves changes within this child version.

Attempt to Reconcile and Post to Default: The editor successfully reconciles but encounters an error during the post operation.

The error during the post operation arises because, with the Default version set to protected, the editor lacks the necessary permissions to post changes directly to it. Only the geodatabase administrator or the owner of the Default version possesses the authority to perform this action.

ArcGIS Pro

Analysis of Options:

Option A: Changing the access level of the child version from protected to public does not grant the editor the required permissions to post to the protected Default version.

Option B: Requesting the owner of the Default version (typically the geodatabase administrator) to perform the reconcile and post is appropriate. This individual has the necessary permissions to post changes to the protected Default version.

Option C: Creating a one-way replica and synchronizing is an unnecessary and complex approach for this situation.

Therefore, the editor should ask the owner of Default to perform the reconcile and post to ensure the changes are integrated into the Default version.

To determine if the Adds and Deletes tables for the 'Buildings' dataset are empty before unregistering as versioned, the GIS administrator needs to reference the sde_layers table.

1. Purpose of the sde_layers Table

The sde_layers table tracks the relationship between base tables and the associated delta tables (Adds and Deletes).

For each versioned dataset, the sde_layers table contains entries linking the dataset to its corresponding A and D tables (e.g., A_<ObjectID> and D_<ObjectID>).

2. Steps to Verify Adds and Deletes

Identify the ObjectID of the Buildings dataset in the sde_layers table.

Query the Adds table (A_<ObjectID>) and Deletes table (D_<ObjectID>) associated with the Buildings dataset:

SELECT COUNT(*) FROM A_<ObjectID>;

SELECT COUNT(*) FROM D_<ObjectID>;

If both queries return 0, the Adds and Deletes tables are empty, and it is safe to unregister the dataset as versioned.

3. Why Not Other Options?

table_registry: This table tracks registered datasets but does not provide information about delta tables or their contents.

gdb_items: This table stores metadata for datasets but does not have details on delta table contents.

Reference from Esri Documentation and Learning Resources:

Compressing a Geodatabase---ArcGIS Pro Documentation

Delta Tables in Versioned Geodatabases

Conclusion:

The GIS administrator must query the sde_layers table to verify the Adds and Deletes tables before unregistering the dataset as versioned.

Understanding the Scenario:

A database exists but lacks the repository owner required for a geodatabase.

The GIS administrator has database administrator credentials to set up the geodatabase.

Options Overview:

Create Enterprise Geodatabase: This tool creates a geodatabase in a relational database. It sets up the repository owner and adds the required system tables, schema, and configurations.

Enable Geodatabase: This tool enables geodatabase functionality in an existing database that already has the repository owner and structure. Since the repository owner is missing, this tool cannot be used.

Create Workflow Database: This tool is unrelated to creating or enabling geodatabases. It is used for managing workflows in a production environment.

Steps to Use Create Enterprise Geodatabase:

Open the Create Enterprise Geodatabase tool in ArcGIS Pro.

Provide the database connection information, including administrator credentials.

Specify the authorization file for geodatabase licensing.

Run the tool to create the geodatabase.

Reference:

Esri Documentation: Create Enterprise Geodatabase.

Why the Correct Answer is A: The Create Enterprise Geodatabase tool is specifically designed for initializing a geodatabase, including creating the repository owner and required system components. The other options are either not applicable or insufficient for the given scenario.

The issue arises because One-way, parent to child replication is being used. In this type of replication, changes from the parent replica (production server) overwrite the data in the child replica (consultant's server) during synchronization, regardless of edits made in the child replica.

1. One-way Replication Workflow

Parent to Child: Changes are pushed from the parent to the child. The child can make local edits, but these edits are not sent back to the parent, and they can be overwritten when synchronizing.

In this case, the consultant's edits are overwritten because the synchronization is unidirectional from the production server to the consultant's server.

2. Issue with Conflicting Edits

Since One-way, parent to child replication does not support bi-directional synchronization or conflict detection, local changes in the child replica are not preserved if the parent replica pushes updates that conflict with them.

3. Why Not Other Options?

Checkout/check-in:

This replication type allows edits to be made in the checkout replica and reconciled back to the parent during check-in. This ensures that conflicting edits are addressed.

One-way, child to parent:

In this replication, edits flow from the child replica to the parent replica. The issue described does not align with this setup.

Reference from Esri Documentation and Learning Resources:

Geodatabase Replication---ArcGIS Pro Documentation

Understanding One-Way Replication

Conclusion:

The issue occurs because One-way, parent to child replication is being used, where edits made on the child replica are overwritten by updates from the parent replica during synchronization.

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.