Question 260
An unresolved malware investigation crosses from the Asia-Pacific shift to the European SOC team. Which additional finding would most directly support the suspected security interpretation?
- Alerts span infrastructure telemetry and enterprise identity activity
- A correlated successful session following repeated rejected credentials
- An alert requires privileged containment outside the provider's delegated remit
- The departing shift owns open containment decisions with no incoming acknowledgement
Explanation
Correct Answer
D:A change in personnel can strand urgent steps even when alerts remain visible. The follow-up evidence is the current case timeline, pending actions, and shift-transfer acknowledgement, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
A:No single team has the full evidence needed to decide whether a cloud workload is compromised; that is suited to investigating hybrid SOC coordination, whereas the follow-the-sun transfer case requires the departing shift owns open containment decisions with no incoming acknowledgement for recognizing the distinguishing signal.
B:The success after failures changes the event from a noisy authentication anomaly to a potential compromise; prioritizing that triage versus investigation mechanism would leave this follow-the-sun transfer decision unresolved because the departing shift owns open containment decisions with no incoming acknowledgement is the direct fit.
C:The managed service may detect and recommend, but authorization remains with the customer; applied to this follow-the-sun transfer case, it addresses managed SOC boundary instead of the required step: the departing shift owns open containment decisions with no incoming acknowledgement.
Question 261
One developer legitimately executes large compilation jobs nightly, triggering process-volume anomaly alerts. Supporting evidence includes: Per-role historical execution rates, signed binaries and change records. Which next step most directly reduces the described risk?
- Tune deviation thresholds against the developer's established normal behavior
- Map the detection to the supported ATT&CK technique and note telemetry prerequisites
- Translate the rule and test it against native SIEM events
- Restrict time windows, use indexed fields and schedule appropriately
Explanation
Correct Answer
A:Permanent broad exclusions would hide malicious shifts in the same role. For safe case progression, preserve the evidence and later verify approved nightly jobs remain distinguishable from new high-risk process trees.
Incorrect Answers
B:This relates to MITRE ATTACK mapping: adding many ATT&CK tags without evidence inflates coverage metrics; the behavioral baselines question instead requires choosing the immediate operational response, specifically tune deviation thresholds against the developer's established normal behavior.
C:Copying a query without checking source schemas can produce silent misses; prioritizing that sigma rule portability mechanism would leave this behavioral baselines decision unresolved because tune deviation thresholds against the developer's established normal behavior is the direct fit.
D:Reducing sensitivity by deleting events is not an acceptable first optimization; that is suited to investigating analytic query cost, whereas the behavioral baselines case requires tune deviation thresholds against the developer's established normal behavior for choosing the immediate operational response.
Question 262
During an investigation of GCP Security Command Center, the SOC validates this finding: Misconfigurations and threat signals require centralized cloud findings. What should the response owner do next?
- Stream relevant Activity Log events to monitored storage or workspace
- Enable appropriate SCC services and route high-risk findings into SOC workflow
- Ingest and map relevant logs then test behavioral detections in Google SecOps
- Correct least-privilege access and monitor use of service identities
Explanation
Correct Answer
B:A generic log sink alone does not organize posture findings. For safe case progression, preserve the evidence and later verify a controlled misconfiguration yields a traceable finding with resource ownership.
Incorrect Answers
A:Collecting only VM Security events misses resource-management changes; applied to this GCP Security Command Center case, it addresses Azure activity log visibility instead of the required step: enable appropriate SCC services and route high-risk findings into SOC workflow.
C:A standalone SCC finding does not replace cross-source SIEM analytics; prioritizing that Google SecOps investigation mechanism would leave this GCP Security Command Center decision unresolved because enable appropriate SCC services and route high-risk findings into SOC workflow is the direct fit.
D:Demanding host hypervisor logs from the provider would not fix tenant grants; applied to this GCP Security Command Center case, it addresses cloud shared responsibility instead of the required step: enable appropriate SCC services and route high-risk findings into SOC workflow.
Question 263
The working hypothesis concerns MITRE ATTACK hunt map. The initial finding is: Technique-oriented mapping captures behavior independent of product label. Which evidence should investigators prioritize?
- Known attack behavior and mapped defensive technique prerequisites
- Linked infrastructure registration, payload characteristics and victim timeline
- Observed process behavior aligned with appropriate ATT&CK techniques
- Actual schema, sample events and independent query execution results
Explanation
Correct Answer
C:The mapping must be evidence based and not overclaim campaign attribution. Linking these records back to technique-oriented mapping captures behavior independent of product label reduces reliance on an isolated indicator.
Incorrect Answers
A:For MITRE D3FEND application, the mapping should lead to a deployable defense, not only a label; here the narrower objective is independently corroborating the suspected behavior in MITRE ATTACK hunt map, best addressed by observed process behavior aligned with appropriate ATT&CK techniques.
B:Cross-relating these features can surface additional intrusion events; this evidence or action is associated with diamond model pivot, whereas the case concerns MITRE ATTACK hunt map and calls for observed process behavior aligned with appropriate ATT&CK techniques.
D:Reproducible data checks are necessary before trusting suggested detections, which would be relevant to AI-assisted hunting, but not the MITRE ATTACK hunt map scenario that requires observed process behavior aligned with appropriate ATT&CK techniques.
Question 264
An analyst plans to close a confirmed intrusion because the original malicious process exited. Which finding best distinguishes this activity from a routine operational change?
- The initial symptom is gone but scoping and remediation proof are missing
- The ticket omits observed artifacts, scope and business impact
- Alert count falls at the same time source-ingestion volume disappears
- Unnormalized timestamps scramble the apparent sequence of attacker actions
- A time-bounded suppression has no scheduled expiration or owner review
Explanation
Correct Answer
A:Process termination may occur while persistence and stolen access survive. The follow-up evidence is host isolation, persistence checks, impacted credentials and responder sign-off, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
B:The alternative concerns ticket escalation evidence: a receiving responder cannot reproduce the conclusion from a vague label; however, the described case closure standard situation calls for the initial symptom is gone but scoping and remediation proof are missing.
C:For analyst dashboard fidelity, volume reduction can reflect a blind spot rather than improved risk; here the narrower objective is recognizing the distinguishing signal in case closure standard, best addressed by the initial symptom is gone but scoping and remediation proof are missing.
D:The investigative narrative relies on trustworthy event ordering; applied to this case closure standard case, it addresses case evidence timeline instead of the required step: the initial symptom is gone but scoping and remediation proof are missing.
E:Permanent exceptions can silently preserve attack blind spots; that is suited to investigating rule suppression expiry, whereas the case closure standard case requires the initial symptom is gone but scoping and remediation proof are missing for recognizing the distinguishing signal.
Question 265
The first-line team is investigating mean time to detect. Its preliminary finding is: Intrusion start to first credible detection is the dominant delay. What corroborating material is most decisive?
- Alert creation, approval, and endpoint isolation timestamps
- Intrusion timeline and timestamp of earliest defensible alert
- Historical event samples, predicted alert volume, and test results
- Identity-provider sign-in details joined to endpoint activity
Explanation
Correct Answer
B:The gap can be measured only if onset and detection evidence are both established. Linking these records back to intrusion start to first credible detection is the dominant delay reduces reliance on an isolated indicator.
Incorrect Answers
A:The operational timeline identifies which response stage generated the delay; this evidence or action is associated with mean time to respond, whereas the case concerns mean time to detect and calls for intrusion timeline and timestamp of earliest defensible alert.
C:For rule-change governance, backtesting reveals false positives and source coverage before production activation; here the narrower objective is independently corroborating the suspected behavior in mean time to detect, best addressed by intrusion timeline and timestamp of earliest defensible alert.
D:Correlating user, device, and subsequent behavior is stronger than treating failure counts alone as an incident, which would be relevant to triage versus investigation, but not the mean time to detect scenario that requires intrusion timeline and timestamp of earliest defensible alert.
Question 266
The working evidence for analyst dashboard fidelity includes this observation: Alert count falls at the same time source-ingestion volume disappears. Which intervention is the best fit for the established finding?
- Keep the incident open until remediation, validation and ownership are recorded
- Add telemetry-health panels beside threat-alert metrics
- Automate audit onboarding and open coverage gaps as operational incidents
- Build a unified timeline and note uncertain source clocks explicitly
Explanation
Correct Answer
B:A dashboard focused only on detections can mislead leadership. Operational success is not assumed until canary events and ingestion statistics remain complete during quiet periods, the relevant outcome for this response.
Incorrect Answers
A:Reducing ticket backlog is not a substitute for security restoration; prioritizing that case closure standard mechanism would leave this analyst dashboard fidelity decision unresolved because add telemetry-health panels beside threat-alert metrics is the direct fit.
C:Manual dashboards do not provide consistent future account visibility, which would be relevant to cloud logging gap, but not the analyst dashboard fidelity scenario that requires add telemetry-health panels beside threat-alert metrics.
D:Sorting by ingestion time alone can fabricate an incorrect chain of events; this evidence or action is associated with case evidence timeline, whereas the case concerns analyst dashboard fidelity and calls for add telemetry-health panels beside threat-alert metrics.
Question 267
A Windows fleet must be checked for suspicious scheduled tasks during a targeted hunt. What finding is the strongest distinguishing indicator for triage?
- A repeatable adversary technique is more durable than one destination IP
- Cross-source sequence connects credential access to later lateral movement
- A family-specific combination of bytes or strings can identify related samples
- Remote read-only collection can enumerate task definitions at scale
Explanation
Correct Answer
D:PowerShell can gather Windows administrative artifacts without modifying endpoints. Confirmation should then examine task metadata, script execution transcripts and host coverage inventory; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
A:Tactical intelligence focuses on behaviors, tools and procedures supporting detections; that is suited to investigating tactical threat intelligence, whereas the PowerShell hunt scripts case requires remote read-only collection can enumerate task definitions at scale for recognizing the distinguishing signal.
B:Timeline reasoning can distinguish causal attack paths from unrelated alerts; that is suited to investigating threat-hunt timeline, whereas the PowerShell hunt scripts case requires remote read-only collection can enumerate task definitions at scale for recognizing the distinguishing signal.
C:This relates to YARA file matching: YARA rules can match file content and conditions beyond file names; the PowerShell hunt scripts question instead requires recognizing the distinguishing signal, specifically remote read-only collection can enumerate task definitions at scale.
Question 268
A critical case is acknowledged promptly but remains uncontained far beyond the target. Which observation most directly identifies the concern that needs investigation?
- A collection-scope increase explains part of the apparent incident increase
- Aggregate counts lack entity and event-level investigation context
- A control requires traceable privileged changes and accountable identities
- Acknowledgment compliance hides a missed containment service objective
Explanation
Correct Answer
D:Different SLA stages measure different responsibilities and risk exposures. Investigators should still corroborate it with ticket timestamps for detection, acknowledgment, escalation and enforcement before assigning definitive scope or attribution.
Incorrect Answers
A:Changes in sensor coverage can affect counts without changing attack frequency; applied to this SOC SLA breach case, it addresses incident trend analysis instead of the required step: acknowledgment compliance hides a missed containment service objective.
B:A useful dashboard should let analysts move from trend to underlying evidence; this evidence or action is associated with SOC dashboard drilldown, whereas the case concerns SOC SLA breach and calls for acknowledgment compliance hides a missed containment service objective.
C:Compliance detection should map to a specific control objective and evidence; that is suited to investigating compliance use case, whereas the SOC SLA breach case requires acknowledgment compliance hides a missed containment service objective for recognizing the distinguishing signal.
Question 269
An isolated database server repeatedly connects to a suspicious internet address. Select the most discriminating sign for the SOC assessment.
- Unusual remote interactive logons fan out from one compromised identity
- An unauthorized web-accessible file executes operating-system commands
- Unapproved periodic outbound sessions suggest covert external control
- Conflicting gateway MAC advertisements indicate a layer-two interception path
Explanation
Correct Answer
C:Server role and destination novelty increase concern compared with workstation traffic. The follow-up evidence is EDR process-to-socket mapping and historical firewall flows, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
A:The alternative concerns lateral movement through RDP: credentialed movement can look like normal RDP unless source and timing are reviewed; however, the described unexpected outbound C2 situation calls for unapproved periodic outbound sessions suggest covert external control.
B:For web shell discovery, a web shell creates remote execution independent of the original vulnerability; here the narrower objective is recognizing the distinguishing signal in unexpected outbound C2, best addressed by unapproved periodic outbound sessions suggest covert external control.
D:This relates to ARP interception: local spoofing can redirect traffic without changing internet routing tables; the unexpected outbound C2 question instead requires recognizing the distinguishing signal, specifically unapproved periodic outbound sessions suggest covert external control.
Question 270
An alert suggests threat-hunt timeline. The recorded clue is: Cross-source sequence connects credential access to later lateral movement. What evidence would best test this hypothesis?
- Report markings, intended audience and partner distribution agreement
- Malware sample bytes, encoded strings and rule condition test corpus
- Credential-related process access, account logons and remote tool execution times
- Task metadata, script execution transcripts and host coverage inventory
- Artifact query parameters, endpoint response status and resulting evidence
Explanation
Correct Answer
C:Time-normalized records show whether the proposed sequence is plausible. Linking these records back to cross-source sequence connects credential access to later lateral movement reduces reliance on an isolated indicator.
Incorrect Answers
A:This relates to TLP handling: release decisions must reflect both markings and contractual restrictions; the threat-hunt timeline question instead requires independently corroborating the suspected behavior, specifically credential-related process access, account logons and remote tool execution times.
B:For YARA file matching, benign and malicious corpora help estimate signature precision; here the narrower objective is independently corroborating the suspected behavior in threat-hunt timeline, best addressed by credential-related process access, account logons and remote tool execution times.
D:A defensible hunt records what was queried and on which systems, which would be relevant to PowerShell hunt scripts, but not the threat-hunt timeline scenario that requires credential-related process access, account logons and remote tool execution times.
E:Traceability matters across many simultaneous endpoint requests; prioritizing that velociraptor collection mechanism would leave this threat-hunt timeline decision unresolved because credential-related process access, account logons and remote tool execution times is the direct fit.