Quick Answer
The answer is the `lockoutThreshold` attribute. This LDAP attribute directly defines the maximum number of consecutive failed authentication attempts permitted before the account is locked, which is exactly what the policy requires. In an LDAP directory, `lockoutThreshold` works alongside related attributes like `lockoutDuration` to enforce account lockout policies, ensuring brute-force attacks are mitigated by temporarily disabling access after a specified failure count. On the CISSP exam, this concept tests your understanding of identity and access management controls within the Domain 5 (Identity and Access Management) area, often appearing in scenario-based questions where you must distinguish between configuration attributes. A common trap is confusing `lockoutThreshold` with `lockoutDuration`—remember that threshold controls *how many* failures, while duration controls *how long* the lock lasts. A useful memory tip: think of a “threshold” as the number of strikes before you’re out, just like in baseball—three strikes (failed attempts) and the account is locked.
This CISSP practice question tests your understanding of identity and access management. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A system administrator is configuring an LDAP directory for user authentication. The policy requires that account lockout occurs after a specified number of failed attempts. Which attribute should be configured?
failedLoginAttempts
Why wrong: This may be a counter, not the threshold setting.
lockoutThreshold
This attribute defines the number of failed attempts before account lockout.
lockoutDuration
Why wrong: This defines how long the account remains locked.
passwordLockoutTime
Why wrong: This typically defines the duration of lockout, not the threshold.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
lockoutThreshold
The `lockoutThreshold` attribute in an LDAP directory specifies the maximum number of consecutive failed authentication attempts allowed before the account is locked. This directly satisfies the policy requirement to lock the account after a specified number of failed attempts, making it the correct attribute to configure.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
failedLoginAttempts
Why it's wrong here
This may be a counter, not the threshold setting.
lockoutThreshold
Why this is correct
This attribute defines the number of failed attempts before account lockout.
Related concept
Read the scenario before looking for a memorised answer.
lockoutDuration
Why it's wrong here
This defines how long the account remains locked.
passwordLockoutTime
Why it's wrong here
This typically defines the duration of lockout, not the threshold.
Common exam traps
The trap here is that candidates confuse the attribute that sets the failure limit (`lockoutThreshold`) with the attribute that tracks current failures (`failedLoginAttempts`) or the attribute that sets the lockout duration (`lockoutDuration`), leading them to pick a wrong option that describes a related but distinct function.
Detailed technical explanation
In LDAP directories (e.g., OpenLDAP, Microsoft Active Directory), the `lockoutThreshold` is often part of the password policy object (e.g., `pwdLockout` attribute in RFC 2307 or `lockoutThreshold` in AD's `msDS-PasswordSettings`). The directory service increments a counter (like `pwdFailureCount`) on each failed bind attempt and resets it on a successful bind or after a specified duration; only when this counter reaches the threshold does the account lock. Real-world misconfigurations can occur if the threshold is set too low, causing legitimate users to be locked out after a few typos, or too high, allowing brute-force attacks to continue.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A security analyst at a medium-sized enterprise encounters this scenario during an investigation or architecture review. The correct answer reflects best practice for the specific threat or control described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Security exam questions test whether you can match controls to threats in context — not just recall definitions.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Identity and Access Management — study guide chapter
Learn the concepts, then practise the questions
Identity and Access Management practice questions
Targeted practice on this topic area only
All CISSP questions
529 questions across all exam domains
Certified Information Systems Security Professional CISSP study guide
Full concept coverage aligned to exam objectives
CISSP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise CISSP questions linked to Software Development Security.
Practise CISSP questions linked to Security Assessment and Testing.
Practise CISSP questions linked to Identity and Access Management.
Practise CISSP questions linked to Security and Risk Management.
Practise CISSP questions linked to Security Architecture and Engineering.
Practise CISSP questions linked to Communication and Network Security.
Practise CISSP questions linked to Asset Security.
Practise CISSP questions linked to Security Operations.
Practise CISSP questions linked to CISSP fundamentals.
Practise CISSP questions linked to CISSP scenario.
Practise CISSP questions linked to CISSP troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Identity and Access Management — This question tests Identity and Access Management — Read the scenario before looking for a memorised answer..
The correct answer is: lockoutThreshold — The `lockoutThreshold` attribute in an LDAP directory specifies the maximum number of consecutive failed authentication attempts allowed before the account is locked. This directly satisfies the policy requirement to lock the account after a specified number of failed attempts, making it the correct attribute to configure.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Keep practising
Last reviewed: Jun 24, 2026
This CISSP practice question is part of Courseiva's free ISC2 certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CISSP exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.