Data-Quality-10-Developer-Specialist Data Quality 10: Developer Specialist Exam Questions and Answers

Mappings

Mapplets

Re-usable Transformations

Rules

Reference Tables can be updated from a Value Frequency list in the Developer

All except Un-Managed Reference Tables can be updated through the Reference Table Manager in the Analyst

Reference Tables maintained in the Analyst and Developer tools are stored in separate repositories

Reference Tables can be imported and exported using the Developer Tool

Use a reference table with the firstname as the valid column and the gender in the second column. Then choose to Replace Reference Table Matches with Valid Values when applying the reference table in a strategy in the Standardizer. Use the firstname as input.

Use a reference table with the gender as the valid column and the firstname in next column. Then choose to Replace Reference Table Matches with Valid Values when applying the reference table in a strategy in the Standardizer. Use the firstname as input.

Use a decision and create an If then else rule eg: If fname = ' Jennifer ' then gender: = ' F ' Endif

Use a reference table with the gender as the valid column and the firstname in next column. Then choose to Replace Reference Table Matches with Custom Strings when applying the reference table in a strategy in the Standardizer. Use the firstname as input.

It manages the dictionaries created in the Analyst Tool.

It provides the DIS with information on the location of the address validation data as well as license and other AV configuration settings.

It runs Identity Matching

It makes the Profile repository available to outside reporting applications like Jaspersoft.

No standardization is necessary, map input fields to the match transformation

Standardize address fields and use address line, locality, region and postcode fields as input to the match transformation

Standardize address fields and use the discrete address component fields, locality, region and postcode fields as input to the match transformation

Standardize address fields, create a group key field which contains parts of the address fields and only use the group key for address matching

Once added, the target will display resolution for each folder imported.

A conflict resolution can be selected to apply to all imported objects.

Default is replace, options include rename or reuse.

The import can consist of an XML file and a Zip file containing the reference tables

Double click on the transformation in the transformation palette

Click and drag the transformation onto the mapping

From the Mapping menu, select Add Transformation

Right click and choose Add Transformation on the mapping

0

0.5

1

1.2

Mappings can only be created as a web service through PC integration

DQ has both native web service functionality and allows integration through PC

DQ mappings can only be made accessible through native means

DQ has not web service support

Set parameter for RTM Location/ Path

Set parameter for RTM Name

Ability to parameterise relational and flat-file connections

All of the above

Using the IDQ content installer.

It is imported through Developer.

The file extracted onto the server and it is automatically picked up after restarting the services

It is installed using the importer available in the Content Management service

Data Rules must be run against the entire data set they are defined upon

Once created a Data Rule cannot be changed...it can only be deleted and re-created

A Data Rule created in the Analyst will appear as a mapplet with an Expression Transformation in the Developer

Data Rules can only be run on data in the project in which they were created

Scorecarding

Matching

Grading

Standardization

The same icon is used to indicate a shared and non shared project.

Comments that are added to a profile in the Analyst can be viewed by the Developer in the same profile in the Developer Tool.

Permissions need to be assigned to each Folder within the project so users of shared projects can access all the objects.

Rules that were created In the Analyst Tool will be visible In the Developer but Developer built rules can not be made available in the Analyst.

There is no specific reason. It is simply a step of an ordered best practice approach.

It is good because it is easier to determine if a field is numeric or text.

Values with leading spaces or punctuation will typically sort to the top or bottom making them easier to identify.

None of the above.

Only if the customer thinks it ' s a good idea

Only if the quality of the data is poor

Not always. If the dataset is small enough, grouping is not required

Yes, it ' s always necessary

IDQ field level matching does not utilize grouping

When field level matching is performed, the records within each group will be compared against each other

When field level matching is performed, matching will be performed across multiple groups in a single match transformation.

When field level matching is performed, matching will not be performed across groups, therefore it is imperative grouping is performed on a complete and accurate field(s)

Decision

Standardizer

Comparison

Parser