Which scenario is not a valid use of a Connector transformer?

• A. Using a Connector to manage the schema of a cloud database.
• B. Downloading a file using a Connector and then reading it with a FeatureReader using the _dataset parameter.
• C. Writing data locally with a FeatureWriter and then uploading it to a web service using a Connector transformer.
• D. Retrieving a list of file URLs using a Connector and then reading them all directly using a FeatureReader.

Answer: (A)

The Connector transformer is for connecting to external systems and moving data in and out, not for altering or defining the structure of a destination like a cloud database. Its role is to fetch, list, or push data through a defined connection, often in combination with readers, writers, or other transformers, rather than to perform schema management.

Using a Connector to manage the schema of a cloud database is not valid because schema creation or modification (defining tables, columns, types, constraints) is a database/schema operation. That kind of work belongs to the destination writer settings or to a SQL-based action (like SQLExecutor) that runs DDL statements, not to the Connector itself. The Connector handles access and data transfer, while schema changes are handled by the toolchains specifically designed to modify the database structure.

The other scenarios fit because they involve data movement or access patterns supported by Connectors: downloading a file and then reading it with a FeatureReader using the _dataset parameter leverages the Connector to retrieve the resource and the reader to access its contents; writing locally and then uploading via a Connector uses the Connector to push data to a web service after local staging; retrieving a list of URLs with a Connector and reading them with a FeatureReader follows the pattern of listing resources and then iterating through them with a reader.