In the Adobe Experience Platform architecture, the Adobe Experience Platform Edge Network provides a globally distributed point of presence for low-latency delivery of experiences. Synchronizing the Hub (Real-Time CDP) with the Edge is critical for 'Real-Time' use cases. The primary factor governing this synchronization is Profile qualification as part of an Edge audience.

When an audience is marked for 'Edge' evaluation, the platform ensures that the necessary profile fragments and segment membership statuses are projected to the Edge Network. This allows the Edge to make instant decisions (like personalizing a website banner) without having to query the central Hub, which would introduce latency. If a profile qualifies for an audience that is active on the Edge, that profile's relevant data is synchronized to ensure the Edge has the most current state for decisioning.

Option B, the rate of data change, affects ingestion but doesn't specifically dictate the Edge-Hub synchronization logic. Options C and D (interaction volume and data size) are environmental factors that influence performance but are not the functional 'trigger' for synchronization. The architectural design of AEP prioritizes efficiency by only moving the data to the Edge that is required for active, edge-enabled use cases, making audience qualification the definitive driver of this process.