Which pairing of interface to task is correct?
Select an answer to reveal the explanation.
Short Explanation
You write and run SQL in the query workspace, then review past executions in query history. Don't let the distractors swap these two screens - that's exactly how the exam likes to test it.
Full Explanation
The correct pairing uses the query workspace for authoring and running SQL, and query history for reviewing and troubleshooting past executions. The query workspace is the authoring and execution surface; query history is the retrospective record used to review what ran and diagnose problems. The pairing that puts access control screens for authoring SQL and the query workspace for granting permissions is incorrect because access control screens manage permissions and the workspace does not grant them - the two roles are reversed. The pairing that uses Infrastructure Manager for reviewing executions and Data manager for running SQL is incorrect because Infrastructure Manager handles engines and services while Data manager handles data assets; neither reviews executions or runs ad hoc SQL. The pairing that uses query history for authoring SQL and query workspace for storing execution records is incorrect because it inverts the pair: history is a record, not an editor. For the exam, learn these as a matched pair - workspace forward, history backward - and watch for distractors that simply transpose them.