- A
SigninLogs | where Location.countryOrRegion !in (dynamic(['US','CA']))
Location is a dynamic field containing countryOrRegion. The !in operator with a dynamic array correctly checks for countries not in the allowed list.
- B
SigninLogs | where Country !in ('US','CA')
Why wrong: There is no direct 'Country' column in SigninLogs; the country data is nested under the Location dynamic field.
- C
SigninLogs | where location != 'US' and location != 'CA'
Why wrong: location is a dynamic object, not a simple string. Direct != comparisons will not work correctly.
- D
SigninLogs | where geoLocation !in (dynamic(['US','CA']))
Why wrong: There is no 'geoLocation' column; the correct property is Location.countryOrRegion.
Quick Answer
The correct KQL query pattern is `SigninLogs | where Location.countryOrRegion !in (dynamic(['US','CA']))`. This works because the `SigninLogs` table stores geographic sign-in data within the `Location` dynamic object, where `countryOrRegion` is a nested property that must be accessed using dot notation. The `!in` operator performs a case-sensitive comparison against a list, and wrapping the allowed countries in `dynamic()` ensures KQL treats them as a proper array for matching. On the SC-200 exam, this pattern tests your understanding of how to filter nested dynamic fields in Microsoft Sentinel analytics rules, a common task for SOC analysts monitoring anomalous sign-ins. A frequent trap is using `!=` or `notcontains` instead of `!in`, which fails because those operators don’t handle list comparisons correctly. To remember this, think “dynamic list, dot path, not-in for exclusion” — the `dynamic()` wrapper and the `Location.countryOrRegion` path are the key pieces that make the filter work.
SC-200 Mitigate threats using Microsoft Sentinel Practice Question
This SC-200 practice question tests your understanding of mitigate threats using microsoft sentinel. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. A key principle to apply: signinLogs table stores Microsoft Entra ID sign-in events.. 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 SOC analyst creates a scheduled analytics rule in Microsoft Sentinel to detect anomalous Microsoft Entra ID sign-ins. The rule uses the SigninLogs table and runs every 15 minutes. The analyst wants to alert when a user signs in from a country that is not in the allowed list (['US', 'CA']). Which KQL query pattern should be used in the rule?
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
SigninLogs | where Location.countryOrRegion !in (dynamic(['US','CA']))
Option A is correct because the SigninLogs table stores the sign-in location in the `Location.countryOrRegion` field, which is a nested property of the `Location` dynamic object. The KQL operator `!in` with `dynamic(['US','CA'])` correctly performs a case-sensitive comparison against a list of string values, ensuring that only sign-ins from countries outside the allowed list trigger the alert.
Key principle: SigninLogs table stores Microsoft Entra ID sign-in events.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
SigninLogs | where Location.countryOrRegion !in (dynamic(['US','CA']))
Why this is correct
Location is a dynamic field containing countryOrRegion. The !in operator with a dynamic array correctly checks for countries not in the allowed list.
Related concept
SigninLogs table stores Microsoft Entra ID sign-in events.
- ✗
SigninLogs | where Country !in ('US','CA')
Why it's wrong here
There is no direct 'Country' column in SigninLogs; the country data is nested under the Location dynamic field.
- ✗
SigninLogs | where location != 'US' and location != 'CA'
Why it's wrong here
location is a dynamic object, not a simple string. Direct != comparisons will not work correctly.
- ✗
SigninLogs | where geoLocation !in (dynamic(['US','CA']))
Why it's wrong here
There is no 'geoLocation' column; the correct property is Location.countryOrRegion.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the flat field name `Country` or `location` with the correct nested property `Location.countryOrRegion`, leading them to choose options that reference non-existent or incorrectly named columns.
Detailed technical explanation
How to think about this question
The `Location` column in SigninLogs is of type `dynamic` and contains nested properties such as `countryOrRegion`, `city`, `state`, and `coordinates`. When querying nested properties, you must use dot notation (e.g., `Location.countryOrRegion`). The `!in` operator with a `dynamic` array performs a case-sensitive match; if case-insensitive matching is needed, use `!in~` with a `dynamic` array. This distinction is critical when dealing with country codes that may appear in different cases in logs.
KKey Concepts to Remember
- SigninLogs table stores Microsoft Entra ID sign-in events.
- The 'Location' column in SigninLogs is a dynamic (JSON) object.
- Country information is accessed via 'Location.countryOrRegion'.
- The 'dynamic()' function is used to create a dynamic array for 'in' or '!in' operators.
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
SigninLogs table stores Microsoft Entra ID sign-in events.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
What to study next
Got this wrong? Here's your next step.
Review signinLogs table stores Microsoft Entra ID sign-in events., then practise related SC-200 questions on the same topic to reinforce the concept.
- →
Mitigate threats using Microsoft Sentinel — study guide chapter
Learn the concepts, then practise the questions
- →
Mitigate threats using Microsoft Sentinel practice questions
Targeted practice on this topic area only
- →
All SC-200 questions
1,639 questions across all exam domains
- →
Microsoft Security Operations Analyst SC-200 study guide
Full concept coverage aligned to exam objectives
- →
SC-200 practice test guide
How to use practice tests most effectively before exam day
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.
Manage a security operations environment practice questions
Practise SC-200 questions linked to Manage a security operations environment.
Respond to security incidents practice questions
Practise SC-200 questions linked to Respond to security incidents.
Perform threat hunting practice questions
Practise SC-200 questions linked to Perform threat hunting.
Mitigate threats using Microsoft Defender XDR practice questions
Practise SC-200 questions linked to Mitigate threats using Microsoft Defender XDR.
Mitigate threats using Microsoft Defender for Cloud practice questions
Practise SC-200 questions linked to Mitigate threats using Microsoft Defender for Cloud.
Mitigate threats using Microsoft Sentinel practice questions
Practise SC-200 questions linked to Mitigate threats using Microsoft Sentinel.
SC-200 fundamentals practice questions
Practise SC-200 questions linked to SC-200 fundamentals.
SC-200 scenario practice questions
Practise SC-200 questions linked to SC-200 scenario.
SC-200 troubleshooting practice questions
Practise SC-200 questions linked to SC-200 troubleshooting.
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?
Mitigate threats using Microsoft Sentinel — This question tests Mitigate threats using Microsoft Sentinel — SigninLogs table stores Microsoft Entra ID sign-in events..
What is the correct answer to this question?
The correct answer is: SigninLogs | where Location.countryOrRegion !in (dynamic(['US','CA'])) — Option A is correct because the SigninLogs table stores the sign-in location in the `Location.countryOrRegion` field, which is a nested property of the `Location` dynamic object. The KQL operator `!in` with `dynamic(['US','CA'])` correctly performs a case-sensitive comparison against a list of string values, ensuring that only sign-ins from countries outside the allowed list trigger the alert.
What should I do if I get this SC-200 question wrong?
Review signinLogs table stores Microsoft Entra ID sign-in events., then practise related SC-200 questions on the same topic to reinforce the concept.
What is the key concept behind this question?
SigninLogs table stores Microsoft Entra ID sign-in events.
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 11, 2026
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.
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.