Question 819 of 1,152
Security OperationsmediumMultiple ChoiceObjective-mapped

Rate Limiting — Mitigating Authentication Attacks

This SY0-701 practice question tests your understanding of security operations. 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 security analyst detects a high volume of failed authentication attempts from IP address 203.0.113.1 against a web application. The attempts use different usernames, such as 'admin', 'root', 'test', and several common names. Account lockout policies are configured to lock an account after five failed attempts. Despite this, the analyst sees the attempts continuing over several hours. Which of the following security controls is most likely missing or improperly configured?

Clue words in this question

Noticing these words before you look at the options changes how you read each choice.

  • Clue: "most likely"

    Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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

Configure rate limiting per source IP address

Rate limiting per source IP address is the correct control because it restricts the number of authentication requests from a single IP (203.0.113.1) within a given time window, regardless of the usernames used. Account lockout policies are ineffective here because the attacker is rotating through different usernames (e.g., 'admin', 'root', 'test'), so no single account reaches the five-failed-attempt threshold. By limiting the request rate from the source IP, the analyst can throttle the attacker's brute-force attempts without affecting legitimate users.

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.

  • Increase the account lockout threshold to a lower number

    Why it's wrong here

    This would lock accounts more quickly but does not address the core issue: the attacker uses many different usernames. Locking accounts faster does not prevent the attacker from moving to the next username.

    When this WOULD be correct

    If the question described a brute-force attack using a single username (e.g., 'admin') with many attempts, then lowering the lockout threshold (e.g., from 5 to 3) would lock the account sooner and reduce successful breaches.

  • Implement geofencing to block traffic from the attacker's region

    Why it's wrong here

    Geofencing restricts access based on geographic location, but it does not stop a determined attacker who may use a VPN or proxy. It is not a direct mitigation for brute force attacks across usernames.

    When this WOULD be correct

    A company wants to restrict access to a sensitive internal application to only employees within the country's borders. The correct answer would be geofencing if the question specifies that all legitimate users are in a known geographic region and the threat is from external IPs outside that region.

  • Configure rate limiting per source IP address

    Why this is correct

    Rate limiting on the application or firewall level restricts the number of authentication attempts from a single IP address over a given time period, regardless of the username being tried. This directly counters the attacker's strategy of rotating usernames to bypass account lockout.

    Clue confirmation

    The clue word "most likely" in the question point toward this answer.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Enable detailed failed login attempt logging

    Why it's wrong here

    While logging helps with detection and forensic analysis, it does not prevent the attack from continuing. The analyst already observed the attempts; proactive controls like rate limiting are needed.

Option-by-option analysis

Why each answer is right or wrong

Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SY0-701 exam frequently reuses these exact scenarios with slightly different constraints.

Configure rate limiting per source IP addressCorrect answer

Why this is correct

Rate limiting on the application or firewall level restricts the number of authentication attempts from a single IP address over a given time period, regardless of the username being tried. This directly counters the attacker's strategy of rotating usernames to bypass account lockout.

Increase the account lockout threshold to a lower numberWrong answer — click to see why

Why this is wrong here

The account lockout threshold is already set to lock after five attempts, but the attack uses different usernames, so lockout per user is ineffective. Lowering the threshold further would not stop the attack since each username is tried only a few times.

★ When this WOULD be the correct answer

If the question described a brute-force attack using a single username (e.g., 'admin') with many attempts, then lowering the lockout threshold (e.g., from 5 to 3) would lock the account sooner and reduce successful breaches.

Why candidates choose this

Candidates may think that reducing the lockout threshold always improves security, not realizing that in a distributed username attack, lockout per user does not prevent the overall volume of attempts.

Implement geofencing to block traffic from the attacker's regionWrong answer — click to see why

Why this is wrong here

Geofencing blocks traffic based on geographic location, but the attacker's IP address 203.0.113.1 is a documentation-only address (not assigned to any real region), and the attack could easily be routed through proxies or VPNs in other regions. The core issue is the volume of attempts from a single source, which rate limiting addresses directly.

★ When this WOULD be the correct answer

A company wants to restrict access to a sensitive internal application to only employees within the country's borders. The correct answer would be geofencing if the question specifies that all legitimate users are in a known geographic region and the threat is from external IPs outside that region.

Why candidates choose this

Candidates may think geofencing is a standard defense against external attackers, but they overlook that attackers can spoof locations or use proxies, and that the question's scenario involves a single IP address rather than a regional threat.

Analysis generated from the official SY0-701blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume account lockout policies are sufficient for all brute-force attacks, but they fail to recognize that rotating usernames (a 'password spraying' attack) bypasses per-account lockout, making per-source-IP rate limiting the correct mitigation.

Detailed technical explanation

How to think about this question

Rate limiting is typically implemented at the web application firewall (WAF) or reverse proxy layer (e.g., Nginx, HAProxy, or AWS WAF) using a token bucket or leaky bucket algorithm. For example, a rule might allow 10 requests per minute per source IP; exceeding that triggers a 429 Too Many Requests response or a temporary block. In a real-world scenario, attackers often use distributed botnets to bypass single-IP rate limiting, so combining rate limiting with CAPTCHA or device fingerprinting is recommended for robust protection.

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.

Related practice questions

Related SY0-701 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SY0-701 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 SY0-701 question test?

Security Operations — This question tests Security Operations — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Configure rate limiting per source IP address — Rate limiting per source IP address is the correct control because it restricts the number of authentication requests from a single IP (203.0.113.1) within a given time window, regardless of the usernames used. Account lockout policies are ineffective here because the attacker is rotating through different usernames (e.g., 'admin', 'root', 'test'), so no single account reaches the five-failed-attempt threshold. By limiting the request rate from the source IP, the analyst can throttle the attacker's brute-force attempts without affecting legitimate users.

What should I do if I get this SY0-701 question wrong?

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Are there clue words in this question I should notice?

Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More SY0-701 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

This SY0-701 practice question is part of Courseiva's free CompTIA 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 SY0-701 exam.