Question 1,117 of 1,639
Respond to security incidentshardMultiple ChoiceObjective-mapped

Detect Brute Force on Disabled Accounts

This SC-200 practice question tests your understanding of respond to security incidents. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.

Exhibit

Refer to the exhibit.

```kusto
// KQL query in Microsoft Sentinel
let threshold = 10;
let timeframe = 1h;
SigninLogs
| where TimeGenerated > ago(timeframe)
| where ResultType == "50057" // User account disabled
| summarize Count = count() by UserPrincipalName, IPAddress
| where Count > threshold
| join kind=inner (IdentityInfo | project UserPrincipalName, AccountEnabled) on UserPrincipalName
| where AccountEnabled == false
```

The KQL query above is used in a Microsoft Sentinel analytics rule. What is the purpose of this rule?

Exhibit

Refer to the exhibit.

```kusto
// KQL query in Microsoft Sentinel
let threshold = 10;
let timeframe = 1h;
SigninLogs
| where TimeGenerated > ago(timeframe)
| where ResultType == "50057" // User account disabled
| summarize Count = count() by UserPrincipalName, IPAddress
| where Count > threshold
| join kind=inner (IdentityInfo | project UserPrincipalName, AccountEnabled) on UserPrincipalName
| where AccountEnabled == false
```

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

Detect brute force attempts against disabled user accounts.

The KQL query filters for sign-in events where the user account is disabled (e.g., StatusCode = 50057 or UserAccountControl flags indicate disabled) and then groups by source IP and user to count failed attempts over a short window. When the count exceeds a threshold, it signals a brute force attack targeting disabled accounts, which is a common post-exploitation or reconnaissance technique. Option C is correct because the rule specifically detects repeated authentication failures against disabled accounts, not just any sign-in attempt or inactivity.

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.

  • Detect when a disabled user account attempts to sign in.

    Why it's wrong here

    It detects sign-in attempts to disabled accounts, but more specifically, it focuses on high frequency from the same IP, indicating an attack.

  • Identify users who have been disabled due to inactivity.

    Why it's wrong here

    The query does not consider inactivity; it focuses on sign-in attempts.

  • Detect brute force attempts against disabled user accounts.

    Why this is correct

    The threshold on count per IP and the condition on disabled accounts makes this a brute force detection for disabled accounts.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Monitor sign-in attempts from suspicious IP addresses.

    Why it's wrong here

    While it uses IP addresses, the main focus is on disabled accounts.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may choose Option A because they see 'disabled user account' and assume any sign-in attempt is detected, but the rule requires multiple attempts (brute force pattern), not a single event.

Detailed technical explanation

How to think about this question

Under the hood, the KQL query likely uses the `SigninLogs` table and filters on `Status.errorCode == 50057` (user account is disabled) or checks `UserAccountControl` flags via `AADUserRiskEvents`. The aggregation uses `summarize` with `bin` on `TimeGenerated` (e.g., 5-minute windows) and `count() > threshold` to detect brute force. In real-world scenarios, attackers often target disabled accounts to avoid triggering alerts for active users, making this rule critical for detecting lateral movement or credential stuffing.

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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

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 SC-200 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 SC-200 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 SC-200 question test?

Respond to security incidents — This question tests Respond to security incidents — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Detect brute force attempts against disabled user accounts. — The KQL query filters for sign-in events where the user account is disabled (e.g., StatusCode = 50057 or UserAccountControl flags indicate disabled) and then groups by source IP and user to count failed attempts over a short window. When the count exceeds a threshold, it signals a brute force attack targeting disabled accounts, which is a common post-exploitation or reconnaissance technique. Option C is correct because the rule specifically detects repeated authentication failures against disabled accounts, not just any sign-in attempt or inactivity.

What should I do if I get this SC-200 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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More SC-200 practice questions

Last reviewed: Jul 4, 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 SC-200 practice question is part of Courseiva's free Microsoft 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 SC-200 exam.