In FME Flow, which action would typically make Deployment Parameters available for use in workspaces across multiple projects?

• A. Expose them with an attribute exposer
• B. Connect to the Flow instance
• C. Create a new parameter in each workspace
• D. Store them in a local file

Answer: (B)

Deployment parameters in FME Flow are defined at the Flow instance level and become available to any workspace that is connected to that Flow. By connecting a workspace to the Flow instance, you access the centralized deployment settings, allowing the same parameters to be reused across multiple projects without duplicating them in each workspace. This centralization ensures consistency and simplifies management when deploying across different workflows.

Exposing with an attribute exposer would only make parameters available within a single workspace, not across projects. Creating a new parameter in each workspace duplicates effort and breaks reuse. Storing them in a local file confines the parameters to a single project or machine and doesn’t propagate to other projects.