Question 910
An engineer tries to query account-level system tables from a workspace without the required UC privileges. Which operational policy best prevents the same failure?
Explanation
Correct Answer
Audit system table grants before new monitoring integrations. This is the most directly relevant preventive control because system table visibility is controlled by authorization rather than workspace membership alone. A concrete acceptance check is: An approved monitoring identity queries the required usage rows and a restricted identity cannot. To reduce recurrence: Audit system table grants before new monitoring integrations.
Incorrect Answers
Ephemeral compute identifiers do not reliably identify the logical pipeline lifecycle. That consideration does not remove the current constraint: system table visibility is controlled by authorization rather than workspace membership alone.
Excessive API calls can exceed service limits and cause monitoring blind spots. In this situation, system table visibility is controlled by authorization rather than workspace membership alone.
Attempt-level telemetry is not the same as successfully delivered business batches. For the observed behavior, system table visibility is controlled by authorization rather than workspace membership alone.