AGIS data administrator needs to prepare data for use in offline workflows. Which database operation must the data administrator perform?
Answer(s): C
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 ArchivingArchiving tracks historical edits but is not required for offline workflows.Option B: Add Global IDsWhile 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.
An editor performs a field calculation on 500,000 records of a traditional versioned feature class while connected to a child version of Default. In the meantime, the Default version is updated by another editor. The child version is then reconciled with Default. What will happen to the 500,000 updated records during the reconcile?
Answer(s): A
Scenario Overview:An editor updates 500,000 records in a child version of the Default version using a field calculation. Another editor updates the Default version, and the child version is reconciled with Default.What Happens During Reconciliation?In traditional versioning, edits to feature classes are stored in the Adds and Deletes tables.During reconciliation:Changes in the child version that differ from the Default version are duplicated in the Adds and Deletes tables to track the differences.This allows conflicts to be detected and resolved while preserving all edits. (ArcGIS Documentation: Traditional Versioning Workflow) Alternative Options:Option B: They will be migrated to the Base tableMigration to the base table occurs only when changes are posted and the geodatabase is compressed.Option C: They will be removed from the States repository table The States repository table tracks state transitions and is unaffected during reconciliation. Thus, during reconciliation, the 500,000 records are duplicated in the Adds and Deletes tables to manage and detect conflicts.
A GIS administrator receives reports of slowing performance across the entire geodatabase. Users report that the time for edits to be made and drawing are affected when adding 10.000 records.Traditional versioning is being used.The following processes are completed weekly:- Rebuilding of indexes and statistics- Geodatabase compress- Remove orphaned connectionsWhich action should be taken?
Scenario Overview:Users experience slowing performance across the geodatabase, particularly for edits and drawing when adding 10,000 records.The organization performs weekly maintenance tasks:Rebuilding indexes and statisticsCompressing the geodatabaseRemoving orphaned connectionsWhy Reconcile and Post Versions?Slow performance in traditional versioning often results from excessive unreconciled versions and a bloated state tree.Reconciling and posting versions reduces the number of states, enabling geodatabase compression to fully collapse redundant states and improve performance.(ArcGIS Documentation: Reconcile and Post)Alternative Options:Option A: Change to use Default versionThis bypasses versioning workflows and does not address the root cause of performance degradation.Option B: Update records via PythonUsing Python to update records does not resolve issues caused by unreconciled versions or state tree inefficiencies.Thus, the correct action is to reconcile and post versions, ensuring the geodatabase state tree is optimized and performance is restored.
A GIS administrator needs to make a synchronized copy of a branch versioned dataset. Editing must be performed on both copies.How should the data be replicated?
Answer(s): B
Scenario Overview:The GIS administrator needs to create a synchronized copy of a branch versioned dataset.Both copies must allow editing.Why Geodatabase Replication?Geodatabase replication supports the creation of synchronized copies of datasets while allowing edits in both the parent and child geodatabases.For branch versioned data, replication ensures that edits made in either the parent or child geodatabase can be synchronized using a two-way replica.(ArcGIS Documentation: Geodatabase Replication)Key Features of Geodatabase Replication for This Scenario:Two-way replication enables editing on both sides while synchronizing changes. Supports branch versioning, ensuring versioned workflows remain intact. Maintains schema consistency across both geodatabases.Alternative Options:Option A: Distributed CollaborationCollaboration is suitable for sharing data across ArcGIS Enterprise environments but does not support active synchronization for editing on both sides.Option C: DBMS ReplicationDBMS-level replication handles raw data replication but does not preserve geodatabase-specific functionalities, such as branch versioning.Thus, geodatabase replication is the correct method for synchronizing and editing branch versioned datasets in both geodatabases.
A GIS data administrator needs to store color, model, and size attributes for different kinds of valves. Pick lists should only show permitted combinations of color, model, and size.Which geodatabase capability should be configured?
Scenario Overview:The administrator needs to store attributes for valves (e.g., color, model, and size). Pick lists must display only valid combinations of these attributes.Why Contingent Values?Contingent values allow geodatabases to enforce specific, dependent attribute combinations. For example, if certain sizes are only valid for specific models and colors, contingent values ensure only permitted combinations are displayed in pick lists.(ArcGIS Documentation: Contingent Values)How Contingent Values Work:Attribute domains are defined for individual fields (e.g., color, model, size). Contingent value rules are configured to establish relationships between the fields, restricting invalid combinations.When editing data, pick lists dynamically adjust based on contingent value rules, showing only valid options.Alternative Options:Option A: DomainsAttribute domains enforce constraints on individual fields but cannot define dependencies between fields.Option B: Subtypes with domainsSubtypes group features into categories with distinct domain rules but do not support interdependent attribute combinations.Thus, contingent values are the appropriate geodatabase capability to configure pick lists for valid attribute combinations.
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.