In a watsonx.data deployment with both Presto and Spark engines; how is access control enforced consistently across both engines?

watsonx.data's access control policies are enforced at the catalog/metastore level; when any engine (Presto or Spark) accesses a table; it must pass through the same policy checks ensuring consistent governance. The incorrect options ("Each engine maintains its own independent access control database", "Only Presto enforces access control; Spark bypasses all policies", "Access is controlled only by the IBM Cloud IAM roles without any engine-level enforcement") are distractors that don't fully capture the concept described.