Which two authorization rights does a Database Vault realm owner have that a realm participant does not have?

Question

Options

• AAdd or remove realm-protected objects to or from the reaim.
• BGrant or revoke privileges on realm-protected objects to or from other users.
• CAdd or remove realm-secured database roles to or from the realm.
• DGrant or revoke system privileges to access objects protected by the realm.
• EAdd or remove participants to or from the realm.
• FAdd or remove owners to or from the realm.
• GGrant or revoke realm-secured database roles.

• A
  13% (7)
• B
  5% (3)
• C
  77% (43)
• E
  2% (1)
• F
  2% (1)
• G
  2% (1)

Explanation

In Oracle Database Vault, a realm owner has a superset of rights compared to a realm participant. The two exclusive owner rights are adding/removing realm-secured database roles (C) and granting/revoking system privileges on realm-protected objects (D) - both are administrative controls that govern who can access the realm at a structural level, which participants are not trusted to modify.

Why the distractors are wrong:

• A and B are actually participant rights - participants can add/remove protected objects and grant/revoke object-level privileges, since these operate within the realm, not over it.
• E and F (managing participants and owners) are plausible-sounding but are realm configuration tasks handled by the DV_OWNER administrative role, not a distinguishing right between owner vs. participant authorization types.
• G (granting/revoking realm-secured roles) is a near-duplicate distractor for C - C describes managing roles within the realm structure, whereas G is a rephrasing designed to confuse.

Memory tip: Think "Owners = Roles + System" - the two things a realm owner controls that participants don't are Realm-secured Roles (C) and System privileges (D). Participants handle objects; owners handle the infrastructure around them.

No community discussion yet for this question.