Adding a reader as a Resource will cause FME Workbench to read all that dataset's features, impacting performance as much as adding a regular reader. True or False?

Adding a reader as a Resource will cause FME Workbench to read all that dataset's features, impacting performance as much as adding a regular reader. True or False?

• A. True
• B. It will read only a subset of features
• C. False
• D. It will read data in a streaming fashion

Answer: (C)

Adding a reader as a Resource doesn't trigger loading every feature from the dataset in Workbench. When you create a Resource, FME mainly uses it to reference the data source and to obtain its structure (such as feature types and attribute schemas), often by reading a small sample or just metadata. The heavy data I/O happens when you actually run the translation, not while configuring the workspace. So the statement that it reads all features and impacts performance the same as a regular reader is not correct. Streaming behavior is about how data is processed during a run, not about design-time resource creation.

Adding a reader as a Resource doesn't trigger loading every feature from the dataset in Workbench. When you create a Resource, FME mainly uses it to reference the data source and to obtain its structure (such as feature types and attribute schemas), often by reading a small sample or just metadata. The heavy data I/O happens when you actually run the translation, not while configuring the workspace. So the statement that it reads all features and impacts performance the same as a regular reader is not correct. Streaming behavior is about how data is processed during a run, not about design-time resource creation.