What capability in watsonx.data allows different types of SQL queries to be automatically directed to the most appropriate engine?
Select an answer to reveal the explanation.
Short Explanation and Infographic
watsonx.data supports query routing policies through resource groups that direct workloads (interactive; batch; ETL) to the appropriate engine (Presto for interactive; Spark for heavy ETL) based on metadata and rules.
Full explanation below image
Full Explanation
watsonx.data supports query routing policies through resource groups that direct workloads (interactive; batch; ETL) to the appropriate engine (Presto for interactive; Spark for heavy ETL) based on metadata and rules. The incorrect options ("Manual copy-paste of SQL statements between Presto and Spark consoles", "Automatic conversion of all queries to MapReduce jobs", "A round-robin scheduler that distributes queries equally across all engines") are distractors that don't fully capture the concept described.