Correlating Campaign Requests With Threat-Intel IoCs
Short answer
B Build a custom SIEM query that correlates web server request logs with threat-intelligence IoCs tied to the suspected threat actor.
Question
Key Takeaways
The task is correlation, not collection: only threat-intelligence IoCs join many foreign source IPs into a single campaign, while XFF, GeoIP and WHOIS merely add address or location facts already implied by the scenario.
This CS0-003 question asks how to link distributed web attacks to one coordinated campaign. The correct approach (B) is a custom SIEM query matching request logs against threat-intelligence IoCs associated with the actor, not log enrichment for IP, GeoIP or WHOIS detail.
Common mistake: Choosing A, because X-Forwarded-For reveals the true client IP behind a proxy; but the logs already list many distinct source IPs, and a raw IP alone cannot attribute requests to a coordinated campaign.
Expert Analysis
The qualifier that decides this question The stem does not ask how to find the real client IP, nor how to show where attackers live. It asks which option will "identify the requests connected to this campaign." Every option must be measured against that single verb: linking individual requests to one coordinated effort.
Why A is already satisfied
Option A adds X-Forwarded-For so logs record the originating client IP instead of the proxy or load-balancer address. That is useful when logs show only the proxy IP — but the scenario says the logs already show "many different source IP addresses," so real client IPs are already present. XFF also only reveals an address; it does not tie that address to a coordinated campaign. One comment argues XFF is "the necessary first step," but that first step is depicted as already done by the problem statement.
Why C and D are eliminated by the stem Option D (GeoIP) and option C (full WHOIS on all sources) both return location and registration facts. The question has already handed you the geography — "different countries" — so annotating the same fact adds no campaign linkage. WHOIS enrichment on all sources is also expensive and produces ownership noise, not correlation.
Why B is correct Option B builds a custom SIEM query that joins the web request logs against threat-intelligence IoCs tied to the suspected threat actor. IoCs such as URI patterns, user agents, payloads and known infrastructure are exactly what binds scattered source IPs into one campaign, which is the threat-intelligence/correlation work tested under objective 1.4. As one comment puts it, option A "will identify IPs, but that won't help you attribute those IPs to a specific coordinated campaign" — B is the only choice that performs that attribution.
Official Reference
https://www.comptia.org/certifications/cybersecurity-analyst
This link opens the official vendor documentation in a new tab.
Exam Strategy
Read the stem's requested outcome as a filter and score each option against that exact verb. When a scenario already supplies a fact (here, many foreign source IPs), eliminate options that only restate it, such as GeoIP and WHOIS. Reserve enrichment answers for questions asking to reveal a missing attribute like the true client IP; when the question asks to tie activity to an actor or campaign, reach for the SIEM-plus-threat-intelligence correlation option.
Frequently Asked Questions
Why isn't adding X-Forwarded-For the right answer here?
What does GeoIP or WHOIS enrichment actually give an analyst?
How does a SIEM query with threat-intel IoCs identify campaign traffic?
Community Votes
80% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 5 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 5
-
3be4e12 👍 8 Answered AThe X-Forwarded-For (XFF) HTTP header field is a common method for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer.Without the use of XFF or another similar technique, any connection through the proxy would reveal only the originating IP address of the proxy server, effectively turning the proxy server into an anonymizing service
-
33e8122 👍 5 Answered AAnswer is A. Beware other users deliberately giving the wrong answer
-
1chung 👍 3 Answered ACorrect Answer is A
-
Kakster 👍 2 Answered BWhat exactly is being asked? "identify the requests connected to this campaign" - Sure, A will identify IPs, but that won't help you attribute those IPs to a specific coordinated campaign. B is the best answer for this.
-
tailogdavid1987 👍 1 Answered AAdding the X-Forwarded-For header reveals the true originating client IP for each request, which is the necessary first step to identify and correlate the individual requests that belong to the campaign.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.