When a user switches from one engine to another to run the same query, what happens to the governance controls on the data?
Select an answer to reveal the explanation.
Short Explanation
Changing engines is not a way around policy. The controls live with the data, and every engine resolves through them - which is what makes multiple engines safe in the first place.
Full Explanation
The correct choice says governance controls continue to apply because policy is enforced on the governed data against the user's identity regardless of which engine executes the query. Governance is a property of the data and identity, not compute. Whichever engine executes the statement, the policy decision is the same, which makes multi-engine access safe.
Reapplying controls only after an administrator re-registers tables for the new engine is wrong because no per-engine re-registration step exists; tables are registered once in the catalog.
Controls lapsing until the user's session is refreshed on the new engine is wrong because there is no window during which controls lapse; that would be an exploitable gap.
Controls applying only if both engines are of the same type is wrong because engine type has no bearing on policy evaluation; heterogeneous engines are a normal design.
For the exam, treat any suggestion that changing engines bypasses governance as automatically wrong.