An organisation with substantial existing on-premises data infrastructure wants to adopt watsonx.data without decommissioning those systems. Which characteristic of the platform most supports this?
Select an answer to reveal the explanation.
Short Explanation
You don't have to rip out existing systems. Use hybrid deployment and federation to query current sources in place while new data lands in the lakehouse, then migrate on a schedule the business can absorb.
Full Explanation
Hybrid deployment plus federation supports incremental adoption: existing systems keep serving their workloads and are reachable through connectors, while new data lands in the lakehouse. Migration then proceeds workload by workload rather than as one high-risk event.
The claim about importing other platforms' proprietary storage formats directly into its catalog is incorrect because the platform's openness is about open table formats on object storage, not about ingesting other vendors' proprietary internal storage.
The claim that all sources must be migrated first, forcing a clean cutover, is incorrect because a forced migration is the opposite of what the organisation asked for, and big-bang cutovers are the pattern this approach exists to avoid.
The claim that it uses a single engine type to simplify matching existing workloads is incorrect factually because the platform supports multiple engine types, and that variety is a strength when matching diverse existing workloads, not a simplification.
For the exam, tie hybrid and federation together as the mechanism for coexistence with existing infrastructure.