Geodatabase replication is designed to synchronize data edits (inserts, updates, and deletes) but not schema changes. When a field is added to the parent replica's source data, the existing replication agreement is unaware of this structural change. The synchronization process continues to operate based on the original schema defined when the replica was created. Therefore, the new field and its values are not sent to the child. The only officially supported method to apply schema changes to replicated data is to remove the existing replica relationship, apply the schema changes to the source data, and then create a new replica. This ensures the new replica is based on the updated schema.

A. Enable Replica Tracking is a prerequisite for creating replicas, not a tool to update an existing replication schema. You cannot synchronize after unregistering a replica.

B. Feature Compare is a data analysis tool used to identify differences between datasets; it does not manage or repair the replication process or schema.

1. Esri ArcGIS Pro Documentation, "Geodatabase replication fundamentals": Under the section "Replication and geodatabase compatibility," the documentation states, "Once data is replicated, you should not make schema changes to the data in the parent or child geodatabase. If you need to make schema changes, you must first unregister the replica." This directly supports the need to unregister the replica before proceeding.

2. Esri ArcGIS Pro Documentation, "Create Replica (Data Management)": The usage notes for this geoprocessing tool imply that the schema is fixed at the time of creation. The tool's purpose is to establish a replica based on the current state and schema of the source data. This supports the need to recreate the replica to capture the new schema.

3. Esri ArcGIS Enterprise Documentation, "Prepare data for replication": This guide details the steps needed before creating a replica, including schema finalization. It states, "Before replicating, it is important to have the geodatabase design finalized. Schema changes made after a replica is created are not sent during synchronization." This confirms that schema changes are not propagated and necessitates the unregister/recreate workflow.

To allow a parent geodatabase in a one-way replication scenario to be fully compressed (to state 0), the replication must be configured to use the archiving option. When this option is enabled for one-way replication, the system sends data changes from the archive tables instead of the versioning delta tables (the A and D tables). This decouples the replication process from the versioning state. As a result, the versioning delta tables can be compressed into the base tables even if child replicas have not acknowledged receipt of all data change messages, fulfilling the specific requirement of the question.

A. Replicate only the base tables: This is not a specific configuration setting. While replicating non-versioned data (which resides in base tables) would allow compression, the requirement to compress implies the source data is versioned. The correct method for versioned data is using the archiving option.

B. Use the Full replica access type: The "Full" replica access type is designed for two-way replication, where edits can be made in both the parent and child geodatabases. The scenario explicitly requires one-way replication to provide read-only copies.

---

1. Esri ArcGIS Pro Documentation, "One-way replication": Under the section "One-way replication with the option to use archiving," the documentation states, "This option allows the data in the parent replica to be versioned and the geodatabase to be compressed, removing redundant rows from the delta tables. The changes sent to the child replica are read from the archive tables instead of the delta tables of the versioned data."

Source: Esri ArcGIS Pro 3.2 Documentation, "One-way replication".

2. Esri ArcGIS Pro Documentation, "Create Replica (Data Management)" Geoprocessing Tool: The documentation for this tool describes the archiving parameter. For the ARCHIVING option, it specifies: "Changes are sent from the archive class on the parent. This option is available for one-way replication only. It allows the parent replica's geodatabase to be compressed to state 0."

Source: Esri ArcGIS Pro 3.2 Documentation, Geoprocessing Tools, "Create Replica (Data Management)".

3. Esri ArcGIS Pro Documentation, "Replication and geodatabase versioning": This page explains the limitations of standard versioned replication on compression: "If you have replicas that have not synchronized, the versioning reconcile and post process cannot be compressed. This is because the replica versions are still present to track the changes that need to be synchronized." This highlights the problem that using the archiving option (Option C) is designed to solve.

Source: Esri ArcGIS Pro 3.2 Documentation, "Replication and geodatabase versioning".

