Question 380
Analysts confirm the following observation: Resolver query logs reveal client, queried name and response patterns. Supporting material includes: DNS query timestamps and endpoint process-to-domain attribution. Which operational action addresses the issue most directly?
- Forward recursive resolver events and normalize queried-domain fields
- Correlate proxy sessions with sign-in and endpoint posture signals
- Review the precise blocking rule and approved traffic requirement
- Enrich SIEM events with time-aware lease assignments
Explanation
Correct Answer
A:A firewall flow record usually lacks the full DNS name required for this detection. The response must subsequently be checked by confirming test lookups appear with correct query name and client identity centrally; otherwise the original exposure may persist.
Incorrect Answers
B:Policy action must be based on authenticated context, not destination reputation alone; prioritizing that HTTP proxy authentication mechanism would leave this DNS resolver logs decision unresolved because forward recursive resolver events and normalize queried-domain fields is the direct fit.
C:Allowing an entire subnet would exceed the authorized exception; this evidence or action is associated with firewall denied connection, whereas the case concerns DNS resolver logs and calls for forward recursive resolver events and normalize queried-domain fields.
D:This relates to DHCP lease attribution: static IP-to-host lookups can attribute yesterday's behavior to today's device; the DNS resolver logs question instead requires choosing the immediate operational response, specifically forward recursive resolver events and normalize queried-domain fields.
Question 381
The working hypothesis concerns broken object authorization. The initial finding is: Cross-tenant object access succeeds despite a valid low-privilege session. Which evidence should investigators prioritize?
- Stored record, browser evidence, CSP reports and affected users
- API gateway request rates, per-identity outcomes and server resource pressure
- Access logs with actor, requested object and owner tenant
- Web request payloads, database statement logs and affected record counts
Explanation
Correct Answer
C:The impact depends on which unauthorized resources were accessed. The result can be compared with cross-tenant object access succeeds despite a valid low-privilege session to verify that the suspected mechanism is actually present.
Incorrect Answers
A:Victim execution and persistence must be verified separately; applied to this broken object authorization case, it addresses stored XSS incident instead of the required step: access logs with actor, requested object and owner tenant.
B:Rate and success evidence distinguishes brute force from traffic spikes; this evidence or action is associated with API rate-limit incident, whereas the case concerns broken object authorization and calls for access logs with actor, requested object and owner tenant.
D:This relates to active SQL injection: backend access evidence is needed to establish what the attacker retrieved; the broken object authorization question instead requires independently corroborating the suspected behavior, specifically access logs with actor, requested object and owner tenant.
Question 382
An external host sends SYN probes to hundreds of internal addresses on the same destination port within a minute. Select the most discriminating sign for the SOC assessment.
- One source sweeping many destinations on a fixed service port
- Many destination ports targeted on a single host from one source
- A multi-origin traffic surge exhausts service or upstream capacity
- High-entropy repeated subdomains with abnormal query and answer patterns
Explanation
Correct Answer
A:Horizontal scanning searches for an exposed service across hosts, unlike per-host enumeration. Confirmation should then examine netFlow or firewall connection tuples with source, destination and port; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
B:Vertical scanning enumerates services on one machine rather than locating a service across many machines; applied to this horizontal port scan case, it addresses vertical port scan instead of the required step: one source sweeping many destinations on a fixed service port.
C:Distributed request or packet floods differ from a single malfunctioning client; this evidence or action is associated with distributed denial of service, whereas the case concerns horizontal port scan and calls for one source sweeping many destinations on a fixed service port.
D:Encoded payloads can be hidden in DNS labels or record data to tunnel information; that is suited to investigating DNS tunneling, whereas the horizontal port scan case requires one source sweeping many destinations on a fixed service port for recognizing the distinguishing signal.
Question 383
A packed sample contains almost no readable strings and must be analyzed for behavior. Which additional finding would most directly support the suspected security interpretation?
- Malicious script or injected code exists primarily in process memory
- Display sender and visible hyperlink text differ from technical message origins
- Partial hash resemblance does not establish common malware family
- Code packing obscures static features but may unpack during controlled execution
Explanation
Correct Answer
D:Dynamic analysis reveals processes, files and network activity in an isolated environment. Investigators should still corroborate it with sandbox process tree, dropped files, registry changes and captured traffic before assigning definitive scope or attribution.
Incorrect Answers
A:File-scanning alone can miss in-memory execution and injected modules, which would be relevant to fileless malware investigation, but not the dynamic sandbox behavior scenario that requires code packing obscures static features but may unpack during controlled execution.
B:For email artifact examination, header and URL analysis can reveal spoofing and hidden destinations; here the narrower objective is recognizing the distinguishing signal in dynamic sandbox behavior, best addressed by code packing obscures static features but may unpack during controlled execution.
C:Cryptographic hashes are exact identifiers; family inference requires features and behavior; this evidence or action is associated with malware family attribution, whereas the case concerns dynamic sandbox behavior and calls for code packing obscures static features but may unpack during controlled execution.
Question 384
To verify remediation of stored XSS incident, the team reports taking this action: Remove malicious content and fix context-specific output encoding. Which outcome should the analyst demand?
- No unapproved executable files remain and upload controls reject the exploit pattern
- Previously affected pages render safely and malicious script no longer runs
- Exploit tests fail and database access confirms no further unauthorized reads
- Legitimate sign-in works while simulated abuse receives appropriate limits
- Cross-tenant requests return denial and authorized tenant reads still succeed
Explanation
Correct Answer
B:The data field should remain functional with harmless text. The measure should be evaluated against the actual action, remove malicious content and fix context-specific output encoding, rather than against ticket status.
Incorrect Answers
A:A clean front page does not demonstrate web-tier security; that is suited to investigating web shell discovery, whereas the stored XSS incident case requires previously affected pages render safely and malicious script no longer runs for demonstrating that the remediation or control took effect.
C:A hidden error page is not evidence of secure query construction; applied to this stored XSS incident case, it addresses active SQL injection instead of the required step: previously affected pages render safely and malicious script no longer runs.
D:For API rate-limit incident, measure both attack suppression and normal-user success; here the narrower objective is demonstrating that the remediation or control took effect in stored XSS incident, best addressed by previously affected pages render safely and malicious script no longer runs.
E:A passing authentication test does not validate authorization; this evidence or action is associated with broken object authorization, whereas the case concerns stored XSS incident and calls for previously affected pages render safely and malicious script no longer runs.
Question 385
To verify remediation of SOC dashboard drilldown, the team reports taking this action: Add filtered drilldowns to the corresponding raw SIEM events. Which outcome should the analyst demand?
- Analysts can move from aggregate spike to correct source events promptly
- Trend comparisons use a consistent baseline and disclose coverage changes
- Follow-up exercises meet both communication and control-enforcement deadlines
- A test unauthorized change is retained, flagged and included in reports
Explanation
Correct Answer
A:Dashboard usefulness is measured by investigative outcomes, not colors. It documents the result of this response step—Add filtered drilldowns to the corresponding raw SIEM events—and helps determine whether the protective state persists.
Incorrect Answers
B:This relates to incident trend analysis: metrics need explanatory denominators and transparent assumptions; the SOC dashboard drilldown question instead requires demonstrating that the remediation or control took effect, specifically analysts can move from aggregate spike to correct source events promptly.
C:A closed ticket is not proof of timely risk reduction; applied to this SOC dashboard drilldown case, it addresses SOC SLA breach instead of the required step: analysts can move from aggregate spike to correct source events promptly.
D:The alternative concerns compliance use case: an audit-ready trail requires both detection and defensible evidence; however, the described SOC dashboard drilldown situation calls for analysts can move from aggregate spike to correct source events promptly.
Question 386
A Windows fleet must be checked for suspicious scheduled tasks during a targeted hunt. Supporting evidence includes: Task metadata, script execution transcripts and host coverage inventory. Which next step most directly reduces the described risk?
- Build an evidence-linked sequence and investigate the earliest suspicious precursor
- Run signed, approved read-only PowerShell collection with least privilege
- Write and test a YARA rule with multiple discriminating strings
- Deploy an approved Velociraptor hunt with scoped artifact collection
Explanation
Correct Answer
B:Unrestricted remote script execution would increase risk and evidentiary uncertainty. For safe case progression, preserve the evidence and later verify collection results are complete, time-stamped and repeatable across targeted hosts.
Incorrect Answers
A:The alternative concerns threat-hunt timeline: starting only from the final remote connection may miss entry and persistence; however, the described PowerShell hunt scripts situation calls for run signed, approved read-only PowerShell collection with least privilege.
C:Matching one common library string risks alerting on harmless programs; prioritizing that YARA file matching mechanism would leave this PowerShell hunt scripts decision unresolved because run signed, approved read-only PowerShell collection with least privilege is the direct fit.
D:Manual login to each host would be slower and less consistent; applied to this PowerShell hunt scripts case, it addresses velociraptor collection instead of the required step: run signed, approved read-only PowerShell collection with least privilege.
Question 387
Events from regional systems appear in the SIEM in an impossible order across time zones. Select the most discriminating sign for the SOC assessment.
- Local logs alone are vulnerable to privileged alteration or deletion
- Mixed local timestamps without consistent time-zone interpretation
- Best-effort UDP syslog can lose messages during congestion
- CEF header and extension key-value fields were not parsed into schema
Explanation
Correct Answer
B:Chronological investigations fail when event times are normalized incorrectly. Confirmation should then examine raw timestamp, time-zone offset, ingest time and NTP health; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
A:This relates to log integrity: independent storage protects evidence when an attacker controls the source host; the timestamp normalization question instead requires recognizing the distinguishing signal, specifically mixed local timestamps without consistent time-zone interpretation.
C:Traditional UDP transport provides no built-in delivery acknowledgement; this evidence or action is associated with Syslog transport reliability, whereas the case concerns timestamp normalization and calls for mixed local timestamps without consistent time-zone interpretation.
D:Unparsed structured messages cannot support reliable field-based correlation, which would be relevant to CEF parsing, but not the timestamp normalization scenario that requires mixed local timestamps without consistent time-zone interpretation.
Question 388
Analysts confirm the following observation: Managed threat detection flags suspicious workload behavior. Supporting material includes: GuardDuty finding details plus VPC and workload activity context. Which operational action addresses the issue most directly?
- Configure organization-level finding aggregation and response routing
- Triage the finding and apply scoped containment to confirmed compromised resources
- Ingest and map relevant logs then test behavioral detections in Google SecOps
- Preserve trails and investigate or revert the unauthorized IAM modification
Explanation
Correct Answer
B:Simply enabling Security Hub aggregation does not remediate the instance. The response must subsequently be checked by confirming malicious communication stops and the finding is dispositioned with supporting evidence; otherwise the original exposure may persist.
Incorrect Answers
A:CloudTrail log delivery alone does not provide unified finding management; applied to this GuardDuty compromise finding case, it addresses AWS Security Hub aggregation instead of the required step: triage the finding and apply scoped containment to confirmed compromised resources.
C:A standalone SCC finding does not replace cross-source SIEM analytics; that is suited to investigating Google SecOps investigation, whereas the GuardDuty compromise finding case requires triage the finding and apply scoped containment to confirmed compromised resources for choosing the immediate operational response.
D:VPC network flow monitoring does not directly record policy API changes; prioritizing that CloudTrail administrative audit mechanism would leave this GuardDuty compromise finding decision unresolved because triage the finding and apply scoped containment to confirmed compromised resources is the direct fit.
Question 389
Analysts confirm the following observation: A deceptive message redirects recipients to an attacker-controlled login page. Supporting material includes: Email headers, redirect chain, URL reputation and sign-in audit events. Which operational action addresses the issue most directly?
- Enforce anti-CSRF tokens and suitable cookie SameSite settings
- Escalate under insider-threat procedures and preserve access evidence
- Check whether the source is an approved scanner and isolate if malicious
- Quarantine the campaign, invalidate exposed sessions and warn affected users
Explanation
Correct Answer
D:Removing mail limits further clicks but does not revoke already compromised tokens. For safe case progression, preserve the evidence and later verify related messages are removed and impacted identities have no active illicit sessions.
Incorrect Answers
A:This relates to cross-site request forgery: request origin defenses must protect state-changing operations while respecting normal workflows; the phishing attachment question instead requires choosing the immediate operational response, specifically quarantine the campaign, invalidate exposed sessions and warn affected users.
B:The alternative concerns insider bulk export: controlled review protects privacy and avoids an unsupported accusation from volume alone; however, the described phishing attachment situation calls for quarantine the campaign, invalidate exposed sessions and warn affected users.
C:For vertical port scan, authorization context prevents disruption of legitimate scheduled assessments; here the narrower objective is choosing the immediate operational response in phishing attachment, best addressed by quarantine the campaign, invalidate exposed sessions and warn affected users.
Question 390
A malicious comment causes the same script to execute for multiple viewers. Which observation most directly identifies the concern that needs investigation?
- A deceptive message redirects recipients to an attacker-controlled login page
- A state-changing request carries an existing session without verified user intent
- Untrusted input changes the structure of an application SQL statement
- Stored user content is rendered as active browser script for later visitors
- Mass reads of sensitive records deviate from assigned job activities
Explanation
Correct Answer
D:Persistent XSS differs from a reflection visible only in the initiating request. The follow-up evidence is submitted payload, storage record and browser execution trace with CSP reports, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
A:This relates to phishing attachment: credential harvesting relies on social persuasion and a misleading authentication surface; the stored cross-site scripting question instead requires recognizing the distinguishing signal, specifically stored user content is rendered as active browser script for later visitors.
B:CSRF abuses the browser's authenticated context rather than stealing the password directly; prioritizing that cross-site request forgery mechanism would leave this stored cross-site scripting decision unresolved because stored user content is rendered as active browser script for later visitors is the direct fit.
C:For SQL injection, injection exploits unsafe query construction rather than merely malformed HTTP headers; here the narrower objective is recognizing the distinguishing signal in stored cross-site scripting, best addressed by stored user content is rendered as active browser script for later visitors.
E:Potential exfiltration must be judged using permissions, business justification and timing; applied to this stored cross-site scripting case, it addresses insider bulk export instead of the required step: stored user content is rendered as active browser script for later visitors.