The Alfresco Synchronization Service operates by replicating changes from an on-premise Alfresco Content Services (ACS) instance to the cloud. For this to function, two core capabilities are required. First is the Synchronization feature itself, which manages the replication process. Second, the service must be aware of what content has been created, updated, or deleted. This is achieved through an event-driven model where the on-premise repository publishes change events. This mechanism of tracking and recording changes is functionally an Audit capability, providing a trail of events that the Synchronization service consumes to keep the repositories in sync.

A. Synchronization & Multi-tenancy feature.

Multi-tenancy is an architectural feature for hosting separate, isolated organizations on a single instance. It is not a prerequisite for the on-premise system to synchronize with the cloud.

C. Synchronization & Authentication feature.

While authentication is mandatory for establishing a secure connection between the on-premise and cloud systems, the question focuses on the components for the content synchronization logic. The core logic relies on tracking changes (auditing), whereas authentication is a general prerequisite for any remote system communication.

D. Synchronization & Transformation Services feature.

Transformation Services are used to create renditions of content (e.g., PDF previews). They are not a requirement for the fundamental process of synchronizing the original source files between repositories.

1. Alfresco Content Services Documentation, Alfresco Sync Service 3.4, "Sync Service overview": This document describes the architecture, stating, "The repository is configured to send messages to a message queue... when content is created, updated, or deleted. The Sync Service consumes messages from the queue...". This event stream of content changes serves as the audit trail required for synchronization.

2. Alfresco Content Services Documentation, Alfresco Sync Service 3.4, "Configuring Sync Service": The configuration details show properties for connecting to the source and target repositories. While authentication properties (sync.target.auth.) are present and required for the connection, the fundamental logic of synchronization depends on the event messages detailing content changes, which aligns with the concept of an audit trail.

3. Alfresco Content Services Documentation, "Audit Service": The official Audit Service documentation explains its purpose is to "log a complete trail of all the activities that are performed on a record". The Synchronization Service relies on a similar, purpose-built trail of activities specifically for content changes to perform its function. The exam question uses "Audit feature" to refer to this required change-tracking capability.