QUESTION: 13

An organization has ArcGIS Enterprise. A new project requires versioned editing with the ability to show which user deleted a feature from the default version.
Which editing workflow should be used?

Branch versioned editing
Traditional versioned editing
Nonversioned editing

Answer(s): A

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.

Reveal Solution Next Question

QUESTION: 14

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?

Disable schema locking on the service
Run the Alter Field geoprocessing tool
Delete the spatial index

Answer(s): 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.

Reveal Solution Next Question

QUESTION: 15

A data owner creates a one-way replica parent-to-child for a single feature class to share data from a production geodatabase to a public-facing geodatabase. - The data owner synchronizes once a week to share updated data - In time, the data owner wants to add a new attribute field/field type and calculates new attribute values
- The data owner synchronizes the replicas, but the new field and values are not present in the child replica
- In the public-facing geodatabase, the data owner adds the same attribute field and field type - The data owner synchronizes the replicas again, and the values are not replicated in the child replica
How should the data owner resolve this issue?

Unregister the replica pair?, run Enable Replica Tracking and Synchronize Change?
Unregister the replica pairs, run Feature Compare and Synchronize Changes
Unregister the replica pairs, recreate the replica, and Synchronize Changes

Answer(s): C

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.

Reveal Solution Next Question

QUESTION: 16

AGIS data administrator needs to prepare data for use in offline workflows.
Which database operation must the data administrator perform?

Enable archiving
Add global IDs
Enable sync

Answer(s): C

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.

Reveal Solution Next Question

Free EGMP2201 Exam Braindumps (page: 4)

QUESTION: 13

Explanation:

QUESTION: 14

Explanation:

QUESTION: 15

Explanation:

QUESTION: 16

Explanation: