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?
Answer(s): B
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.
A GIS data administrator is unable to upgrade the geodatabase while editors have active sessions and are working on editing workflows.What should the editors do?
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.
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?
Answer(s): 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.
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?
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 toolThis tool modifies fields but cannot execute schema changes while schema locks are active.Option C: Delete the spatial indexDeleting 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 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 replicaHow should the data owner resolve this issue?
Answer(s): C
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.
Post your Comments and Discuss Esri EGMP2201 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the EGMP2201 content, but please register or login to continue.