Geodatabase archiving is fundamentally incompatible with data that is registered for traditional versioning with the option to move edits to base. This versioning type is designed to move edits from the delta tables directly into the base table when posted to the default version. This process conflicts with the archiving mechanism, which tracks historical transactions by maintaining a separate history table and referencing specific database states. Because the "move edits to base" option alters the base table in a way that bypasses the state-based tracking required for archiving, the geodatabase explicitly prevents enabling archiving on a feature class configured this way.

A. Versioned without move edits to base: This is the standard traditional versioning registration, which is fully compatible with geodatabase archiving. Archiving could be enabled on a feature class registered in this manner.

C. Branch versioned with editor tracking: For datasets registered with branch versioning, archiving is automatically enabled by default and is a mandatory component. The user would not need to—nor could they—manually enable it.

---

1. Esri ArcGIS Pro Documentation, "Geodatabase archiving": In the section detailing the requirements for enabling archiving, the documentation explicitly states, "You cannot enable archiving on a feature class that is registered as versioned with the option to move edits to base."

Source: ArcGIS Pro Documentation > Data management > Geodatabases > Manage geodatabases > Geodatabase archiving.

2. Esri ArcGIS Pro Documentation, "Register a dataset as versioned": This document describes the different versioning options. In the section "Register as versioned with the option to move edits to base," it lists the limitations of this option, including: "You cannot enable archiving on datasets that are registered as versioned with the option to move edits to base."

Source: ArcGIS Pro Documentation > Data management > Geodatabases > Manage geodatabases > Traditional versioning > Register a dataset as versioned.

3. Esri ArcGIS Enterprise Documentation, "A quick tour of geodatabase archiving": This overview document outlines the prerequisites for using archiving. Under the "How to enable archiving" section, it lists as a requirement: "The dataset cannot be registered as versioned with the option to move edits to base."

Source: ArcGIS Enterprise Documentation > Manage data > Geodatabases and databases > Geodatabase archiving > A quick tour of geodatabase archiving.

To identify the Adds and Deletes tables for a versioned feature class like 'Buildings', the administrator must first find its unique registrationid. The sdetableregistry (or gdbtableregistry) system table is the primary source for this information, containing a record for every table registered with the geodatabase. The registrationid from this table is used to programmatically name the corresponding delta tables (e.g., a and d). By querying sdetableregistry for the 'Buildings' table, the administrator can retrieve the correct ID to reference the specific Adds and Deletes tables and check if they are empty.

A. sdejayers: While sdelayers contains a layerid that corresponds to the registrationid for feature classes, it is a metadata table for spatial properties. The sdetableregistry is the fundamental source for the registration ID for all registered objects, including non-spatial tables.

C. gdbjtems: The gdbitems table stores metadata about items as they appear in the Catalog pane (e.g., names, paths, types). It does not contain the low-level registration information required to identify versioning delta tables.

1. Esri ArcGIS Pro Documentation. "System tables of a geodatabase in Oracle." This document explicitly states, "The TABLEREGISTRY table... contains a record for each business table that is registered with the geodatabase... The registrationid column contains the unique ID for the table registration, and it is used to identify the business table in other system tables." It also clarifies that for the LAYERS table, the layerid "corresponds to the registrationid in the TABLEREGISTRY table," establishing the latter as the primary source.

2. Pennsylvania State University, GEOG 868. "Lesson 4: Versioning." The courseware explains the versioning architecture: "When a feature class... is registered as versioned, two tables, called delta tables, are created. These are the adds (or A) table and the deletes (or D) table... The A and D tables are named using the RegistrationID of the feature class as it is stored in the SDETABLEREGISTRY system table." This directly supports using the table registry to find the delta tables.

The requirement is to track historical changes while ensuring that the standard versioning workflow (reconcile, post, compress) is independent of the data distribution (replication) process.

A one-way replica is designed for this separation. Changes are made and posted to the Default version in the parent geodatabase, and these changes are then sent to the child. The synchronization is a distinct, one-directional process. Enabling the archive option on the data in the Default version before creating the replica ensures that all changes posted to Default are historically tracked. This configuration directly meets both requirements of the question.

A. Create a one-way replica using the archive option on a child version of Default

