What is the effect of pointing a reader's data path to $(FME_SHAREDRESOURCE_DATA)?

What is the effect of pointing a reader's data path to $(FME_SHAREDRESOURCE_DATA)?

• A. It uses data from FME Flow regardless of user.
• B. It uses only local data.
• C. It disables web connections.
• D. It cannot be used in Workbench.

Answer: (A)

Pointing the reader to $(FME_SHAREDRESOURCE_DATA) directs FME to load input from the shared resource store on FME Flow rather than from the local workspace or a user-specific location. The variable expands to the actual directory on the Flow server that holds shared data, so the reader accesses data that is common to all users and runs. This ensures consistency and centralized data management across teams. That’s why this is the best answer: it explicitly uses the shared data repository, independent of who runs the workflow. It does not imply using only local data, it doesn’t disable web connections, and it can be used in Workbench since environment variables are supported there. If you needed per-user or local data, you’d point to a local path instead.

Pointing the reader to $(FME_SHAREDRESOURCE_DATA) directs FME to load input from the shared resource store on FME Flow rather than from the local workspace or a user-specific location. The variable expands to the actual directory on the Flow server that holds shared data, so the reader accesses data that is common to all users and runs. This ensures consistency and centralized data management across teams.

That’s why this is the best answer: it explicitly uses the shared data repository, independent of who runs the workflow. It does not imply using only local data, it doesn’t disable web connections, and it can be used in Workbench since environment variables are supported there. If you needed per-user or local data, you’d point to a local path instead.