What is a stated benefit of using a database connection in FME?

What is a stated benefit of using a database connection in FME?

• A. You can share a workspace without sharing database permissions
• B. The reader performs slower
• C. Database connections are optional
• D. You cannot upload to FME Server with database perms

Answer: (A)

Using a database connection in FME centralizes how the workspace talks to the database and keeps credentials managed separately from individual users. This lets you share and deploy the same workspace while not requiring others to have direct database access. The runtime uses the credentials stored in the connection (often managed on the server or in a secure store), so collaborators don’t need database permissions to run the workspace. That’s why the stated benefit is that you can share a workspace without sharing database permissions. The other options don’t describe a built-in benefit: performance isn’t guaranteed to be slower because of connections, and saying database connections are optional isn’t a benefit. Also, in practice you can upload to FME Server with appropriate permissions, so the last option isn’t correct.

Using a database connection in FME centralizes how the workspace talks to the database and keeps credentials managed separately from individual users. This lets you share and deploy the same workspace while not requiring others to have direct database access. The runtime uses the credentials stored in the connection (often managed on the server or in a secure store), so collaborators don’t need database permissions to run the workspace. That’s why the stated benefit is that you can share a workspace without sharing database permissions.

The other options don’t describe a built-in benefit: performance isn’t guaranteed to be slower because of connections, and saying database connections are optional isn’t a benefit. Also, in practice you can upload to FME Server with appropriate permissions, so the last option isn’t correct.