Examine this query: Why is this account in this status?

Question

Options

• AThe account uses a global authentication.
• BThe user exceeded the value of FAILED_LOGIN _ATTEMPTS and its password has not been
• CThe account has the SYSDBA privilege granted.
• DThe user exceeded the value of PASSWORD_LIFE_TIME and its password has not been reset yet
• EThe ACCOUNTS_ STATUS column is not updated until the user attempts to log in.

• A
  10% (3)
• B
  3% (1)
• C
  81% (25)
• D
  3% (1)
• E
  3% (1)

Explanation

Option C is correct because accounts granted the SYSDBA privilege (such as SYS) are authenticated through the operating system or password file, bypassing Oracle's standard profile-based password management. This means normal profile parameters do not lock or expire a SYSDBA account the same way they do regular accounts, which directly explains why the account appears in an unexpected or special status.

Why the distractors are wrong:

• A – Global (enterprise) authentication is a centralized identity mechanism unrelated to why SYSDBA accounts behave differently under profile management.
• B – Exceeding FAILED_LOGIN_ATTEMPTS causes a LOCKED status, and SYSDBA-privileged accounts are exempt from this restriction anyway.
• D – Exceeding PASSWORD_LIFE_TIME causes an EXPIRED status, but again, SYSDBA accounts bypass profile-enforced password expiry rules.
• E – Oracle does update ACCOUNT_STATUS based on profile conditions independently of login attempts; it's not deferred until the next login in all cases.

Memory tip: Think "SYSDBA = Super DBA = Super rules." Just as a super admin bypasses normal access controls in many systems, Oracle's SYSDBA privilege bypasses standard password profile enforcement - so any profile-based status explanation (B or D) cannot be the root cause for a SYSDBA account's behavior.

No community discussion yet for this question.