There are cases like when version store is corrupted or when versioning scheme is different than the default one which might make sync module take wrong content and activate it. E.g. in DAM versioning strategy is on modification, not on activation hence latest version of the content, might not be the one we want to activate, but current one might be better match when activated. Thus it would be beneficial to optionally configure whether to activate latest activated version, current content or use custom to-be-synchroned-content-selection-strategy.