You want to execute a query, but do not have the authorization for selection defined in the query for authorization-relevant characteristics. What would occur in this scenario? (2)

Question

Options

• AYou get an error message
• BYou get only the authorized data
• CYou cannot run the query
• DYou will not get a query result

• A
  81% (30)
• B
  14% (5)
• C
  5% (2)

Explanation

When a query contains explicit selections on authorization-relevant characteristics and you lack the required authorization for those selections, the system raises an authorization error (A) - it detects the violation and reports it. Because the error halts execution, no query result is returned (D); these two outcomes are directly linked as cause and effect.

Why the distractors are wrong:

• B would apply in a different scenario: when the query has no specific selection defined for an auth-relevant characteristic, the system silently filters results to only what you're authorized to see. Here, however, the query has an explicit selection you're not permitted for, so an error is thrown rather than partial data being returned.
• C is misleading - you can technically initiate/run the query; you're not blocked at the UI level before execution. The failure occurs during execution, not before it.

Memory tip: Think "defined selection = hard stop." If the query targets data you're not authorized for, the system doesn't quietly trim results - it flags the problem (A) and hands you nothing (D). No auth → no result, with a message telling you why.

No community discussion yet for this question.