Question 680
Responders addressed unauthorized removable media using this measure: Suspend unauthorized transfer and initiate a controlled insider-risk investigation. What should the SOC test before considering closure?
- The account returns to protected standby with access tested under controls
- The privilege graph returns to approved state and suspicious sessions are terminated
- Restricted file transfer is blocked under policy and authorized workflows remain available
- Former contractor access is denied across all connected identity systems
Explanation
Correct Answer
C:Verification includes device controls and data accessibility. It documents the result of this response step—Suspend unauthorized transfer and initiate a controlled insider-risk investigation—and helps determine whether the protective state persists.
Incorrect Answers
A:MFA exception status should not obscure compensating safeguards; prioritizing that misuse of break-glass account mechanism would leave this unauthorized removable media decision unresolved because restricted file transfer is blocked under policy and authorized workflows remain available is the direct fit.
B:The original account's sign-out is not enough; prioritizing that compromised privileged account mechanism would leave this unauthorized removable media decision unresolved because restricted file transfer is blocked under policy and authorized workflows remain available is the direct fit.
D:For departing contractor access, verify federated and cached sessions rather than one application only; here the narrower objective is demonstrating that the remediation or control took effect in unauthorized removable media, best addressed by restricted file transfer is blocked under policy and authorized workflows remain available.
Question 681
A suspicious outbound transfer occurred and flow logs show bytes but no application content. What finding is the strongest distinguishing indicator for triage?
- Embedded strings and import tables can expose capabilities without running code
- Multiple clock sources and filesystem time fields distort incident chronology
- Volatile memory contains process and connection evidence not stored on disk
- Flow metadata cannot show all application-layer request details
Explanation
Correct Answer
D:Packet captures may reveal protocol features and transmitted payload when available. The follow-up evidence is PCAP capture point, five-tuple, TCP stream and TLS visibility constraints, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
A:The alternative concerns static malware strings: static analysis can identify likely functions while obfuscation limits conclusions; however, the described network packet evidence situation calls for flow metadata cannot show all application-layer request details.
B:This relates to forensic timeline: a forensic timeline must account for timezone, drift and timestamp semantics; the network packet evidence question instead requires recognizing the distinguishing signal, specifically flow metadata cannot show all application-layer request details.
C:A power cycle can eliminate decrypted payloads and ephemeral runtime artifacts; prioritizing that memory capture order mechanism would leave this network packet evidence decision unresolved because flow metadata cannot show all application-layer request details is the direct fit.
Question 682
The working evidence for velociraptor collection includes this observation: A centralized endpoint-query mechanism can collect specified artifacts consistently. Which intervention is the best fit for the established finding?
- Build an evidence-linked sequence and investigate the earliest suspicious precursor
- Run signed, approved read-only PowerShell collection with least privilege
- Translate the confirmed credential-access technique into a behavioral analytic
- Deploy an approved Velociraptor hunt with scoped artifact collection
Explanation
Correct Answer
D:Manual login to each host would be slower and less consistent. For safe case progression, preserve the evidence and later verify responses are linked to host identity and failed collections are retried or documented.
Incorrect Answers
A:Starting only from the final remote connection may miss entry and persistence; that is suited to investigating threat-hunt timeline, whereas the velociraptor collection case requires deploy an approved Velociraptor hunt with scoped artifact collection for choosing the immediate operational response.
B:Unrestricted remote script execution would increase risk and evidentiary uncertainty; applied to this velociraptor collection case, it addresses PowerShell hunt scripts instead of the required step: deploy an approved Velociraptor hunt with scoped artifact collection.
C:Blocking a single hash can miss the same technique implemented differently; that is suited to investigating tactical threat intelligence, whereas the velociraptor collection case requires deploy an approved Velociraptor hunt with scoped artifact collection for choosing the immediate operational response.
Question 683
The team has responded to executive SOC report using this measure: Summarize material incidents, response performance and recommended decisions. Which post-action evidence would justify declaring the measure effective?
- Recipients can identify the risk change and accountable corrective actions
- Follow-up exercises meet both communication and control-enforcement deadlines
- Exposure is closed and a repeated unauthorized update triggers an alert
- Trend comparisons use a consistent baseline and disclose coverage changes
Explanation
Correct Answer
A:A polished chart is not sufficient if decisions are unclear. It documents the result of this response step—Summarize material incidents, response performance and recommended decisions—and helps determine whether the protective state persists.
Incorrect Answers
B:A closed ticket is not proof of timely risk reduction; prioritizing that SOC SLA breach mechanism would leave this executive SOC report decision unresolved because recipients can identify the risk change and accountable corrective actions is the direct fit.
C:The alternative concerns cloud control-plane edit: rule state and future detection both matter; however, the described executive SOC report situation calls for recipients can identify the risk change and accountable corrective actions.
D:Metrics need explanatory denominators and transparent assumptions, which would be relevant to incident trend analysis, but not the executive SOC report scenario that requires recipients can identify the risk change and accountable corrective actions.
Question 684
The SOC has completed this action: Remove unauthorized methods and reset trusted authentication enrollment. Which result provides the strongest assurance that the specific problem was addressed?
- The privilege graph returns to approved state and suspicious sessions are terminated
- Critical records and transactions match approved recovery tolerances
- Only verified user methods remain and risky device sessions are revoked
- Old sessions are rejected and the user reauthenticates through a trusted device
- Previously issued suspect tokens fail and no unauthorized API actions continue
Explanation
Correct Answer
C:Test future sign-in requirements after the remediation. It documents the result of this response step—Remove unauthorized methods and reset trusted authentication enrollment—and helps determine whether the protective state persists.
Incorrect Answers
A:The original account's sign-out is not enough; prioritizing that compromised privileged account mechanism would leave this suspicious MFA enrollment decision unresolved because only verified user methods remain and risky device sessions are revoked is the direct fit.
B:Validated data quality is an explicit exit criterion; that is suited to investigating data-integrity validation, whereas the suspicious MFA enrollment case requires only verified user methods remain and risky device sessions are revoked for demonstrating that the remediation or control took effect.
D:A successful password change alone does not prove session eviction, which would be relevant to stolen user password, but not the suspicious MFA enrollment scenario that requires only verified user methods remain and risky device sessions are revoked.
E:This relates to refresh token theft: verify at the service endpoint, not just the identity console; the suspicious MFA enrollment question instead requires demonstrating that the remediation or control took effect, specifically only verified user methods remain and risky device sessions are revoked.
Question 685
Analysts confirm the following observation: Partial hash resemblance does not establish common malware family. Supporting material includes: Code similarity, YARA features, protocol patterns and tooling overlaps. Which operational action addresses the issue most directly?
- Classify by observed behaviors and record confidence separately from indicator matches
- Capture memory with approved methods before shutting down when safe
- Execute only in an instrumented isolated sandbox with controlled egress
- Preserve the original MIME message and examine headers and URLs safely
Explanation
Correct Answer
A:Guessing a family from a file name can contaminate later response decisions. For safe case progression, preserve the evidence and later verify independent samples reproduce the assigned traits and exclusions are documented.
Incorrect Answers
B:Prioritization must consider safety and continued attacker access, which would be relevant to memory capture order, but not the malware family attribution scenario that requires classify by observed behaviors and record confidence separately from indicator matches.
C:The alternative concerns dynamic sandbox behavior: running the sample on a production endpoint is unnecessary and unsafe; however, the described malware family attribution situation calls for classify by observed behaviors and record confidence separately from indicator matches.
D:Clicking the link from an analyst workstation could trigger credential theft or tracking; this evidence or action is associated with email artifact examination, whereas the case concerns malware family attribution and calls for classify by observed behaviors and record confidence separately from indicator matches.
Question 686
The first-line team is investigating SOC dashboard drilldown. Its preliminary finding is: Aggregate counts lack entity and event-level investigation context. What corroborating material is most decisive?
- Source events with identity, origin and failure reason fields
- Sensor onboarding dates, comparable asset population and severity trends
- Ticket timestamps for detection, acknowledgment, escalation and enforcement
- Incident severity trends, containment intervals and control-gap records
Explanation
Correct Answer
A:Those attributes support root-cause and targeted triage. Linking these records back to aggregate counts lack entity and event-level investigation context reduces reliance on an isolated indicator.
Incorrect Answers
B:For incident trend analysis, normalizing by coverage makes before-and-after comparisons fairer; here the narrower objective is independently corroborating the suspected behavior in SOC dashboard drilldown, best addressed by source events with identity, origin and failure reason fields.
C:The timeline must separate workflow touches from effective mitigation, which would be relevant to SOC SLA breach, but not the SOC dashboard drilldown scenario that requires source events with identity, origin and failure reason fields.
D:Outcome measures connect operational activity to risk management; this evidence or action is associated with executive SOC report, whereas the case concerns SOC dashboard drilldown and calls for source events with identity, origin and failure reason fields.
Question 687
During an investigation of sigma rule portability, the SOC validates this finding: A detection is expressed in a product-neutral Sigma rule definition. What should the response owner do next?
- Tune deviation thresholds against the developer's established normal behavior
- Translate the rule and test it against native SIEM events
- Use a managed scalable deployment with volume budgets and tiering
- Treat generated logic as an untrusted draft requiring human review and backtesting
Explanation
Correct Answer
B:Copying a query without checking source schemas can produce silent misses. The response must subsequently be checked by confirming both backends detect the same representative behavior with acceptable precision; otherwise the original exposure may persist.
Incorrect Answers
A:Permanent broad exclusions would hide malicious shifts in the same role; applied to this sigma rule portability case, it addresses behavioral baselines instead of the required step: translate the rule and test it against native SIEM events.
C:Scaling alone cannot correct noisy or unnecessary telemetry collection; this evidence or action is associated with cloud SIEM elasticity, whereas the case concerns sigma rule portability and calls for translate the rule and test it against native SIEM events.
D:The alternative concerns AI-generated SIEM logic: automatically deploying AI output risks false negatives and operational noise; however, the described sigma rule portability situation calls for translate the rule and test it against native SIEM events.
Question 688
The team has responded to vertical port scan using this measure: Check whether the source is an approved scanner and isolate if malicious. Which post-action evidence would justify declaring the measure effective?
- Related messages are removed and impacted identities have no active illicit sessions
- Legitimate user success rates and backend capacity return to baseline
- Unapproved connection attempts cease and network telemetry confirms containment
- The sweep stops and the source is confirmed unauthorized or approved
Explanation
Correct Answer
C:A dashboard alert count alone cannot validate that all probes stopped. It documents the result of this response step—Check whether the source is an approved scanner and isolate if malicious—and helps determine whether the protective state persists.
Incorrect Answers
A:This relates to phishing attachment: an empty mailbox search alone does not establish account security; the vertical port scan question instead requires demonstrating that the remediation or control took effect, specifically unapproved connection attempts cease and network telemetry confirms containment.
B:Traffic reduction is insufficient if real users still cannot complete transactions; prioritizing that distributed denial of service mechanism would leave this vertical port scan decision unresolved because unapproved connection attempts cease and network telemetry confirms containment is the direct fit.
D:A drop in alerts without source attribution could hide continuing reconnaissance; that is suited to investigating horizontal port scan, whereas the vertical port scan case requires unapproved connection attempts cease and network telemetry confirms containment for demonstrating that the remediation or control took effect.
Question 689
A database server begins outbound traffic to a new internet address over an unapproved port. Select the most discriminating sign for the SOC assessment.
- Repeated application requests exceed normal per-client rate and strain resources
- Repeated intervals with low timing variance suggest automated callbacks
- New external connection crosses the server's established egress baseline
- Certificate issuer or fingerprint differs from a known pinned service identity
Explanation
Correct Answer
C:Server function and approved destinations define whether a flow is suspicious. Confirmation should then examine flow records, firewall policy, asset role and initiating process; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
A:For HTTP request flood, an HTTP-layer flood can exhaust application resources without extreme packet volume; here the narrower objective is recognizing the distinguishing signal in unexpected outbound port, best addressed by new external connection crosses the server's established egress baseline.
B:Periodic communication can occur in benign agents, so rarity and process context matter; applied to this unexpected outbound port case, it addresses low-and-slow beacon instead of the required step: new external connection crosses the server's established egress baseline.
D:Unexpected certificate changes can indicate interception or legitimate rotation; this evidence or action is associated with TLS certificate anomaly, whereas the case concerns unexpected outbound port and calls for new external connection crosses the server's established egress baseline.
Question 690
Responders suspect run key persistence based on this observation: A user- or machine-level autorun value points to a suspicious script. Which artifact should be examined first?
- Directory audit of member, group, actor and change ticket linkage
- Process token integrity, ancestry and authentication or consent records
- Task creation events, task XML and executable hash correlation
- Registry change telemetry with value data and modifying process
- Domain controller 4769 records and requestor host process lineage
Explanation
Correct Answer
D:The value payload and actor are needed beyond a generic registry-edit count. The result can be compared with a user- or machine-level autorun value points to a suspicious script to verify that the suspected mechanism is actually present.
Incorrect Answers
A:The alternative concerns domain admin group change: effective group membership and actor authorization determine the risk; however, the described run key persistence situation calls for registry change telemetry with value data and modifying process.
B:An administrator account alone does not prove legitimate elevation; applied to this run key persistence case, it addresses privilege token misuse instead of the required step: registry change telemetry with value data and modifying process.
C:The registration identity and command path expose the mechanism; prioritizing that scheduled task persistence mechanism would leave this run key persistence decision unresolved because registry change telemetry with value data and modifying process is the direct fit.
E:Ticket request context and service names help avoid misreading normal delegation; that is suited to investigating Kerberos ticket anomaly, whereas the run key persistence case requires registry change telemetry with value data and modifying process for independently corroborating the suspected behavior.