Why should a Connector Call be considered a last resort when obtaining data?

A Connector Call should be regarded as a last resort for obtaining data primarily due to its negative performance implications. When making a connector call, the integration process must interact with external systems or services. This interaction typically involves network latency, which can significantly slow down the overall integration flow. Additionally, if the external system is under heavy load or experiences outages, this can further delay data retrieval and affect the performance of the integration as a whole.

Furthermore, each connector call introduces the potential for bottlenecks in the workflow, especially if multiple calls are made in a single process. This can lead to reduced efficiency and slower response times. Therefore, it's advisable to utilize other methods of data retrieval, such as using local databases or cached data, before resorting to connector calls to ensure a more efficient and faster integration process.

While other options mention aspects such as configuration settings, compatibility with data types, and latency, the focus here lies on the practicality of performance issues, making it vital to minimize the reliance on connector calls whenever possible.