Question 660
An engineer tries to query account-level system tables from a workspace without the required UC privileges. Which principle BEST explains why the implementation failed?
Explanation
Correct Answer
System table visibility is controlled by authorization rather than workspace membership alone. This is the most directly relevant technical explanation 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
Successful API request delivery does not imply workload success or new data. For the observed behavior, system table visibility is controlled by authorization rather than workspace membership alone.
Broad personal tokens grant unnecessary control beyond monitoring needs. Here the important technical distinction is that system table visibility is controlled by authorization rather than workspace membership alone.
A success-only filter can hide material operational faults. The reported failure instead depends on this fact: system table visibility is controlled by authorization rather than workspace membership alone.