CrowdStrike Certified Falcon Hunter (CCFH-202) — Free Practice Questions
10 free sample questions from a bank of 131, with the correct answers and explanations. No signup required — start practising right now.
1Which of the following is a suspicious process behavior?
PowerShell running an execution policy of RemoteSigned
An Internet browser (eg., Internet Explorer) performing multiple DNS requests
PowerShell launching a PowerShell script
Non-network processes (e.g., notepad.exe) making an outbound network connection
Answer: D
The short version
D — Non-network process reaching outbound is the suspicious behavior. Normal utilities like notepad.exe have no legitimate need to open external sockets, so that pattern signals possible injection, backdoor activity, for triage.
Key concepts in this question
Expected process behavior: every binary has a normal profile of child processes, file access, and network use.
Network-capable versus non-network binaries: browsers and updaters routinely connect outward, while editors should remain local.
Living-off-the-land and injection: adversaries abuse trusted non-network processes by injecting code so traffic blends as legitimate.
Falcon process and network telemetry: ProcessRollup, DnsRequest, and network connection events let hunters correlate which image opened a socket, to which destination,.
Why D is correct
D describes a textbook anomaly because notepad.exe is a local editing utility with no updater, help-retrieval, or cloud feature that justifies outbound connectivity in standard builds. When it connects outward, the likely causes are injection, hollowing, or command-and-control use.
Why the others are wrong
A. RemoteSigned is the standard protective default that still allows local scripts while blocking untrusted remote scripts, so it is expected rather than suspicious.
B. Browsers exist to resolve and fetch remote content, so multiple DNS requests during normal web use are routine and volume alone does not indicate compromise.
C. PowerShell spawning a script process is common in administration, automation, and logon tasks, and requires additional malicious indicators such as obfuscation or suspicious parentage to become suspicious.
CCFH-202 exam tip
Remember the network-need test: if the binary has no business on the wire but appears in network telemetry, treat it as guilty until proven innocent and pivot to parent, command line, and destination.
2Which SPL (Splunk) field name can be used to automatically convert Unix times (Epoch) to UTC readable time within the Falcon Event Search?
utc_time
conv_time
_time
time
Answer: C
The short version
C — Underscore-time is the Splunk auto-time field in Falcon Event Search. Splunk recognizes _time as the primary timestamp and renders epoch as readable UTC for timelines and sorting.
Key concepts in this question
Epoch versus readable time: Falcon records many timestamps as decimals since 1970 that need formatting for review.
Splunk reserved _time field: in Splunk processing language, _time is the canonical event timestamp used for time-range picking, sorting, bucketing, and visualization.
Falcon Event Search on Splunk: the Investigate search layer exposes sensor events through SPL, so standard Splunk time semantics apply to Falcon event timestamps.
Automatic versus manual conversion: some fields convert implicitly when mapped to _time, while other numeric fields require explicit eval functions such as strftime.
Why C is correct
C is correct because _time is the Splunk-reserved timestamp field that the search head automatically interprets and formats as readable UTC in results, timelines, and time-based commands. Other names are non-reserved fields that Splunk will not treat as event time.
Why the others are wrong
A. utc_time sounds plausible but is not a Splunk-reserved time field, so Splunk treats it as an ordinary string or numeric without timeline behavior.
B. conv_time is not a standard Falcon or Splunk timestamp, and using it leaves epoch values unconverted and invisible to time-picker controls.
D. time is a generic word that may appear in raw data but lacks the underscore-prefixed reserved meaning, so it does not drive automatic UTC formatting or sorting.
CCFH-202 exam tip
Memorize underscore-time as the clock: whenever the exam asks for automatic epoch to UTC handling, choose _time, and reserve strftime for manual eval formatting.
3Which of the following would be the correct field name to find the name of an event?
Event_SimpleName
Event_Simple_Name
EVENT_SIMPLE_NAME
event_simpleName
Answer: D
The short version
D — Lowercase event_simpleName with camel-case suffix is the exact Falcon field. only event_simpleName matches stored documents in Event Search.
Key concepts in this question
Falcon event schema: sensor fields have fixed casing and queries must match exactly.
event_simpleName role: this field holds the high-level event type such as ProcessRollup2, DnsRequest, or FileWritten, and is the first filter in almost every hunt.
Case sensitivity in SPL: unlike some SQL dialects, Splunk field names distinguish upper and lower case, so Event_SimpleName and event_simpleName are different fields.
Hunt reliability: using the wrong casing silently returns zero results, which hunters can mistake for no activity.
Why D is correct
D is correct because the Falcon sensor and cloud schema define the field as all-lowercase event plus camel-case simpleName,. Filtering on event_simpleName reliably isolates event types and combines cleanly with additional terms like FileName or DomainName. The other variants change capitalization or insert underscores, which do not exist in the schema and therefore match nothing.
Why the others are wrong
A. Event_SimpleName capitalizes the first letter and splits words with capitals, which does not match the defined Falcon schema and returns no hits.
B. Event_Simple_Name adds an extra underscore and capitalizes the first letter, creating a non-existent field that Splunk cannot resolve.
C. All-caps EVENT_SIMPLE_NAME follows a different convention and will not match Falcon documents, which use lower-plus-camel casing.
CCFH-202 exam tip
Visualize it as lower then camel: event plus simpleName joined without spaces, and reject any answer that capitalizes E or inserts extra underscores.
4Event Search data is recorded with which time zone?
PST
GMT
EST
UTC
Answer: D
The short version
D — UTC is the settled store for Event Search time. Falcon records event time in Coordinated Universal Time so global telemetry stays comparable and correlation does not break across time zones.
Key concepts in this question
UTC normalization: a single global reference clock that lets sensors, cloud and console agree on when an event happened regardless of endpoint locale.
Event Search timestamping: each event carries a normalized time value used for sorting, filtering by time range, and joining with other data sources.
Display versus storage: the console may render times in browser local time for readability, while the stored canonical value remains UTC for consistency.
Cross-region hunting: adversaries move across time zones, so a shared baseline prevents missed joins, duplicated timelines and off-by-hours errors.
Why D is correct
Falcon Event Search records event data in UTC by design, which is the industry norm for security telemetry and log management. Storing one canonical time removes ambiguity from daylight saving changes, endpoint locale differences and analyst location. That is why UTC is the expected answer for how Event Search data is recorded, and vendor material directly confirms this behavior for consistency and accuracy.
Why the others are wrong
A. PST is a regional local zone for part of North America and is never used as the global store for distributed telemetry.
B. GMT tracks closely to UTC in practice, but the platform names and documents the standard as UTC, so GMT is not the accepted label here.
C. EST is another regional local zone and would fragment timelines if used as the recording standard across a worldwide fleet.
CCFH-202 exam tip
Remember UTC as storage and local as display: if a question asks how data is recorded, choose UTC; if it asks how it appears, think browser setting.
5Which of the following Event Search queries would only find the DNS lookups to the domain: www.randomdomain.com?
A — Exact event type plus exact domain narrows to only that host lookup. Pairing event_simpleName equals DnsRequest with DomainName equals the full name isolates only that host lookup.
Key concepts in this question
DnsRequest events: Falcon logs each DNS resolution with process, computer, and queried DomainName.
Fully qualified versus parent domain: www dot randomdomain dot com and randomdomain dot com are distinct query strings, and hunting often needs one without the other to avoid noise.
Field-equals precision: event_simpleName scopes to DNS only, while DomainName with full equality avoids substring matches that would sweep in lookalives or sibling subdomains.
Exclusion by omission: adding ComputerName or bare terms without field names either over-restricts to one host or under-specifies the match and returns unrelated events.
Why A is correct
A is correct because it applies two exact filters that together define the requirement: event type is DNS request and queried name is precisely the target fully qualified domain. That excludes other event types and parent-domain lookups across all hosts.
Why the others are wrong
B. Filtering to the bare parent domain misses the www prefix requirement and adds a localhost restriction, so it answers a different and narrower question.
C. A bare Dns equals token without event scoping or full field syntax is imprecise and will match substrings, unrelated fields, or nothing depending on parsing.
D. Combining a host filter with an unscoped quoted string lacks the required event type and exact DomainName equality, producing either noise or zero results.
CCFH-202 exam tip
For only-this-domain questions, demand both event_simpleName equals DnsRequest and DomainName equals the full shown hostname with no extra host filter.
6How do you rename fields while using transforming commands such as table, chart, and stats?
By renaming the fields with the “rename” command after the transforming command. e.g. “stats count by ComputerName | rename count AS total_count”
You cannot rename fields as it would affect sub-queries and statistical analysis
By using the “renamed” keyword after the field name. e.g. “stats count renamed totalcount by ComputerName”
By specifying the desired name after the field name. e.g. “stats count totalcount by ComputerName”
Answer: A
The short version
A — Pipe rename after the transforming command to relabel fields. In Falcon Event Search you run the aggregation first, then use rename with AS to give the result column a readable name.
Key concepts in this question
Transforming commands: table, chart and stats reshape results into new rows and columns, producing computed fields such as count that need clear labels.
Rename pipeline stage: rename operates on the output schema of the previous command, changing display names without altering underlying events or stored data.
AS syntax: the pattern rename old AS new is the supported Splunk-style form, shown in the example as rename count AS total_count for clarity.
Readability for hunts: well-named aggregates make dashboards, exports and hand-offs easier to interpret during investigations and reporting.
Why A is correct
Option A shows the proper method because transforming commands emit a new field like count that only exists after aggregation completes. Piping that output into rename with AS relabels the column safely, preserving the statistical result while improving presentation. This matches documented Splunk-style behavior in Event Search and is the only choice that uses a real command in the correct position.
Why the others are wrong
B. You cannot rename fields is false because renaming display labels is routine and does not harm sub-queries or statistics when done after aggregation.
C. The keyword renamed is not a valid command form in this context, and inserting it inside the stats clause breaks expected syntax.
D. Placing a bare desired name after the field inside stats is not supported syntax and will not create a reliable alias for the computed column.
CCFH-202 exam tip
Think transform then rename: aggregate first, then pipe to rename with AS whenever a question asks about relabeling stats, chart or table output.
7SPL (Splunk) eval statements can be used to convert Unix times (Epoch) into UTC readable time. Which eval function is correct?
now
typeof
strftime
relative_time
Answer: C
The short version
C — strftime formats epoch into readable UTC in SPL eval. It takes a numeric Unix time plus a format string and returns a human-friendly timestamp for tables, reports, and timelines in Falcon Event Search.
Key concepts in this question
Unix epoch storage: many Falcon timestamp decimals count seconds since 1970, ideal for math but unreadable until formatted for review.
SPL eval functions: eval extends results with computed fields, and its date family converts, extracts, or compares time values during search.
strftime behavior: borrowed from standard time formatting, strftime accepts an epoch value and a pattern and emits year-month-day hour-minute-second text.
Companion functions: now returns current time, relative_time offsets a timestamp, and typeof reports data type, none of which render epoch as calendar text.
Why C is correct
C is correct because strftime is the documented SPL eval function for rendering numeric epoch as formatted UTC, as in eval readable equals strftime with timestamp and pattern. The function is purpose-built for this conversion, while the distractors either supply current time, shift time windows, or inspect types, so only strftime satisfies the question.
Why the others are wrong
A. now returns the current epoch at search execution and is useful for deltas, but it does not format a stored event timestamp into readable text.
B. typeof reports whether a value is number or string for debugging, and performs no date rendering or timezone conversion.
D. relative_time adds or subtracts an interval for window math such as earliest equals relative_time with offset, but it outputs another epoch rather than formatted UTC.
CCFH-202 exam tip
Link strftime to string-format-time: when the exam asks for eval conversion of epoch to readable form, strftime is the answer and _time is the automatic field counterpart.
8Which of the following queries will return the parent processes responsible for launching badprogram.exe?
[search (ParentProcess) where name=badprogram.exe ] | table ParentProcessName _time
event_simpleName=processrollup2 [search event_simpleName=processrollup2 FileName=badprogram.exe | rename ParentProcessId_decimal AS TargetProcessId_decimal | fields aid TargetProcessId_decimal] | stats count by FileName _time
event_simpleName=processrollup2 [search event_simpleName=processrollup2 FileName=badprogram.exe | rename TargetProcessId_decimal AS ParentProcessId_decimal | fields aid TargetProcessId_decimal] | stats count by FileName _time
Answer: B
The short version
B — Subsearch on the child then join back on process linkage reveals the parent. By finding badprogram dot exe executions, renaming ParentProcessId to TargetProcessId, and re-searching ProcessRollup2, the outer query returns the processes that launched it.
Key concepts in this question
ProcessRollup2 linkage: Falcon process events connect parent and child through identifiers such as ParentProcessId_decimal and TargetProcessId_decimal.
Subsearch join pattern: SPL subsearches collect a small set of keys that the outer search uses to filter the larger event set to related records.
Rename for correlation: renaming aligns the child-side parent key with the parent-side process key so the outer search matches the correct generation.
aid scoping and stats: including aid keeps the join on the same host, while stats or table presents parent name and time for triage.
Why B is correct
B is correct because it follows the documented Falcon parent-hunt workflow: inner search isolates ProcessRollup2 records where FileName is badprogram dot exe, renames ParentProcessId_decimal to TargetProcessId_decimal, and passes aid plus that id outward. The outer ProcessRollup2 search then returns only processes whose own id equals that parent id, effectively listing launchers with time context.
Why the others are wrong
A. A bracket search for a literal ParentProcess token without proper event scoping and id correlation does not perform the required process-id join.
C. Referencing a generic ProcessList and piping to search ParentProcessName lacks the decimal-id linkage and subsearch correlation that Falcon requires.
D. Reversing the rename so Target maps to Parent inverts lineage and returns children or unrelated records instead of the launching parent.
CCFH-202 exam tip
Check rename direction first: to find parents, Parent from the child must become Target for the outer search, and aid must travel with it.
9You want to produce a list of all event occurrences along with selected fields such as the full path, time, username etc. Which command would be the appropriate choice?
fields
distinctcount
table
values
Answer: C
The short version
C — Use table to list every occurrence with chosen columns. When you need one row per event showing full path, time, username and similar fields, table builds that readable event list.
Key concepts in this question
Tabular event listing: returning raw occurrences preserved as rows, with only the requested fields projected for triage and timeline review.
Table command role: explicitly selects and orders columns for display and export, ideal for full path, timestamp and user context side by side.
Aggregation versus listing: some commands collapse many events into counts or unique values, while table keeps individual occurrences visible.
Hunt workflow fit: listing occurrences helps validate a hypothesis, scope affected hosts, and pivot into process or host timelines.
Why C is correct
Table is the appropriate choice because the goal is to produce a list of all event occurrences along with selected fields rather than a summary. It preserves each matching event and renders the requested columns in a consistent grid that analysts can sort, export and investigate. Vendor guidance confirms this pattern with examples like TABLE full path, time and username for occurrence review.
Why the others are wrong
A. Fields only includes or excludes fields from results but does not by itself format a clean multi-column occurrence list the way table does.
B. Distinctcount collapses data into a single numeric count of distinct values, which hides the individual occurrences the question asks to list.
D. Values lists unique values for a field but does not create a multi-field row-per-event table with path, time and username together.
CCFH-202 exam tip
Map the verb to the command: list occurrences means table, summarize means stats, filter columns means fields, unique values means values.
10When exporting the results of the following event search, what data is saved in the exported file (assuming Verbose Mode)? event_simpleName=*Written | stats count by ComputerName
The text of the query
The results of the Statistics tab
No data. Results can only be exported when the “table” command is used
All events in the Events tab
Answer: B
The short version
B — Export saves what the Statistics tab shows. With a stats aggregation in Verbose Mode, the exported file contains the aggregated rows such as count by ComputerName, not the raw event list.
Key concepts in this question
Verbose Mode context: the search pipeline runs the full query and populates both Events and Statistics views, with the transform defining the Statistics output.
Stats transformation effect: piping to stats count by ComputerName replaces raw events with a summary table grouped by host and count.
Export scope rule: export captures the result set of the active transformed view that the query produced, which is the Statistics tab here.
Query text versus data: the literal search string is metadata about the hunt, not the dataset saved during export.
Why B is correct
Option B is correct because the query ends in a stats aggregation, so the meaningful result set is the grouped count table shown under Statistics. When exporting from that state in Verbose Mode, Falcon and Splunk-style behavior saves the aggregated rows that answer how many matching writes occurred per host. That is exactly what analysts need for reporting scope without re-running the search.
Why the others are wrong
A. The text of the query is not exported as the dataset because export is meant to preserve result rows rather than the search syntax itself.
C. No data is incorrect because exports work with stats output, and there is no rule limiting export only to searches that use table.
D. All events in the Events tab is wrong because the trailing stats stage supersedes the raw event view as the exportable result for this query.
CCFH-202 exam tip
Look at the last pipe: if the search ends in stats, expect the Statistics tab to be the exportable result in export questions.