Which transformer would you use to keep only a subset of attributes and discard the rest?

Which transformer would you use to keep only a subset of attributes and discard the rest?

• A. BulkAttributeRenamer
• B. BulkAttributeRemover
• C. AttributeKeeper
• D. AttributeManager

Answer: (C)

Keeping only a subset of attributes is about filtering the data so only the fields you want are passed downstream. The AttributeKeeper transformer is built for this exact purpose: you specify which attributes to retain, and it passes through only those while discarding everything else. That direct focus on membership makes it the best fit when you want a defined subset of attributes. BulkAttributeRemover, by contrast, deletes attributes you list, which isn’t as precise for defining a kept set—you’d need to know exactly what to remove and still end up managing the remaining attributes. AttributeRenamer changes names but doesn’t control which attributes exist in the stream. AttributeManager offers broader attribute handling but is more complex and less direct for simply keeping a subset.

Keeping only a subset of attributes is about filtering the data so only the fields you want are passed downstream. The AttributeKeeper transformer is built for this exact purpose: you specify which attributes to retain, and it passes through only those while discarding everything else. That direct focus on membership makes it the best fit when you want a defined subset of attributes.

BulkAttributeRemover, by contrast, deletes attributes you list, which isn’t as precise for defining a kept set—you’d need to know exactly what to remove and still end up managing the remaining attributes. AttributeRenamer changes names but doesn’t control which attributes exist in the stream. AttributeManager offers broader attribute handling but is more complex and less direct for simply keeping a subset.