Question 350
Scenario: An invoice file has repeated rows after a connector retried one day's extract. Which configuration or calculation is the most appropriate?
Explanation
Correct Answer
This directly addresses the stated constraint. Deduplication keys must match the grain of the business record. Confirmation: One row remains for every unique invoice business key without losing genuinely distinct line items.
Incorrect Answers
Joining on product descriptions causes unmatched or incorrect relationships after renaming. The specific problem here is that removing duplicates by invoice date alone deletes legitimate sales occurring on the same day.
Assigning a one-side relationship on a mostly null nonunique identifier produces incorrect modeling. The specific problem here is that removing duplicates by invoice date alone deletes legitimate sales occurring on the same day.
A full outer join unintentionally includes CRM-only customers outside the required population. The specific problem here is that removing duplicates by invoice date alone deletes legitimate sales occurring on the same day.