What is the benefit of using a separate deduplication service in address management?

• A. It stores addresses in a separate database.
• B. It provides faster write performance.
• C. Centralizes matching logic, improves scalability, enables reuse across systems, and simplifies testing.
• D. It eliminates the need for validation.

Answer: (C)

Separating deduplication into its own service centralizes the matching logic, so every system uses the same rules and normalization for identifying duplicates. That consistency means dedup results are uniform across applications, avoiding conflicting outcomes from different parts of the system. Because the dedupe function lives in a dedicated service, it can be scaled independently to handle peak workloads, and multiple systems can reuse the same logic instead of each implementing its own version. Testing becomes simpler as well: you can validate the deduplication rules and edge cases in one place, run automated tests against the service, and mock or stub it in consumer tests to ensure reliable behavior across all consumers. This setup also makes it easy to update rules or add new data sources without touching each consuming system.

Storing addresses in a separate database is about where data is kept, not how dedupe logic is shared. Faster write performance isn’t guaranteed and isn’t the main advantage here. Validation is still necessary for data quality and business rules, and a deduplication service doesn’t eliminate that need.