How is pre-configuring parameters for individual output formats done when using the Generic Writer?

• A. In the Generic Writer parameters.
• B. By adding a Reader Resource.
• C. By adding an additional writer to the workspace and setting the parameters there.
• D. By using a ParameterFetcher transformer.

Answer: (C)

The idea being tested is that per-format parameter customization with the Generic Writer is achieved by using separate writer instances for each target format. In FME, the Generic Writer can emit multiple formats, but the format-specific settings live on the individual writer blocks that actually produce that format. To tailor parameters for a particular output format (for example, a specific path, encoding, compression, or layout options), you add another writer to the workspace configured for that format and set its parameters there. This keeps each target format's settings isolated and reliable, rather than trying to mix different per-format options in a single writer’s parameter set.

The other options don’t fit because the Generic Writer’s main parameters aren’t the place to store per-format differences; a Reader Resource is about input, not output configuration; and a ParameterFetcher could drive values but doesn’t by itself create separate per-format parameter contexts within the workspace.