The statement 'Checking the Merge Feature Types parameter on a reader feature type is similar to selecting Single Merged Feature Type in Workflow Options when adding a reader' is true or false?

• A. True
• B. False
• C. Not applicable
• D. Not sure

Answer: (A)

The situation tests how FME handles unifying multiple feature types produced by a reader. The Merge Feature Types parameter on a reader feature type directs FME to combine the different feature types from that reader into a single, merged feature type for downstream processing, creating one common attribute schema and filling missing attributes with nulls as needed. Selecting Single Merged Feature Type in Workflow Options when adding a reader does the same thing at workspace setup time: it configures the reader to emit one merged feature type instead of multiple distinct types. Because both settings purposefully produce the same outcome—one merged feature type for the reader’s output—the statement is true. This helps simplify downstream wiring and transformer configuration, though be mindful that merging combines attributes from different types and may introduce null values or require resolving attribute name conflicts.