Why is using a WHERE clause on the reader typically faster than filtering data with a Tester in an FME workflow?

Why is using a WHERE clause on the reader typically faster than filtering data with a Tester in an FME workflow?

• A. It is not faster.
• B. The Tester is particularly slow when working with PostGIS and geodatabase formats.
• C. With the WHERE clause you filter the data using a published parameter, while the Tester uses a fixed value.
• D. With the WHERE clause you don't read data only to immediately filter it out.

Answer: (D)