Question 340
A responder investigating password spraying has corroborated this finding: Low-rate failures spread across many identities rather than one victim. What action belongs next in the approved workflow?
- Isolate affected hosts and stop malicious processes while preserving evidence
- Block the malicious source or enforce risk-based authentication challenges
- Reset exposed weak service-account secrets and investigate credential theft
- Disable the malicious task and investigate its creator and dropped payloads
Explanation
Correct Answer
B:Per-user password resets alone may not stop attempts against the remaining tenant. For safe case progression, preserve the evidence and later verify no further distributed attempts and no suspicious successes for targeted accounts.
Incorrect Answers
A:Containment limits spread; backups should be assessed before any restoration; that is suited to investigating ransomware encryption, whereas the password spraying case requires block the malicious source or enforce risk-based authentication challenges for choosing the immediate operational response.
C:Address the service-account risk after scoping rather than treating ticket issuance itself as conclusive compromise; applied to this password spraying case, it addresses kerberoasting instead of the required step: block the malicious source or enforce risk-based authentication challenges.
D:Removing only the current process leaves the scheduled relaunch available; this evidence or action is associated with persistence via scheduled task, whereas the case concerns password spraying and calls for block the malicious source or enforce risk-based authentication challenges.
Question 341
A SOC analyst is investigating ARP cache poisoning and records this observation: Gateway IP mapping alternates between legitimate and unexpected MAC addresses. Which source or comparison would most directly corroborate it?
- Recursive DNS query logs tied to endpoint process and byte volume
- ARP replies and switch port-to-MAC association at the affected VLAN
- Destination-port distribution in firewall sessions or packet capture
- Edge request rates, provider flow counters and backend saturation metrics
Explanation
Correct Answer
B:Packet evidence and physical port mapping reveal who advertised the rogue mapping. This is particularly useful after the initial sign of gateway IP mapping alternates between legitimate and unexpected MAC addresses; the two forms of evidence test different parts of the case.
Incorrect Answers
A:The relationship between client process, suspicious domain and cadence distinguishes tunneling from ordinary lookups; this evidence or action is associated with DNS tunneling, whereas the case concerns ARP cache poisoning and calls for ARP replies and switch port-to-MAC association at the affected VLAN.
C:The alternative concerns vertical port scan: protocol and host tuples distinguish probing from ordinary multi-service application traffic; however, the described ARP cache poisoning situation calls for ARP replies and switch port-to-MAC association at the affected VLAN.
D:For distributed denial of service, combining network volume and application capacity identifies where exhaustion occurs; here the narrower objective is independently corroborating the suspected behavior in ARP cache poisoning, best addressed by ARP replies and switch port-to-MAC association at the affected VLAN.
Question 342
The working hypothesis concerns Windows explicit credentials. The initial finding is: Security event 4648 records an attempted logon with explicit credentials. Which evidence should investigators prioritize?
- Security log event 4625 fields including logon type and source address
- Event 4688 creator and new process fields plus command-line audit policy
- Event 4624 logon type, authentication package and source host correlation
- Event 4648 subject, target-account and process fields with destination logs
- Event 1102 subject account and independent forwarded prior events
Explanation
Correct Answer
D:Pairing the initiating record with remote sessions provides better attribution. The result can be compared with security event 4648 records an attempted logon with explicit credentials to verify that the suspected mechanism is actually present.
Incorrect Answers
A:This relates to Windows failed logons: correlating reason codes and origin reduces confusion with user typos or service failures; the Windows explicit credentials question instead requires independently corroborating the suspected behavior, specifically event 4648 subject, target-account and process fields with destination logs.
B:Without process creation and command line collection the SIEM may lack the evidence; that is suited to investigating Windows process start, whereas the Windows explicit credentials case requires event 4648 subject, target-account and process fields with destination logs for independently corroborating the suspected behavior.
C:A success record alone does not establish whether the session was authorized; applied to this Windows explicit credentials case, it addresses Windows successful logons instead of the required step: event 4648 subject, target-account and process fields with destination logs.
E:Remote copies help establish activity even after on-host records have been deleted; this evidence or action is associated with Windows audit log cleared, whereas the case concerns Windows explicit credentials and calls for event 4648 subject, target-account and process fields with destination logs.
Question 343
The team has responded to departing contractor access using this measure: Disable expired access and investigate post-termination activity. Which post-action evidence would justify declaring the measure effective?
- Restricted file transfer is blocked under policy and authorized workflows remain available
- Former contractor access is denied across all connected identity systems
- The account returns to protected standby with access tested under controls
- Unapproved export paths are closed and the investigation records verified scope
Explanation
Correct Answer
B:Verify federated and cached sessions rather than one application only. The measure should be evaluated against the actual action, disable expired access and investigate post-termination activity, rather than against ticket status.
Incorrect Answers
A:Verification includes device controls and data accessibility; this evidence or action is associated with unauthorized removable media, whereas the case concerns departing contractor access and calls for former contractor access is denied across all connected identity systems.
C:For misuse of break-glass account, MFA exception status should not obscure compensating safeguards; here the narrower objective is demonstrating that the remediation or control took effect in departing contractor access, best addressed by former contractor access is denied across all connected identity systems.
D:A blocked future clone does not prove earlier data was never copied, which would be relevant to suspicious source-code export, but not the departing contractor access scenario that requires former contractor access is denied across all connected identity systems.
Question 344
The first-line team is investigating strategic threat intelligence. Its preliminary finding is: Long-horizon adversary trends affect enterprise risk choices. What corroborating material is most decisive?
- Indicator first-seen, last-seen, source confidence and current ownership
- Payment-system threat scenarios, asset exposure and stakeholder decisions
- Process trees, known technique descriptions and observed telemetry fields
- Sourced industry trends, adversary targeting and confidence assessments
Explanation
Correct Answer
D:Decision-makers need credible context and uncertainty instead of raw indicators. The result can be compared with long-horizon adversary trends affect enterprise risk choices to verify that the suspected mechanism is actually present.
Incorrect Answers
A:Temporal context determines whether a reputation claim remains relevant; applied to this strategic threat intelligence case, it addresses IOC expiration instead of the required step: sourced industry trends, adversary targeting and confidence assessments.
B:For priority intelligence requirement, useful requirements start with protected services and expected consumer actions; here the narrower objective is independently corroborating the suspected behavior in strategic threat intelligence, best addressed by sourced industry trends, adversary targeting and confidence assessments.
C:This relates to tactical threat intelligence: technical behavior must be mappable to available enterprise data; the strategic threat intelligence question instead requires independently corroborating the suspected behavior, specifically sourced industry trends, adversary targeting and confidence assessments.
Question 345
The SOC has completed this action: Restore the rule at the approved deadline and test for renewed signal. Which result provides the strongest assurance that the specific problem was addressed?
- Canary events and ingestion statistics remain complete during quiet periods
- The responder can reproduce the alert and confirm the requested next step
- A representative test triggers after exception expiry without excess maintenance noise
- A known sequence from test hosts is represented in correct causal order
Explanation
Correct Answer
C:Expiry must be technically enforced, not only written in notes. That verification specifically tests whether the intervention to restore the rule at the approved deadline and test for renewed signal corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:For analyst dashboard fidelity, healthy monitoring is measurable even when no attacks occur; here the narrower objective is demonstrating that the remediation or control took effect in rule suppression expiry, best addressed by a representative test triggers after exception expiry without excess maintenance noise.
B:The alternative concerns ticket escalation evidence: acknowledgment without usable evidence is an incomplete handoff; however, the described rule suppression expiry situation calls for a representative test triggers after exception expiry without excess maintenance noise.
D:Timeline quality requires retained source provenance; applied to this rule suppression expiry case, it addresses case evidence timeline instead of the required step: a representative test triggers after exception expiry without excess maintenance noise.
Question 346
Analysts confirm the following observation: CEF header and extension key-value fields were not parsed into schema. Supporting material includes: Raw CEF sample compared with extracted deviceEventClassId and source fields. Which operational action addresses the issue most directly?
- Use a reliable protected syslog transport or local buffering relay
- Forward promptly to access-controlled, append-protected repositories
- Deploy the correct CEF parser and map source fields to the target schema
- Apply policy-driven hot retention plus protected long-term storage
Explanation
Correct Answer
C:Changing alert thresholds cannot compensate for missing event attributes. For safe case progression, preserve the evidence and later verify test messages populate the expected normalized fields without truncation.
Incorrect Answers
A:Transport acknowledgement and queueing improve survivability under packet loss; this evidence or action is associated with Syslog transport reliability, whereas the case concerns CEF parsing and calls for deploy the correct CEF parser and map source fields to the target schema.
B:This relates to log integrity: local file permissions cannot guarantee integrity against a fully privileged intruder; the CEF parsing question instead requires choosing the immediate operational response, specifically deploy the correct CEF parser and map source fields to the target schema.
D:Deleting aged indexed records is only acceptable after archive and retention obligations are met; prioritizing that log retention tiers mechanism would leave this CEF parsing decision unresolved because deploy the correct CEF parser and map source fields to the target schema is the direct fit.
Question 347
The team has responded to threat-feed poisoning using this measure: Quarantine suspicious feed updates pending validation. Which post-action evidence would justify declaring the measure effective?
- Collection results are complete, time-stamped and repeatable across targeted hosts
- Unverified indicators cannot enter enforcement lists and approved updates still flow
- Expired indicators stop driving blocks unless independently corroborated
- Reviewers can reproduce the domain's risk assessment from documented observations
Explanation
Correct Answer
B:An ingestion success counter does not demonstrate trustworthy intelligence. That verification specifically tests whether the intervention to quarantine suspicious feed updates pending validation corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:A script exit code alone does not prove every host responded, which would be relevant to PowerShell hunt scripts, but not the threat-feed poisoning scenario that requires unverified indicators cannot enter enforcement lists and approved updates still flow.
C:Reliable expiry should be enforced by the detection pipeline; applied to this threat-feed poisoning case, it addresses IOC expiration instead of the required step: unverified indicators cannot enter enforcement lists and approved updates still flow.
D:The alternative concerns feed confidence: a colorful reputation widget is not equivalent to substantiated confidence; however, the described threat-feed poisoning situation calls for unverified indicators cannot enter enforcement lists and approved updates still flow.
Question 348
An employee mailbox begins silently forwarding messages to an outside address after a risky sign-in. Which observation most directly identifies the concern that needs investigation?
- A payment redirection request deviates from verified supplier instructions
- An unexpected inbox rule or mailbox forwarding setting exports mail
- Attachment extraction precedes unexpected executable launch
- SPF, DKIM or DMARC alignment failures suggest identity spoofing
- Malicious mail reaches multiple recipients with a common redirect destination
Explanation
Correct Answer
B:Mailbox rules can maintain access without repeated interactive sign-ins. Confirmation should then examine mailbox audit of rule changes, actor session and forwarding targets; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
A:For business email compromise, BEC may contain no malware and relies on impersonation or account compromise; here the narrower objective is recognizing the distinguishing signal in mail forwarding persistence, best addressed by an unexpected inbox rule or mailbox forwarding setting exports mail.
C:File handling plus process ancestry links the email to endpoint compromise; this evidence or action is associated with malicious email attachment, whereas the case concerns mail forwarding persistence and calls for an unexpected inbox rule or mailbox forwarding setting exports mail.
D:Display names are not strong authentication proof for a message domain; prioritizing that email authentication spoofing mechanism would leave this mail forwarding persistence decision unresolved because an unexpected inbox rule or mailbox forwarding setting exports mail is the direct fit.
E:A campaign-level response must account for all delivered copies; that is suited to investigating credential-harvesting email campaign, whereas the mail forwarding persistence case requires an unexpected inbox rule or mailbox forwarding setting exports mail for recognizing the distinguishing signal.
Question 349
An alert suggests collector versus search tier. The recorded clue is: Incoming events accumulate while searchable event volume stays flat. What evidence would best test this hypothesis?
- Collector receipts, indexing queue metrics and storage pressure
- Peak event volume, connector throughput and ingestion-cost estimates
- Representative positive and benign events with expected outcomes
- Network isolation requirements, data residency policy and collector topology
Explanation
Correct Answer
A:Pipeline-stage timestamps reveal whether data is stuck before search. The result can be compared with incoming events accumulate while searchable event volume stays flat to verify that the suspected mechanism is actually present.
Incorrect Answers
B:For cloud SIEM elasticity, capacity analysis needs measured load rather than simply endpoint count; here the narrower objective is independently corroborating the suspected behavior in collector versus search tier, best addressed by collector receipts, indexing queue metrics and storage pressure.
C:Both attack-like and nonmalicious examples are needed to assess discrimination, which would be relevant to SIEM rule lifecycle, but not the collector versus search tier scenario that requires collector receipts, indexing queue metrics and storage pressure.
D:Platform choice must match where telemetry can legally and technically travel; this evidence or action is associated with on-premise SIEM tradeoff, whereas the case concerns collector versus search tier and calls for collector receipts, indexing queue metrics and storage pressure.
Question 350
An alert suggests HTTP request flood. The recorded clue is: Repeated application requests exceed normal per-client rate and strain resources. What evidence would best test this hypothesis?
- API gateway token ID, client IP, scope and request traces
- Resolver answer codes, query entropy and endpoint context
- Proxy flows, connection timestamps and owning endpoint process
- WAF request logs, endpoint latency and origin application metrics
Explanation
Correct Answer
D:Client patterns and resource saturation distinguish attack from successful promotion. Linking these records back to repeated application requests exceed normal per-client rate and strain resources reduces reliance on an isolated indicator.
Incorrect Answers
A:This relates to API token misuse: the token's privileges and actual use define exposure; the HTTP request flood question instead requires independently corroborating the suspected behavior, specifically WAF request logs, endpoint latency and origin application metrics.
B:The combined pattern is more robust than domain length alone; applied to this HTTP request flood case, it addresses DNS algorithmic names instead of the required step: WAF request logs, endpoint latency and origin application metrics.
C:This relates to low-and-slow beacon: timing statistics coupled with destination reputation distinguish routine polling; the HTTP request flood question instead requires independently corroborating the suspected behavior, specifically WAF request logs, endpoint latency and origin application metrics.