You upgraded your database from pre-12c to a multitenant container database (CDB) containing pluggable databases (PDBs). Examine the query and its output: Which two tasks must you perform to add…

Question

Options

• AAssign the appropriate operating system groups to SYSBACKUP, SYSDG, SYSKM.
• BGrant SYSBACKUP, SYSDG, and SYSKM privileges to the intended users.
• CRe-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege and the
• DRe-create the password file with SYSBACKUP, SYSDG, and SYSKM privilege, and FORCE
• ERe-createthepasswordfileintheOracleDatabase12cformat. Correct

• A
  7% (2)
• B
  76% (22)
• C
  3% (1)
• E
  14% (4)

Explanation

Granting the privileges (B) automatically adds those users to the password file - in Oracle 12c+, issuing GRANT SYSBACKUP/SYSDG/SYSKM TO <user> is what actually populates the password file entry. However, since you upgraded from a pre-12c database, the existing password file is in the old format and does not support these new privilege types; you must first re-create it using orapwd with FORCE=Y (D) to overwrite the existing file and produce a 12c-compatible format that can hold these entries.

Why the distractors fail:

• A - OS group assignment enables OS-authenticated connections, not password file entries; it is irrelevant here.
• C - Re-creating without FORCE=Y will fail because a password file already exists; Oracle requires the FORCE flag to overwrite it.
• E - Merely re-creating in "12c format" (without specifying FORCE or the new privilege types) is incomplete and does not address the overwrite requirement.

Memory tip: Think of it as a two-step lock replacement - first swap out the old lock (FORCE-recreate the password file so it can hold new key types), then cut new keys for each user (GRANT the privileges). Neither step works without the other.

No community discussion yet for this question.