Database user SCOTT requires the privilege to select from all tables and you decide to configure this using a global role. You have not yet configured the database with Enterprise User Security. You…

Question

Options

• AAll statements succeed even without Enterprise User Security configuration, but the role is not
• BThe third statement falls because global roles can be granted only by using a central authority.
• CThe second statement falls because granting a global role can be completed only by using a
• DThe first statement falls because the database Is not set up with Enterprise User Security.

• A
  10% (4)
• B
  15% (6)
• C
  3% (1)
• D
  73% (29)

Explanation

Option D is correct because in Oracle Database, creating a role IDENTIFIED GLOBALLY requires Enterprise User Security (EUS) to already be configured on the database. Without EUS - which integrates Oracle DB with a central directory like Oracle Internet Directory (OID) - the very first DDL statement (CREATE ROLE ... IDENTIFIED GLOBALLY) will throw an error, stopping execution before the subsequent GRANT statements are ever reached.

Why the distractors are wrong:

• A is wrong because not all statements succeed - the first statement fails outright without EUS; the role is never created.
• B misidentifies which statement fails; it incorrectly points to the third statement (granting the role to SCOTT) as the failure point.
• C misidentifies the failure at the second statement (granting privileges to the role), but the role doesn't even exist yet since statement 1 already failed.

Memory tip: Use the phrase "Global roles need a global home first." EUS is that "global home" - the infrastructure must exist before Oracle will accept IDENTIFIED GLOBALLY syntax. If EUS isn't set up, Oracle rejects the role creation at step 1, making everything else moot. On the exam, when you see IDENTIFIED GLOBALLY + no EUS, always look for the answer that fails at statement 1.

No community discussion yet for this question.