- A
Set session timeout to 15 minutes
Why wrong: Session timeout ends idle sessions, not brute force attempts.
- B
Implement account lockout policy
Account lockout disables the account after a set number of failed attempts.
- C
Enforce complex password policy
Why wrong: Complex passwords slow brute force but do not stop repeated attempts.
- D
Require multi-factor authentication
Why wrong: MFA adds an extra factor but does not prevent the brute force itself.
Quick Answer
The answer is implementing an account lockout policy. This control automatically mitigates repeated failed logins by disabling the account after a predefined number of incorrect attempts within a short time window, directly countering brute-force attacks from a single IP address. The policy works by incrementing a failed-attempt counter; once the threshold is reached—typically 3 to 5 failures—the account is locked for a set duration or until an administrator intervenes, stopping further authentication attempts without manual action. On the Systems Security Certified Practitioner SSCP exam, this question tests your understanding of preventive access controls versus detective or corrective measures, and a common trap is confusing account lockout with password complexity or session timeout policies. Remember the memory tip: “Lock it after three, brute force can’t be free”—the lockout threshold is the key to stopping automated guessing.
SSCP Risk Identification, Monitoring and Analysis Practice Question
This SSCP practice question tests your understanding of risk identification, monitoring and analysis. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 security analyst notices repeated failed login attempts from a single IP address within a short time window. Which control should be implemented to automatically mitigate this behavior?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Implement account lockout policy
An account lockout policy automatically disables an account after a specified number of failed login attempts within a defined time window, directly mitigating brute-force attacks from a single IP. This control is specifically designed to prevent repeated authentication failures by temporarily or permanently locking the account, stopping further attempts without manual intervention.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Set session timeout to 15 minutes
Why it's wrong here
Session timeout ends idle sessions, not brute force attempts.
- ✓
Implement account lockout policy
Why this is correct
Account lockout disables the account after a set number of failed attempts.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Enforce complex password policy
Why it's wrong here
Complex passwords slow brute force but do not stop repeated attempts.
- ✗
Require multi-factor authentication
Why it's wrong here
MFA adds an extra factor but does not prevent the brute force itself.
Common exam traps
Common exam trap: answer the scenario, not the keyword
ISC2 often tests the distinction between preventive controls (like complex passwords or MFA) and corrective/detective controls (like account lockout), leading candidates to choose MFA because it seems stronger, but the question specifically asks for automatic mitigation of repeated failed attempts, which only lockout directly addresses.
Detailed technical explanation
How to think about this question
Account lockout policies are typically configured in Active Directory or local security policies using Group Policy, with settings like 'Account lockout threshold' (e.g., 5 attempts), 'Account lockout duration' (e.g., 30 minutes), and 'Reset account lockout counter after' (e.g., 30 minutes). Under the hood, the domain controller tracks bad password counts per Security Identifier (SID) and increments a badPwdCount attribute; once the threshold is reached, the account's lockoutTime attribute is set, preventing further logins until the duration expires or an administrator unlocks it. In a real-world scenario, a misconfigured lockout policy (e.g., too low a threshold) can lead to denial-of-service if attackers intentionally trigger lockouts on legitimate accounts.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
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
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Risk Identification, Monitoring and Analysis — study guide chapter
Learn the concepts, then practise the questions
- →
Risk Identification, Monitoring and Analysis practice questions
Targeted practice on this topic area only
- →
All SSCP questions
504 questions across all exam domains
- →
Systems Security Certified Practitioner SSCP study guide
Full concept coverage aligned to exam objectives
- →
SSCP practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SSCP practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Risk Identification, Monitoring and Analysis practice questions
Practise SSCP questions linked to Risk Identification, Monitoring and Analysis.
Network and Communications Security practice questions
Practise SSCP questions linked to Network and Communications Security.
Systems and Application Security practice questions
Practise SSCP questions linked to Systems and Application Security.
Security Operations and Administration practice questions
Practise SSCP questions linked to Security Operations and Administration.
Incident Response and Recovery practice questions
Practise SSCP questions linked to Incident Response and Recovery.
Access Controls practice questions
Practise SSCP questions linked to Access Controls.
Cryptography practice questions
Practise SSCP questions linked to Cryptography.
SSCP fundamentals practice questions
Practise SSCP questions linked to SSCP fundamentals.
SSCP scenario practice questions
Practise SSCP questions linked to SSCP scenario.
SSCP troubleshooting practice questions
Practise SSCP questions linked to SSCP troubleshooting.
Practice this exam
Start a free SSCP practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SSCP question test?
Risk Identification, Monitoring and Analysis — This question tests Risk Identification, Monitoring and Analysis — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Implement account lockout policy — An account lockout policy automatically disables an account after a specified number of failed login attempts within a defined time window, directly mitigating brute-force attacks from a single IP. This control is specifically designed to prevent repeated authentication failures by temporarily or permanently locking the account, stopping further attempts without manual intervention.
What should I do if I get this SSCP question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
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 →
Last reviewed: Jun 30, 2026
This SSCP 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 SSCP 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.