During data validation, which technique is used specifically to verify that DMS replication has accurately captured changes?

During data validation, which technique is used specifically to verify that DMS replication has accurately captured changes?

• A. Checksum comparison only.
• B. Manual row-by-row audit.
• C. DMS replication validation.
• D. Schema migration testing.

Answer: (C)

The technique being tested is using DMS replication validation to confirm that the changes captured by the replication process are accurately applied to the target. This built-in capability compares data between the source and target after the replication task runs, using mechanisms like checksums and row counts to detect any mismatches and generate a validation report. It’s specifically designed to verify replication fidelity, making it more reliable and scalable than manual row-by-row audits or generic schema-testing approaches. While checksum comparisons can be part of validation, the dedicated replication validation feature is the appropriate method for this purpose.

The technique being tested is using DMS replication validation to confirm that the changes captured by the replication process are accurately applied to the target. This built-in capability compares data between the source and target after the replication task runs, using mechanisms like checksums and row counts to detect any mismatches and generate a validation report. It’s specifically designed to verify replication fidelity, making it more reliable and scalable than manual row-by-row audits or generic schema-testing approaches. While checksum comparisons can be part of validation, the dedicated replication validation feature is the appropriate method for this purpose.