The answer is to use a hunting query in the Microsoft Sentinel hunting blade to proactively search for PowerShell encoded commands. This technique is correct because it leverages Kusto Query Language (KQL) to scan raw event logs for suspicious patterns like base64-encoded strings or unusual PowerShell execution flags, allowing you to hunt for signs of a specific threat actor before an alert is triggered. On the SC-200 exam, this question tests your understanding of the hunting lifecycle versus detection rules—a common trap is confusing proactive hunting with analytic rules, which only fire after an incident occurs. Remember, watchlists are for static indicators, UEBA for behavioral anomalies, and analytic rules for automated alerts, but only the hunting blade lets you write ad-hoc queries to proactively search for encoded commands. Memory tip: think of the hunting blade as your “proactive search engine” for unknown threats, not a reactive alarm system.
SC-200 Perform threat hunting Practice Question
This SC-200 practice question tests your understanding of perform threat hunting. Compare every option against the stated constraints before choosing — the best answer satisfies all requirements, not just the most obvious one. 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.
You are a security analyst using Microsoft Sentinel. You want to proactively search for signs of a specific threat actor known to use PowerShell encoded commands. Which hunting technique is most appropriate?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a hunting query in the Microsoft Sentinel hunting blade to search for PowerShell encoded commands.
Hunting queries in Microsoft Sentinel allow proactive searching for suspicious patterns. Option C is correct because it directly aligns with the need to create a custom KQL query to detect encoded PowerShell commands. Option A is incorrect because a watchlist is used for known indicators, not proactive hunting. Option B is incorrect because analytic rules create alerts after detection, not for proactive hunting. Option D is incorrect because UEBA identifies anomalies, not specific threat actor techniques.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Create an analytics rule to trigger an alert when PowerShell encoded commands are detected.
Why it's wrong here
Analytics rules are reactive, not proactive hunting.
✗
Create a watchlist of known malicious IPs and correlate with PowerShell events.
Why it's wrong here
Watchlists are for static indicators, not proactive hunting.
✗
Enable UEBA to detect anomalous PowerShell usage.
Why it's wrong here
UEBA detects anomalies but is not specific to encoded commands.
✓
Use a hunting query in the Microsoft Sentinel hunting blade to search for PowerShell encoded commands.
Why this is correct
Hunting queries are designed for proactive search and investigation.
Related concept
Static NAT maps one inside address to one outside address.
Common exam traps
Common exam trap: NAT rules depend on direction and matching traffic
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Trap categories for this question
Command / output trap
UEBA detects anomalies but is not specific to encoded commands.
Detailed technical explanation
How to think about this question
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
KKey Concepts to Remember
Static NAT maps one inside address to one outside address.
PAT allows many inside hosts to share one public address using ports.
Inside local and inside global describe the private and translated addresses.
NAT ACLs identify traffic for translation, not always security filtering.
TExam Day Tips
→Identify inside and outside interfaces first.
→Check whether the scenario needs static NAT, dynamic NAT or PAT.
→Do not confuse NAT matching ACLs with normal packet-filtering intent.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this SC-200 question in full detail.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SC-200 NAT questions on configuration and troubleshooting.
Perform threat hunting — This question tests Perform threat hunting — Static NAT maps one inside address to one outside address..
What is the correct answer to this question?
The correct answer is: Use a hunting query in the Microsoft Sentinel hunting blade to search for PowerShell encoded commands. — Hunting queries in Microsoft Sentinel allow proactive searching for suspicious patterns. Option C is correct because it directly aligns with the need to create a custom KQL query to detect encoded PowerShell commands. Option A is incorrect because a watchlist is used for known indicators, not proactive hunting. Option B is incorrect because analytic rules create alerts after detection, not for proactive hunting. Option D is incorrect because UEBA identifies anomalies, not specific threat actor techniques.
What should I do if I get this SC-200 question wrong?
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related SC-200 NAT questions on configuration and troubleshooting.
What is the key concept behind this question?
Static NAT maps one inside address to one outside address.
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 →
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.
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.