You must restrict execution of the alter system checkpoint command to certain conditions, specified in a rule set used by a command rule. Which two parameters must be specified In the…

Question

Options

• APARAMETER_NAM?;'CHECKPOINT'
• BOBJECT_OWNER=>'SYS
• CCLAUSE_NAME=>'CHECKPOINT'
• DCLAUSE_NAME=>'SYSTEM'
• ECOMMANI>=>' ALTER SYSTEM'
• FOBJECT_NAME=>'CHECKPOINT'
• GCOMMAND=>'ALTER'

• A
  3% (1)
• B
  6% (2)
• C
  78% (28)
• E
  11% (4)
• G
  3% (1)

Explanation

When creating a command rule to restrict ALTER SYSTEM CHECKPOINT, Oracle Database Vault's DBMS_MACADM.CREATE_COMMAND_RULE requires you to identify both the SQL command and its specific clause as separate parameters. CLAUSE_NAME=>'CHECKPOINT' (C) pinpoints the exact clause being restricted within the ALTER SYSTEM family of commands, while CLAUSE_NAME=>'SYSTEM' (D) - note this question likely contains OCR/transcription errors, and the technically correct pair is C and E (CLAUSE_NAME=>'CHECKPOINT' + COMMAND=>'ALTER SYSTEM'), which together uniquely identify the full ALTER SYSTEM CHECKPOINT statement.

Options A (PARAMETER_NAME) and F (OBJECT_NAME) are wrong because checkpoints involve no named object or parameter in this context - those parameters apply to commands like ALTER TABLE or AUDIT. Option B (OBJECT_OWNER=>'SYS') is irrelevant since system-level commands aren't scoped to an owner. Option G (COMMAND=>'ALTER') is incomplete - the command must be the full 'ALTER SYSTEM', not just 'ALTER'.

Memory tip: Think "C = Clause, E = Exact command" - you always need to specify what command (COMMAND) and which clause of that command (CLAUSE_NAME) to nail down a specific ALTER SYSTEM variant. If you only specify COMMAND, you'd block all ALTER SYSTEM statements, not just CHECKPOINT.

No community discussion yet for this question.