Examine these commands and responses: User Karen is an enterprise user. Which two commands are used to allow this login?

Question

Options

• AGRANT CREATE SESSION TO karan;
• BCREATE USER guest IDENTIFIED BY karen;
• CCREATE USER karen IDENTIFIED BY guest;
• DCREATE USER guest IDENTIFIED GLOBALLY as '';
• EGRANT CREATE SESSION TO guest;

• A
  3% (1)
• B
  9% (3)
• D
  74% (25)
• E
  15% (5)

Explanation

Option D (paired with E - the question asks for two commands) correctly sets up enterprise user (directory-authenticated) login in Oracle. CREATE USER guest IDENTIFIED GLOBALLY AS '' creates a shared database schema using global authentication, where the empty string means any enterprise user authenticated via the directory (e.g., Oracle Internet Directory) maps to the guest schema - which is exactly how Karen, as an enterprise user, gets in. Option E (GRANT CREATE SESSION TO guest) is the required second command, because without it the guest schema cannot open a database session regardless of how the user is identified.

Why the distractors fail:

• A fails because Karen has no local schema named karan - granting session there does nothing for her.
• B fails because IDENTIFIED BY karen creates a password-based local user, not a globally-authenticated one, and the names are swapped.
• C fails for the same reason - IDENTIFIED BY guest is local/password auth, not enterprise/global auth.

Memory tip: Spot "enterprise user" in a question and immediately think IDENTIFIED GLOBALLY AS - the word GLOBALLY is the Oracle keyword for directory-based authentication. The empty string '' is the shared-schema shorthand meaning "all enterprise users land here."

No community discussion yet for this question.