Database Vault is configured and enabled in the database. You create a rule set to enforce security on the hr. employees table. Examine these requirements: 1. Users working In hr department are allowe

Question

Options

• AOne rule set contains two rules OR'ed together.
• BThe rule set parameter audit_options must be set to dbms_macutl.g_ruleset_audtt_fail.
• CThe rule set must be defined as is_static.
• DThe rule set parameter eval_options must be set to dbms_macutl.g_ruleset_eval_all.
• EThe rule set parameter audit_options must be set to dbms_macutl.g_buleset_audit_fail + DBMS

• A
  7% (3)
• B
  20% (8)
• C
  68% (28)
• E
  5% (2)

Explanation

Option C is correct because defining the rule set as is_static tells Oracle Database Vault to evaluate the rule set once per session and cache the result. Since the rules depend on user attributes (department and role) that do not change mid-session, caching is both safe and appropriate here.

Option D is correct because setting eval_options to DBMS_MACUTL.G_RULESET_EVAL_ALL forces every rule in the rule set to be evaluated on every call, rather than stopping early when one rule returns TRUE. This is required to support the "audit every evaluation" requirement - you cannot fully audit what you short-circuit.

Why the distractors are wrong:

• A - Two OR'ed rules in one rule set cannot enforce different permission levels (view-only vs. view/update/delete) for different users; separate command rules or realms are needed per operation type.
• B - G_RULESET_AUDIT_FAIL only audits failed evaluations; auditing every evaluation requires combining both fail and success audit flags.
• E - This option is incomplete (truncated) and similarly only references the failure audit flag, which is insufficient for auditing all evaluations.

Memory tip: Link C → Cache (static = cache per session, safe when user context is fixed) and D → Do All (EVAL_ALL = evaluate every rule, needed when you must audit every single call). If the question mentions "every evaluation," immediately look for EVAL_ALL.

No community discussion yet for this question.