When running deduplication on SnapVault destinations, which three statements are true?

A.
The target SnapVault controller deduplicates inline.

B.
The source SnapVault data is deduplicated inline on the target before it is written to disk.

C.
Deduplication internally synchronizes with the SnapVault schedule on the destination.

D.
The source (primary) system sends duplicated data even if the source data is deduplicated.

E.
Deduplication with SnapVault creates a snapshot, deduplicates, then deletes and recreates the snapshot to
effectively deduplicate savings.

Explanation:
https://library.netapp.com/ecmdocs/ECMP1196986/html/GUID-E5AD37DE-2F44-47DB-90A3-
C8E115FCBFB7.html
SnapVault replicates at the file level not the block level.
Deduplication is always a post-processed activity for Data OnTap, while compression is an inline process.
The deduplication schedule depends on the SnapVault update schedule on the destination system.
A new Snapshot copy replaces the archival Snapshot copy after deduplication finishes running on the
destination system. (The name of this new Snapshot copy is the same as that of the archival copy, but the
Snapshot copy uses a new timestamp, which is the creation time.)
The SnapVault update recognizes the deduplicated blocks as changed blocks. Thus, when deduplication is run
on an existing SnapVault source for the first time, all saved space is transferred to the destination system.