Which three are part of an access control list (ACL) when using Real Application Security?

Question

Options

• Aprivileges
• Bschemas
• Cdata realms
• Dcolumn constraints
• Epolicies
• Fdata realm constraints
• Groles

• A
  74% (17)
• C
  4% (1)
• E
  9% (2)
• G
  13% (3)

Explanation

In Oracle Real Application Security (RAS), an ACL is built from privileges (what operations a principal may perform, e.g., SELECT or DML), column constraints (which columns a principal can access or are masked), and data realm constraints (row-level conditions that filter which rows are visible). Together these three elements define the "who can do what, on which rows, and which columns" for a given ACL entry.

The distractors fail because schemas (B) and roles (G) are broader database objects that can be referenced as principals but are not structural components of an ACL itself. Data realms (C) are separate named objects that define row sets-an ACL references them through data realm constraints, not by containing the realm directly. Policies (E) are the higher-level construct that attaches ACLs to application tables; they sit above the ACL, not inside it.

Memory tip: Think of an ACL as answering three questions - What can you do? (privileges), Which rows? (data realm constraints), Which columns? (column constraints) - and everything else (realms, roles, policies, schemas) lives outside the ACL, in the surrounding RAS architecture.

No community discussion yet for this question.