This is incorrect because archiving tracks changes against the Default version, not child versions. Replicating from a child version is also not the standard workflow for distributing authoritative data.

C. Create a two-way replica using the archive option on Default

This is incorrect because two-way replication allows edits in both geodatabases. The synchronization process inherently involves reconciling changes from two sources, which does not keep it separate from the reconcile/post workflow.

---

1. Esri ArcGIS Pro Documentation, "Replication types": This document distinguishes between one-way and two-way replication. It states, "One-way replicas... allow data changes to be sent from a parent replica to a child replica or from a child replica to a parent replica." and "Two-way replicas allow data changes to be sent between two replicas." The one-way model supports the required separation of workflows.

Source: Esri. (2023). ArcGIS Pro Documentation: Geodata > Manage Geodata > Replication > Replication types.

2. Esri ArcGIS Pro Documentation, "Replication with archiving": This source explicitly describes the recommended workflow. "If you plan to use one-way replication to send data changes from a parent to a child replica and want to archive the data in the parent geodatabase, enable archiving on the data before creating the replica." This directly supports creating a replica from the Default version (the parent) with archiving enabled.

Source: Esri. (2023). ArcGIS Pro Documentation: Geodata > Manage Geodata > Replication > Replication and related geodatabase functionality > Replication with archiving.

3. Esri ArcGIS Pro Documentation, "What is geodatabase archiving?": This document clarifies how archiving works. "Archiving in ArcGIS is the mechanism for capturing, managing, and analyzing data change... When a dataset is enabled for archiving, all changes saved or posted to the Default version are recorded in the corresponding archive class." This confirms that archiving is tied to the Default version.

Source: Esri. (2023). ArcGIS Pro Documentation: Geodata > Manage Geodata > Archiving > What is geodatabase archiving?.

In a traditionally versioned geodatabase, edits are not applied directly to the business (base) table. Instead, they are stored in associated delta tables: the adds (A) table and the deletes (D) table. When a user or application views a version, ArcGIS constructs the representation by combining data from the base table with the changes recorded in the delta tables.

A direct SQL UPDATE command on the base table bypasses this versioning mechanism. It only modifies rows in the base table. Consequently, any features that have been previously edited within a version (and thus have entries in the delta tables) will not reflect the changes made by the direct SQL command, as the information in the delta tables takes precedence. This results in an apparently incomplete update.

A. Nonversioned feature class that is partitioned: Partitioning is a database-level optimization. A standard SQL UPDATE command is handled transparently by the DBMS and would correctly update all specified rows across all partitions.

C. Archiving enabled on the feature class: Archiving creates a history of edits in a separate archive table. A direct SQL update on the base table would successfully modify the data but would bypass the triggers that populate the history, leading to data inconsistency, not an incomplete update of the current feature values.

1. Esri ArcGIS Pro Documentation, "How traditional versioning works": This document explains the architecture of traditional versioning, detailing the role of the business table, adds table (A), and deletes table (D). It states, "When you edit or delete a record in the business table in a version, rows are added to the A and D tables. The original record in the business table is not removed until the database is compressed." This underpins why edits to the base table alone are insufficient.

2. Esri ArcGIS Pro Documentation, "SQL access to geodatabase data": In the section on versioned data, this source explicitly warns against direct modification of the base table. It clarifies that to edit versioned data with SQL, one must edit a versioned view, not the base table, because direct edits to the base table are not reflected in the delta tables and will not be correctly accessed by ArcGIS.

3. Esri ArcGIS Pro Documentation, "Geodatabase archiving": This document describes how archiving works by using database triggers to copy the original state of a modified feature into a history table. A direct SQL update would bypass these triggers, but the update on the business table itself would be complete, which contradicts the scenario in the question.

The SQL query filters records using a WHERE clause on the inspectorname column and then sorts the results with an ORDER BY clause on the inspectiondate column. The most effective way to optimize this query is with a composite (multi-column) index. The order of columns in the index is critical. The index should first list the column used for filtering (inspectorname) and then the column used for sorting (inspectiondate). This structure allows the database engine to efficiently locate the filtered rows and retrieve them in the pre-sorted order directly from the index, thereby avoiding a costly separate sorting operation.

