Why might you use Continue Translation mode for the Rejected Feature Handling parameter?

• A. You want to pick and choose which transformers' <Rejected> ports you care about.
• B. You assume rejections are happening because of bad data and don't want to use those records.
• C. You want to verify all your data is correct.
• D. You want to audit performance.

Answer: (B)

Continue Translation mode keeps the data flow moving even when some features are rejected by a transformer. This is useful when you expect some bad data and don’t want the entire process to stop because of those records. By choosing this mode, you let the good records continue through the pipeline while the rejected ones can be discarded or handled separately, rather than halting the translation to fix every issue upfront. That aligns with assuming rejections come from bad data and you don’t want those records to slow down or block the rest of the workflow.

It’s not about selectively routing rejections from specific transformers, nor is it about auditing performance or forcing verification of all data. Those would involve different approaches or modes.