1Z0-116 · Question #76
Examine this parameter In sqinet.ora: SQLNET.ADTHENTICATION_SEBVICES=(NONE) For which two cases do you need a password file?
The correct answer is C. to authenticate administrative privileged users remotely E. to authenticate nonprivileged database users remotely. Note: The stated correct answer (C, E) appears to contain an error - the standard Oracle answer for this scenario is C and F. Here is the accurate explanation: --- When SQLNET.AUTHENTICATION_SERVICES=(NONE) is set, Oracle disables OS (operating system) authentication, meaning…
Question
Examine this parameter In sqinet.ora:
SQLNET.ADTHENTICATION_SEBVICES=(NONE) For which two cases do you need a password file?
Options
- Ato authenticate externally Identified users locally
- Bto authenticate nonprivllegcd database users locally
- Cto authenticate administrative privileged users remotely
- Dto authenticate externally Identified users remotely
- Eto authenticate nonprivileged database users remotely
- Fto authenticate administrative privileged users locally
How the community answered
(25 responses)- A12% (3)
- B4% (1)
- C60% (15)
- D4% (1)
- F20% (5)
Explanation
Note: The stated correct answer (C, E) appears to contain an error - the standard Oracle answer for this scenario is C and F. Here is the accurate explanation:
When SQLNET.AUTHENTICATION_SERVICES=(NONE) is set, Oracle disables OS (operating system) authentication, meaning all users must authenticate via Oracle's own mechanisms. A password file (orapwd) is Oracle's dedicated store for privileged credentials (SYSDBA/SYSOPER) and is required in two situations: (C) remote privileged users need it because OS authentication cannot cross a network boundary reliably, and (F) local privileged users also need it because the NONE setting explicitly disables the OS-based bequeath authentication they would otherwise use. Options A and D (externally identified users) are irrelevant because NONE disables all external/OS auth entirely - those users simply cannot connect. Options B and E (nonprivileged users) never use a password file at all - they authenticate via the data dictionary (username/password stored in the database itself), which works regardless of this setting. Option E in particular does not require a password file for remote non-privileged users; they simply supply their database password over SQL*Net.
Memory tip: Think of the password file as the "SYSDBA safety net" - it only matters for privileged connections (SYS/SYSDBA), and NONE forces even local privileged users to use it since OS auth is shut off.
If your source lists C and E as correct, treat it with caution - verify against official Oracle documentation, as this appears to be a transcription error. The correct pair is C and F.
Topics
Community Discussion
No community discussion yet for this question.