B. facilitytype, inspectiondate: This index is not useful because it does not include the inspectorname column, which is the primary filter in the WHERE clause.

C. facilitytype, inspectorname: This index does not include the inspectiondate column, forcing the database to perform a separate, inefficient sort operation after filtering the data.

1. Esri ArcGIS Pro Documentation, "Attribute indexes": "An attribute index is an alternate path used by the database management system (DBMS) to retrieve a record from a table... You can create a multicolumn index if you frequently specify two or three fields in a query." This establishes the principle of using multi-column indexes for complex queries. The optimal column order is a fundamental database concept applied here.

Source: Esri ArcGIS Pro Documentation, "Attribute indexes in the geodatabase".

2. PostgreSQL 14 Documentation, Chapter 11. Indexes, Section 11.3. Multicolumn Indexes: "A multicolumn B-tree index can be used with query conditions that involve any subset of the index's columns, but the index is most efficient when there are constraints on the leading (leftmost) columns." This supports placing inspectorname first in the index to satisfy the WHERE clause. The documentation further explains that an index can satisfy an ORDER BY clause if the sort order matches the index order.

Source: PostgreSQL 14 Documentation, Chapter 11, Section 11.3.

3. Ramakrishnan, R., & Gehrke, J. (2003). Database Management Systems (3rd ed.). McGraw-Hill. In the chapter on "Query Optimization," the text explains that an index can be used to retrieve tuples satisfying a WHERE condition and also to retrieve them in a specific order for an ORDER BY clause. For this to happen efficiently, the index key must include the attributes from both clauses in the correct sequence (selection attributes first, then ordering attributes).

Source: Chapter 15, "Query Optimization," Section 15.5, "Using Indexing to Speed up Queries." (Specific page numbers vary by edition, but the concept is a core part of this section).

The performance issue is slow map drawing at specific zoomed-out extents, which is a classic server-side rendering bottleneck caused by drawing numerous complex polygons on-the-fly. Caching the map service (creating map tiles) pre-renders the map at these specified scales. When a user requests the map, the server delivers these pre-drawn, static image tiles instead of executing a new drawing process. This dramatically improves display performance. The fact that attribute queries are fast confirms the bottleneck is with rendering the geometry, not with database retrieval, making caching the most appropriate solution.

B. Run the Analyze Datasets tool: This tool updates database statistics to optimize query execution plans. The scenario explicitly states that attribute queries perform quickly, indicating that database query performance is not the bottleneck.

C. Compress the enterprise geodatabase: The compress operation is primarily used to maintain performance in versioned geodatabases by removing unreferenced states and rows. The feature class is explicitly stated as not versioned, making this operation irrelevant.

---

1. Esri, ArcGIS Enterprise Documentation, "Map caching strategies": "If your map is slow to draw, you can improve its performance by caching it. A map cache is a set of prerendered map images (tiles) that are stored on the server... When a user requests a map, the server can return these tiles instead of drawing the map." This directly supports using caching to solve slow drawing performance.

2. Esri, ArcGIS Enterprise Documentation, "When to create a map cache": "A map cache is most appropriate for maps that contain relatively static data and are targeted for a variety of users... Another sign that you should cache your map is if it contains a large amount of data or complex symbology that is slow to draw dynamically." This aligns perfectly with the scenario of complex polygons performing slowly.

3. Esri, ArcGIS Pro Documentation, "Analyze Datasets (Data Management)": "The Analyze Datasets tool is used to update database statistics of business tables, feature classes, and delta tables, along with the statistics of their indexes. Up-to-date statistics help the database's query optimizer choose the most efficient execution plan for a query." This confirms the tool's purpose is to optimize queries, which are not the problem described.

4. Esri, ArcGIS Enterprise Documentation, "The compress operation and geodatabases": "The compress operation is used to maintain performance in a versioned geodatabase... The compress operation removes the unreferenced states and their associated delta table rows..." This reference confirms that compression is a maintenance task for versioned data, which is not the case in the question.

