1Z0-052 · Question #158
The database instance has the following parameter setting: OS_AUTHENT_PREFIX = OPS$ OS_ROLES = FALSE REMOTE_OS_AUTHENT = FALSE REMOTE_OS_ROLES = FALSE TIMED_OS_STATISTICS = 0 You have a local…
The correct answer is C. The local operating system user SKD will be able to access the database instance without specifying. With OS_AUTHENT_PREFIX set to OPS$, an OS user named SKD maps to the database user OPS$SKD, enabling the OS user to log in without providing a database password.
Question
The database instance has the following parameter setting:
OS_AUTHENT_PREFIX = OPS$ OS_ROLES = FALSE REMOTE_OS_AUTHENT = FALSE REMOTE_OS_ROLES = FALSE TIMED_OS_STATISTICS = 0 You have a local operating system user SKD. You create a database user OPS$SKD, and then assign external authentication. The user OPS$SKD has the CREATE SESSION privilege. What would you achieve by the above process?
Options
- AThe database user OPS$SKD will be able to administer the database.
- BThe authentication detail for the database user OPS$SKD is recorded in the password file.
- CThe local operating system user SKD will be able to access the database instance without specifying
- DThe database user OPS$SKD has to login with the password of the local operating system user SKD
How the community answered
(32 responses)- A9% (3)
- B6% (2)
- C72% (23)
- D13% (4)
Why each option
With OS_AUTHENT_PREFIX set to OPS$, an OS user named SKD maps to the database user OPS$SKD, enabling the OS user to log in without providing a database password.
The ability to administer the database requires SYSDBA or SYSOPER privilege, not just CREATE SESSION, and OS authentication alone does not grant administrative rights.
The Oracle password file stores credentials only for users with SYSDBA or SYSOPER privileges; externally authenticated users are not recorded there.
When OS_AUTHENT_PREFIX = OPS$ and a database user is created with the matching prefix (OPS$SKD) and assigned external authentication, Oracle delegates authentication to the operating system. The local OS user SKD can connect using 'CONNECT /' without specifying a password, because Oracle trusts the OS-level identity and grants access based on the matching username prefix. The CREATE SESSION privilege allows the session to be established once the OS identity is confirmed.
External authentication means Oracle does NOT require the user to supply an Oracle password - the OS handles credential verification, so no password is prompted by Oracle.
Concept tested: Oracle OS authentication with OPS$ prefix
Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/dbseg/configuring-authentication.html
Topics
Community Discussion
No community discussion yet for this question.