PR000005 practice question 22 of 25

With respect to field matching in IDQ, which best describes the approach to address matching?

Full set: 140 questions
Answer options
A: No standardization is necessary, map input fields to the match transformation
B: Standardize address fields and use address line, locality, region and postcode fields as input to the match transformation
C: Standardize address fields and use the discrete address component fields, locality, region and postcode fields as input to the match transformation Correct answer
D: Standardize address fields, create a group key field which contains parts of the address fields and only use the group key for address matching
Correct Answer:
C. Standardize address fields and use the discrete address component fields, locality, region and postcode fields as input to the match transformation
Explanation

The best practice for address matching in Informatica Data Quality (IDQ) involves a two-step process. First, the address data is processed through the Address Validator transformation, which parses and standardizes the input into multiple, discrete component fields (e.g., House Number, Street Name, Street Type). Second, these granular, standardized component fields, along with locality, region, and postcode, are used as inputs to the Match transformation. This approach allows for the creation of more precise and robust match rules by applying different algorithms and weights to each individual component, significantly improving the accuracy of the match results. Using discrete fields provides maximum control over the matching logic.

Why Incorrect

A. Raw address data is highly inconsistent. Skipping standardization would lead to a high number of false negatives and poor match quality, making this approach ineffective.
B. This is less precise than option C. Using a single standardized "address line" for matching is less effective than using its discrete components, as it prevents granular rule definition.
D. A group key is used for blocking (creating candidate clusters) to optimize performance, not for the final, detailed comparison. The match logic operates on the detailed fields themselves.

References

1. Informatica 10.5 Data Quality Transformation Guide, "Address Validator Transformation" chapter. This chapter details how the transformation processes address data and outputs it as "discrete address elements." It states, "You can pass the valid, standardized, and enriched address data to downstream transformations for further processing." This supports using the discrete output for subsequent steps like matching.

2. Informatica 10.5 Data Quality Transformation Guide, "Match Transformation" chapter, "Match Strategy" section. This section describes configuring match columns from the transformation's input fields. The examples and descriptions consistently show the use of multiple, discrete fields (like FirstName, LastName, Street, City) to build a match strategy, reinforcing the principle of using granular components for accurate matching.

3. Herzog, T. N., Scheuren, F. J., & Winkler, W. E. (2007). Data Quality and Record Linkage Techniques. Springer. (ISBN: 978-0-387-69502-0). While a general academic text, Chapter 5, "Probabilistic Record Linkage," discusses the principle of using multiple, distinct fields (variables) for comparison, assigning different weights to each based on their discriminating power. This foundational principle supports using discrete address components over a single address line for more accurate matching.

Scroll to Top