A team wants to replace their brittle collection of hand-run export scripts with a supportable integration into watsonx.data. What should they adopt?
Select an answer to reveal the explanation.
Short Explanation
The fix for fragile hand-run scripts is a supported pipeline, not a better rota. Connectors give you something that runs on its own, reports when it fails, and carries governance with it.
Full Explanation
The correct answer is supported connectors and defined ingestion or federation pipelines, because they produce a repeatable integration that can be scheduled, monitored, alerted on and governed - which is precisely what the ad hoc scripts lack. The shared-folder approach where source owners deposit files on an agreed schedule is incorrect because it just relocates the manual process, with no schema enforcement, no failure signal and no lineage. The rota of engineers who run the existing scripts manually each morning is incorrect because staffing a manual process does not make it reliable; it makes the failure mode a person having a busy morning. The single very large export run once per quarter to reduce operational effort is incorrect because reducing frequency to quarterly makes the data unusable for almost any purpose while leaving the fragility untouched. Exam note: For the exam, the answer to ad hoc integration is a supported, defined pipeline - not a more disciplined manual routine.