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?.