An enterprise geodatabase is the appropriate choice as it meets all the specified requirements. It is stored in a relational database management system (RDBMS) such as SQL Server, Oracle, or PostgreSQL, which is installed on the organization's local servers. This architecture is specifically designed to support multi-user editing via web services (e.g., feature services) and provides the full capabilities of the underlying RDBMS. This includes creating custom database indexes on specific business fields to optimize query performance, which is a key requirement for the organization.

B. File geodatabase: This is not ideal for multi-user editing environments. It lacks the robust transactional and performance-tuning capabilities, such as creating custom database indexes, that an RDBMS-based enterprise geodatabase provides.

C. Hosted relational database: The term "hosted" typically implies that the data is managed by a third party or in a cloud environment (like ArcGIS Online), which contradicts the requirement for data to be stored locally on the organization's servers.

1. Esri, ArcGIS Pro Documentation, "What is an enterprise geodatabase?": "An enterprise geodatabase is a geodatabase in a relational database management system (Oracle, Microsoft SQL Server, PostgreSQL, or IBM Db2). Enterprise geodatabases can be used by many users at once and support versioned editing and replication." This supports the multi-user editing and local RDBMS storage requirements.

2. Esri, ArcGIS Pro Documentation, "Types of geodatabases": This document compares geodatabase types, stating, "Enterprise geodatabases... are primarily used in multiuser or enterprise settings where the geodatabase is centrally located and accessed by many users." This contrasts with file geodatabases, which are recommended for single users or small workgroups.

3. Esri, ArcGIS Pro Documentation, "Attribute indexes": "In an enterprise geodatabase, you can create additional database indexes on fields to improve query performance. You can create an attribute index on a single column or on multiple columns." This directly addresses the requirement to index specific business fields.

4. Esri, ArcGIS Enterprise Documentation, "Data and publishing in ArcGIS Enterprise": In the section "Data sources," it clarifies that to publish from your own on-premises RDBMS, you must register it as a data store. This RDBMS contains the enterprise geodatabase, fulfilling the local storage and web service editing requirements.

An enterprise geodatabase is the only option that meets both requirements. It is specifically designed for a multi-user environment, allowing simultaneous editing from various clients, including web and mobile applications, via feature services. It is built on a commercial relational database management system (RDBMS) such as SQL Server, Oracle, or PostgreSQL. This architecture allows a database administrator (DBA) to perform advanced performance tuning, such as creating and managing database indexes on the feature class business tables to optimize common queries, which directly aligns with the scenario's requirements.

B. File geodatabase: This is a single-user editing model. While multiple users can read the data, only one user can edit at a time, making it unsuitable for concurrent editing by web and mobile apps.

C. Mobile geodatabase: This is based on SQLite and designed for single-user, offline workflows on mobile devices. It is not intended to serve as a central, multi-user database for simultaneous editing.

---

1. Esri, ArcGIS Pro Documentation, "Types of geodatabases." This document explicitly states, "Enterprise geodatabases... are stored in a relational database... can be edited simultaneously by multiple users... [and] are required for some multiuser geodatabase capabilities such as versioning, archiving, and replication." This supports the multi-user editing requirement.

Source: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/types-of-geodatabases.htm

2. Esri, ArcGIS Enterprise Documentation, "What is an enterprise geodatabase?" This source clarifies the role of the underlying RDBMS: "They take full advantage of the underlying DBMS architecture to support... a large number of simultaneous users... [and] a relational database that can be scaled to meet the needs of the organization." This confirms its suitability for DBA management and performance scaling.

Source: https://enterprise.arcgis.com/en/portal/latest/use/what-is-an-enterprise-geodatabase-.htm

3. Esri, ArcGIS Pro Documentation, "Attribute indexes." This page details how indexes are managed across geodatabase types. For enterprise geodatabases, it notes, "When you create an attribute index for a feature class or table in an enterprise geodatabase, a corresponding index is created in the database." This directly links the DBA's task of adding indexes to the enterprise geodatabase structure.

Source: https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/manage/attribute-indexes.htm