Question 230
Analysts confirm the following observation: A user- or machine-level autorun value points to a suspicious script. Supporting material includes: Registry change telemetry with value data and modifying process. Which operational action addresses the issue most directly?
- Monitor security-relevant autorun keys and assess new launch targets
- Restrict time windows, use indexed fields and schedule appropriately
- Build per-principal SPN and host baselines with targeted anomaly rules
- Detect unapproved task definitions and investigate the registering process
Explanation
Correct Answer
A:Blocking all registry edits is infeasible and would not identify persistence intent. The response must subsequently be checked by confirming a test autorun modification is attributed correctly and removed entries stay absent; otherwise the original exposure may persist.
Incorrect Answers
B:For analytic query cost, reducing sensitivity by deleting events is not an acceptable first optimization; here the narrower objective is choosing the immediate operational response in run key persistence, best addressed by monitor security-relevant autorun keys and assess new launch targets.
C:Counting all Kerberos traffic globally will produce weak, noisy alerts; prioritizing that Kerberos ticket anomaly mechanism would leave this run key persistence decision unresolved because monitor security-relevant autorun keys and assess new launch targets is the direct fit.
D:Deleting the running process is insufficient if the trigger remains installed; that is suited to investigating scheduled task persistence, whereas the run key persistence case requires monitor security-relevant autorun keys and assess new launch targets for choosing the immediate operational response.
Question 231
The first-line team is investigating Kerberos ticket anomaly. Its preliminary finding is: TGS request breadth differs sharply from the account's role baseline. What corroborating material is most decisive?
- Domain controller 4769 records and requestor host process lineage
- API gateway token ID, client IP, scope and request traces
- Process token integrity, ancestry and authentication or consent records
- Task creation events, task XML and executable hash correlation
Explanation
Correct Answer
A:Ticket request context and service names help avoid misreading normal delegation. The result can be compared with TGS request breadth differs sharply from the account's role baseline to verify that the suspected mechanism is actually present.
Incorrect Answers
B:The token's privileges and actual use define exposure; this evidence or action is associated with API token misuse, whereas the case concerns Kerberos ticket anomaly and calls for domain controller 4769 records and requestor host process lineage.
C:An administrator account alone does not prove legitimate elevation; applied to this Kerberos ticket anomaly case, it addresses privilege token misuse instead of the required step: domain controller 4769 records and requestor host process lineage.
D:The registration identity and command path expose the mechanism; prioritizing that scheduled task persistence mechanism would leave this Kerberos ticket anomaly decision unresolved because domain controller 4769 records and requestor host process lineage is the direct fit.
Question 232
To verify remediation of DNS tunneling, the team reports taking this action: Investigate the originating process and restrict suspicious domain resolution. Which outcome should the analyst demand?
- Clients resolve the real gateway MAC and no further spoofed ARP appears
- Legitimate user success rates and backend capacity return to baseline
- Host network activity and resolver records show no continued encoded lookups
- The sweep stops and the source is confirmed unauthorized or approved
Explanation
Correct Answer
C:Confirm both endpoint remediation and disappearance of the suspicious DNS traffic. That verification specifically tests whether the intervention to investigate the originating process and restrict suspicious domain resolution corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:A successful web refresh without ARP validation does not prove that interception ended; prioritizing that ARP cache poisoning mechanism would leave this DNS tunneling decision unresolved because host network activity and resolver records show no continued encoded lookups is the direct fit.
B:Traffic reduction is insufficient if real users still cannot complete transactions; applied to this DNS tunneling case, it addresses distributed denial of service instead of the required step: host network activity and resolver records show no continued encoded lookups.
D:For horizontal port scan, a drop in alerts without source attribution could hide continuing reconnaissance; here the narrower objective is demonstrating that the remediation or control took effect in DNS tunneling, best addressed by host network activity and resolver records show no continued encoded lookups.
Question 233
A Tier 1 analyst confirms suspicious remote execution on a production authentication server during the night shift. Which finding best distinguishes this activity from a routine operational change?
- Two active tickets have no explicit primary incident owner
- Alerts span infrastructure telemetry and enterprise identity activity
- A correlated successful session following repeated rejected credentials
- A confirmed compromise exceeds first-line triage authority
Explanation
Correct Answer
D:Tier 1 validates alerts and routes material incidents to designated responders rather than independently changing critical systems. Confirmation should then examine an EDR timeline plus asset criticality and escalation policy; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
A:Duplicated tracking without an accountable lead can create gaps in containment and communications; applied to this tier-one escalation case, it addresses incident ownership instead of the required step: a confirmed compromise exceeds first-line triage authority.
B:No single team has the full evidence needed to decide whether a cloud workload is compromised; this evidence or action is associated with hybrid SOC coordination, whereas the case concerns tier-one escalation and calls for a confirmed compromise exceeds first-line triage authority.
C:This relates to triage versus investigation: the success after failures changes the event from a noisy authentication anomaly to a potential compromise; the tier-one escalation question instead requires recognizing the distinguishing signal, specifically a confirmed compromise exceeds first-line triage authority.
Question 234
The SOC has completed this action: Restrict vulnerable exposure and track a dated remediation exception. Which result provides the strongest assurance that the specific problem was addressed?
- Approved users authenticate and compromised credentials are demonstrably unusable
- Host integrity checks pass and monitored services behave normally after reconnection
- The observation period shows no verified malicious activity with healthy data coverage
- The exploit route is blocked under tests and the permanent fix has an owner
- Critical records and transactions match approved recovery tolerances
Explanation
Correct Answer
D:Temporary controls should be monitored and expire with review. That verification specifically tests whether the intervention to restrict vulnerable exposure and track a dated remediation exception corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:Operational success and security assurance must both be established; that is suited to investigating recovered identity service, whereas the compensating controls case requires the exploit route is blocked under tests and the permanent fix has an owner for demonstrating that the remediation or control took effect.
B:The alternative concerns golden image rebuild: restore procedures should not reimport attacker persistence; however, the described compensating controls situation calls for the exploit route is blocked under tests and the permanent fix has an owner.
C:For postincident monitoring, an empty dashboard is meaningful only if sources were functioning; here the narrower objective is demonstrating that the remediation or control took effect in compensating controls, best addressed by the exploit route is blocked under tests and the permanent fix has an owner.
E:Validated data quality is an explicit exit criterion; this evidence or action is associated with data-integrity validation, whereas the case concerns compensating controls and calls for the exploit route is blocked under tests and the permanent fix has an owner.
Question 235
The SOC has completed this action: Enable persistent journal storage or reliable remote forwarding as needed. Which result provides the strongest assurance that the specific problem was addressed?
- Pre-reboot test events remain accessible after restart or at the collector
- A controlled rejected SSH login appears centrally with the originating address
- A known test event is retrieved with matching process and timestamp
- A test write yields traceable identity, path and operation in the central store
Explanation
Correct Answer
A:Testing only new events after boot would miss the historical-loss defect. It documents the result of this response step—Enable persistent journal storage or reliable remote forwarding as needed—and helps determine whether the protective state persists.
Incorrect Answers
B:The alternative concerns Linux SSH failures: validating source IP and timestamp prevents misleading aggregation; however, the described systemd journal persistence situation calls for pre-reboot test events remain accessible after restart or at the collector.
C:Successful forwarding requires interpretable content, not only a collector heartbeat, which would be relevant to macOS unified logging, but not the systemd journal persistence scenario that requires pre-reboot test events remain accessible after restart or at the collector.
D:A record of file existence is not equivalent to a modification audit; this evidence or action is associated with Linux auditd file access, whereas the case concerns systemd journal persistence and calls for pre-reboot test events remain accessible after restart or at the collector.
Question 236
A SOC analyst is investigating on-premise SIEM tradeoff and records this observation: An externally dependent hosted service cannot satisfy offline operation. Which source or comparison would most directly corroborate it?
- Collector receipts, indexing queue metrics and storage pressure
- Rule inventory, asset ownership and change records
- Representative positive and benign events with expected outcomes
- Network isolation requirements, data residency policy and collector topology
Explanation
Correct Answer
D:Platform choice must match where telemetry can legally and technically travel. This is particularly useful after the initial sign of an externally dependent hosted service cannot satisfy offline operation; the two forms of evidence test different parts of the case.
Incorrect Answers
A:Pipeline-stage timestamps reveal whether data is stuck before search; that is suited to investigating collector versus search tier, whereas the on-premise SIEM tradeoff case requires network isolation requirements, data residency policy and collector topology for independently corroborating the suspected behavior.
B:Business ownership identifies whether the use case still protects a live process; prioritizing that security use case owner mechanism would leave this on-premise SIEM tradeoff decision unresolved because network isolation requirements, data residency policy and collector topology is the direct fit.
C:Both attack-like and nonmalicious examples are needed to assess discrimination, which would be relevant to SIEM rule lifecycle, but not the on-premise SIEM tradeoff scenario that requires network isolation requirements, data residency policy and collector topology.
Question 237
A daily SOC chart shows fewer alerts after a telemetry connector silently fails. Select the most discriminating sign for the SOC assessment.
- Alert count falls at the same time source-ingestion volume disappears
- The ticket omits observed artifacts, scope and business impact
- The initial symptom is gone but scoping and remediation proof are missing
- Unnormalized timestamps scramble the apparent sequence of attacker actions
Explanation
Correct Answer
A:Volume reduction can reflect a blind spot rather than improved risk. Investigators should still corroborate it with per-source heartbeat, parse success and event-time freshness indicators before assigning definitive scope or attribution.
Incorrect Answers
B:This relates to ticket escalation evidence: a receiving responder cannot reproduce the conclusion from a vague label; the analyst dashboard fidelity question instead requires recognizing the distinguishing signal, specifically alert count falls at the same time source-ingestion volume disappears.
C:The alternative concerns case closure standard: process termination may occur while persistence and stolen access survive; however, the described analyst dashboard fidelity situation calls for alert count falls at the same time source-ingestion volume disappears.
D:The investigative narrative relies on trustworthy event ordering; prioritizing that case evidence timeline mechanism would leave this analyst dashboard fidelity decision unresolved because alert count falls at the same time source-ingestion volume disappears is the direct fit.
Question 238
A responder investigating refresh token theft has corroborated this finding: Existing tokens continue authorizing API access despite password reset. What action belongs next in the approved workflow?
- Disable or reset compromised credentials and revoke active sessions
- Revoke malicious grants, secure the administrator and investigate downstream changes
- Remove unauthorized methods and reset trusted authentication enrollment
- Explicitly revoke relevant sessions or token grants and review consent
Explanation
Correct Answer
D:Relying solely on credential rotation may leave bearer access alive. The response must subsequently be checked by confirming previously issued suspect tokens fail and no unauthorized API actions continue; otherwise the original exposure may persist.
Incorrect Answers
A:Changing only the password may not immediately invalidate all existing tokens, which would be relevant to stolen user password, but not the refresh token theft scenario that requires explicitly revoke relevant sessions or token grants and review consent.
B:Disabling the first account leaves attacker-created access paths otherwise intact; prioritizing that compromised privileged account mechanism would leave this refresh token theft decision unresolved because explicitly revoke relevant sessions or token grants and review consent is the direct fit.
C:The alternative concerns suspicious MFA enrollment: deleting one sign-in event does not eliminate the attacker's factor; however, the described refresh token theft situation calls for explicitly revoke relevant sessions or token grants and review consent.
Question 239
During an investigation of ransomware lessons learned, the SOC validates this finding: The initiating vulnerability remains open after malware removal. What should the response owner do next?
- Restrict compromised backup administrators and protect offline or immutable copies
- Apply the root-cause fix and update detections and runbooks
- Isolate compromised hosts and interrupt affected share access promptly
- Preserve exfiltration evidence and involve privacy and legal response owners
Explanation
Correct Answer
B:A retrospective report without assigned remediations does not reduce risk. Operational success is not assumed until adversary simulation no longer succeeds and ownership for residual risk is recorded, the relevant outcome for this response.
Incorrect Answers
A:A new scheduled backup is not safe if the attacker retains admin access, which would be relevant to compromised backup repository, but not the ransomware lessons learned scenario that requires apply the root-cause fix and update detections and runbooks.
C:For ransomware early containment, waiting for a ransom note before response increases impact; here the narrower objective is choosing the immediate operational response in ransomware lessons learned, best addressed by apply the root-cause fix and update detections and runbooks.
D:Restoring encrypted files does not resolve potential disclosure obligations; prioritizing that double extortion mechanism would leave this ransomware lessons learned decision unresolved because apply the root-cause fix and update detections and runbooks is the direct fit.
Question 240
Investigators are handling a powered-on workstation suspected of memory-resident malware. Which TWO types of ephemeral evidence should they prioritize when safe and authorized? Choose TWO.
- Record active network connections and process state with timestamps
- Power off immediately and assume all runtime artifacts will persist on disk
- Capture volatile memory using a documented forensic procedure
- Erase temporary files to simplify later forensic searches
- Collect only the wallpaper image from the user's desktop
Explanation
Correct Answers
A:Live sockets and execution relationships can identify command channels and transient processes. These records aid later memory and disk analysis.
C:Runtime memory may contain code, keys and injected processes that vanish when power is lost. Acquisition metadata should be recorded.
Incorrect Answers
B:Shutdown can destroy volatile information and change system state. Safety considerations may alter the plan, but preservation is the aim here.
D:Deletion changes evidence and can remove useful artifacts. Forensic acquisition should minimize destructive actions.
E:Visual customization provides little direct insight into in-memory execution or active sessions. Target volatile security artifacts instead.