An audit administrator wants to log Client Context variables In the audit trail. Examine this query and the output:

Question

Exhibit

Options

• AAUDIT CONTEXT NAMESPACE hr_Ct:x ATTRIBUTES hr_app_id NAMESPACE USERENV
• BAUDIT CONTEXT NAMESPACE hr_ctx ATTRIBUTES hr_app_id NAMESPACE USERENV
• CCREATE AUDIT POLICY hr_omp_pol ACTIONS UPDATE ON hr.employoes;
• DAUDIT CONTEXT NAMESPACE hr_ctx ATTRIBUTES hr_app_id, current_user, db_name BY hr
• EAUDIT POLICY hr_emp_pol BY hr;
• FCREATE AUDIT POLICY hr_emp_pol ACTIONS SELECT ON hr. employees;
• GAUDIT POLICY hr_emp_pol EXCEPT hr;

• A
  94% (47)
• D
  2% (1)
• E
  2% (1)
• F
  2% (1)

Explanation

Option A uses the correct Oracle Unified Auditing command - AUDIT CONTEXT - which is the only syntax that logs application context namespace variables (like custom hr_ctx attributes) into the audit trail; including NAMESPACE USERENV at the end extends this to also capture Oracle's built-in session context values.

Options C and F are wrong because CREATE AUDIT POLICY ... ACTIONS defines auditing for DML/DDL operations (UPDATE, SELECT), not context variables. Options E and G are wrong because AUDIT POLICY and AUDIT POLICY ... EXCEPT enable or suppress an already-created policy - they do nothing for context logging. Option D is wrong because it incorrectly lists USERENV-specific attributes (current_user, db_name) as if they belong to the hr_ctx namespace, and the BY hr clause narrows scope in a way the question doesn't call for. Option B appears nearly identical to A but contains a subtly different namespace reference - on the real exam, carefully compare namespace names character by character, as these distractors are designed to catch careless reading.

Memory tip: Split the command universe into two buckets - CREATE AUDIT POLICY ... ACTIONS/PRIVILEGES for what users do, and AUDIT CONTEXT NAMESPACE ... ATTRIBUTES for what values are recorded. If the question mentions "context variables" or "application context," the answer must contain the word CONTEXT, not POLICY.

No community discussion yet for this question.