Question 850
An app needs to know which SQL rows changed since a last synchronization token without needing every before-image. Which implementation step most directly addresses this requirement?
Explanation
Correct Answer
Change Tracking provides lightweight changed-key metadata within a configured retention window. Use Change Tracking with stored sync version and full resync fallback. Clients retrieve changed keys and recover cleanly after expired version.
Incorrect Answers
That change leaves the underlying defect unresolved: Validate CHANGE_TRACKING_MIN_VALID_VERSION and perform full resynchronization when the checkpoint is stale.
The proposed implementation creates the wrong boundary because Change Tracking records changed keys/operations within retention, not all intermediate row versions; CDC may fit other needs.
This step would not produce the required behavior: Use version-based enumeration and consistent boundaries, including rollback or resync when a batch fails. This alternative omits a necessary contract or control and leaves the tested failure path open.