1Z0-116 · Question #85
Which statement can be used to force password complexity in the password file?
The correct answer is D. orapwd file=orapwOBCL forroat=12.2. Option D references format=12.2, which is the Oracle password file format introduced in Oracle 12c Release 2 that enables password complexity verification and profile enforcement for privileged accounts - this is the key feature that makes it correct, even though the option…
Question
Which statement can be used to force password complexity in the password file?
Options
- Aorapwd file=orapwORCL format=12 force-yes
- Borapwd file=orapwORCL force=yes format=legacy
- Corapwd file=orapwOPCL forcaat=12
- Dorapwd file=orapwOBCL forroat=12.2
How the community answered
(43 responses)- A2% (1)
- B2% (1)
- D95% (41)
Explanation
Option D references format=12.2, which is the Oracle password file format introduced in Oracle 12c Release 2 that enables password complexity verification and profile enforcement for privileged accounts - this is the key feature that makes it correct, even though the option contains a typo (forroat instead of format), which is likely a transcription error in the question itself.
Why the distractors are wrong:
- A uses
force-yesinstead of the correctforce=yessyntax, andformat=12does not enforce password complexity the way12.2does. - B specifies
format=legacy, which uses the old password file format and does not support password complexity or profile enforcement. - C uses the invalid parameter
forcaat=12, which is not a recognizedorapwdoption at all.
Memory tip: Think "12.2 = complexity too" - Oracle version 12.2 was the release that extended password security rules (profiles, complexity) into the password file itself, so format=12.2 is the one that brings complexity enforcement along with it.
Note: This question has multiple typos across the options (e.g.,
forroat,forcaat), which is a red flag for a poorly transcribed question. On the real exam, focus on recognizingformat=12.2as the trigger for password complexity inorapwd.
Topics
Community Discussion
No community discussion yet for this question.