Question 570
The working hypothesis concerns distributed denial of service. The initial finding is: A multi-origin traffic surge exhausts service or upstream capacity. Which evidence should investigators prioritize?
- Recursive DNS query logs tied to endpoint process and byte volume
- NetFlow or firewall connection tuples with source, destination and port
- File I/O telemetry, process tree and remote share access logs
- Edge request rates, provider flow counters and backend saturation metrics
- Destination-port distribution in firewall sessions or packet capture
Explanation
Correct Answer
D:Combining network volume and application capacity identifies where exhaustion occurs. This is particularly useful after the initial sign of a multi-origin traffic surge exhausts service or upstream capacity; 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; that is suited to investigating DNS tunneling, whereas the distributed denial of service case requires edge request rates, provider flow counters and backend saturation metrics for independently corroborating the suspected behavior.
B:This relates to horizontal port scan: distinct-destination cardinality is needed to classify the sweep accurately; the distributed denial of service question instead requires independently corroborating the suspected behavior, specifically edge request rates, provider flow counters and backend saturation metrics.
C:This relates to ransomware encryption: process attribution and scope identify whether encryption is local or propagated; the distributed denial of service question instead requires independently corroborating the suspected behavior, specifically edge request rates, provider flow counters and backend saturation metrics.
E:Protocol and host tuples distinguish probing from ordinary multi-service application traffic; applied to this distributed denial of service case, it addresses vertical port scan instead of the required step: edge request rates, provider flow counters and backend saturation metrics.
Question 571
A multi-cloud SOC wants authoritative administrative audit coverage for Azure, AWS and Google Cloud. Which THREE log families belong in the initial control-plane collection plan? Choose THREE.
- Only endpoint antivirus detections from administrator laptops
- Google Cloud Audit Logs for administrative actions on GCP resources
- Only cloud billing records aggregated into monthly totals
- Only HTTP access logs from the organization's public website
- AWS CloudTrail management events for AWS API administration
- Azure Activity Log events for Azure resource management changes
Explanation
Correct Answers
B:Cloud Audit Logs record auditable administrative activity for relevant Google Cloud services. Collection scope and retention must be verified.
E:CloudTrail provides event names, principals and request context for AWS control-plane actions. Correct organization and region scope matters.
F:Activity Log captures management-plane operations and caller context in Azure. Guest OS logs are a separate additional source.
Incorrect Answers
A:Endpoint security evidence cannot replace managed cloud service API audit trails. Administrative changes may occur through many clients and automation identities.
C:Billing reports may indicate usage but lack actor-level administrative event detail. Incident attribution requires security audit logs.
D:Web request logs do not inherently record management changes across three cloud providers. They cover a different data plane.
Question 572
An alert suggests behavioral baselines. The recorded clue is: The account has a stable workload pattern that differs from enterprise averages. What evidence would best test this hypothesis?
- Sigma selectors, logsource categories and target schema field mapping
- Per-role historical execution rates, signed binaries and change records
- Search job runtime, scanned byte count and result cardinality
- Real ingestion schema, known-positive events and adversarial negative examples
Explanation
Correct Answer
B:Relevant peer groups are more informative than all-user averages. The result can be compared with the account has a stable workload pattern that differs from enterprise averages to verify that the suspected mechanism is actually present.
Incorrect Answers
A:Transportable syntax alone does not guarantee equivalent logs across platforms, which would be relevant to sigma rule portability, but not the behavioral baselines scenario that requires per-role historical execution rates, signed binaries and change records.
C:The alternative concerns analytic query cost: performance data identifies whether the rule is computationally sustainable; however, the described behavioral baselines situation calls for per-role historical execution rates, signed binaries and change records.
D:Field validation and test data reveal hallucinated query behavior; applied to this behavioral baselines case, it addresses AI-generated SIEM logic instead of the required step: per-role historical execution rates, signed binaries and change records.
Question 573
A new AWS IAM policy grants broad privileges through an unexpected API request. The team takes this action: Preserve trails and investigate or revert the unauthorized IAM modification. Which check most directly verifies the intended outcome?
- Malicious communication stops and the finding is dispositioned with supporting evidence
- Sample findings from all in-scope accounts are visible to authorized analysts
- A test IAM edit is recorded and only approved permission state remains
- A known suspicious sign-in produces an incident with correct user and IP entities
Explanation
Correct Answer
C:An intact console page is not audit assurance. It documents the result of this response step—Preserve trails and investigate or revert the unauthorized IAM modification—and helps determine whether the protective state persists.
Incorrect Answers
A:This relates to GuardDuty compromise finding: a finding's disappearance alone is not a restoration test; the CloudTrail administrative audit question instead requires demonstrating that the remediation or control took effect, specifically a test IAM edit is recorded and only approved permission state remains.
B:A dashboard showing only one account could mask gaps; applied to this CloudTrail administrative audit case, it addresses AWS Security Hub aggregation instead of the required step: a test IAM edit is recorded and only approved permission state remains.
D:Testing ingestion alone does not validate incident generation; this evidence or action is associated with Microsoft Sentinel analytic, whereas the case concerns CloudTrail administrative audit and calls for a test IAM edit is recorded and only approved permission state remains.
Question 574
An attacker adds a new authenticator method to a victim account soon after a strange login. Which finding best distinguishes this activity from a routine operational change?
- Unexpected enrollment gives an attacker a durable authentication factor
- A nonhuman credential is exposed with permissions to alter cloud resources
- Successful attacker session follows known credential disclosure
- Evidence suggests both encryption and possible data theft
Explanation
Correct Answer
A:Password resets alone may not remove newly registered MFA methods. Investigators should still corroborate it with identity audit of method registration, source and preceding sessions before assigning definitive scope or attribution.
Incorrect Answers
B:Service principals have independent secrets and tokens outside human password resets; that is suited to investigating service principal exposure, whereas the suspicious MFA enrollment case requires unexpected enrollment gives an attacker a durable authentication factor for recognizing the distinguishing signal.
C:This relates to stolen user password: password theft can create active sessions and refresh tokens beyond the original login; the suspicious MFA enrollment question instead requires recognizing the distinguishing signal, specifically unexpected enrollment gives an attacker a durable authentication factor.
D:Data-loss assessment and recovery are separate parallel response tracks; this evidence or action is associated with double extortion, whereas the case concerns suspicious MFA enrollment and calls for unexpected enrollment gives an attacker a durable authentication factor.
Question 575
A responder investigating chain of custody has corroborated this finding: Custody changes without signatures weaken evidence accountability. What action belongs next in the approved workflow?
- Capture memory with approved methods before shutting down when safe
- Preserve the original MIME message and examine headers and URLs safely
- Seal and label the device and document each authorized transfer
- Create and verify a forensic image using controlled read-only acquisition
Explanation
Correct Answer
C:An unlabeled device handed across desks invites mix-ups and challenge. For safe case progression, preserve the evidence and later verify every transfer is traceable from seizure through laboratory receipt.
Incorrect Answers
A:Prioritization must consider safety and continued attacker access; applied to this chain of custody case, it addresses memory capture order instead of the required step: seal and label the device and document each authorized transfer.
B:Clicking the link from an analyst workstation could trigger credential theft or tracking; prioritizing that email artifact examination mechanism would leave this chain of custody decision unresolved because seal and label the device and document each authorized transfer is the direct fit.
D:This relates to disk forensic imaging: ordinary file copying can omit deleted data and filesystem structures; the chain of custody question instead requires choosing the immediate operational response, specifically seal and label the device and document each authorized transfer.
Question 576
Responders addressed triage versus investigation using this measure: Triage for impact and escalate the confirmed session for deeper investigation. What should the SOC test before considering closure?
- One active incident record with clear owners for each dependent action
- Disposition labels backed by recorded evidence and follow-up ownership
- Measured detection-to-containment time decreases in controlled exercises
- A shorter detection interval on replayed equivalent attack scenarios
- An acknowledged handoff with a named owner and response deadline
Explanation
Correct Answer
B:A closed alert without its reasoning and escalation record cannot be reliably reviewed. The measure should be evaluated against the actual action, triage for impact and escalate the confirmed session for deeper investigation, rather than against ticket status.
Incorrect Answers
A:Closure requires checking task responsibility, not simply reducing duplicate ticket counts; applied to this triage versus investigation case, it addresses incident ownership instead of the required step: disposition labels backed by recorded evidence and follow-up ownership.
C:The metric must follow actual enforcement, not merely ticket creation or chat acknowledgment, which would be relevant to mean time to respond, but not the triage versus investigation scenario that requires disposition labels backed by recorded evidence and follow-up ownership.
D:For mean time to detect, MTTD improvement should be demonstrated on representative behavior and comparable measurements; here the narrower objective is demonstrating that the remediation or control took effect in triage versus investigation, best addressed by disposition labels backed by recorded evidence and follow-up ownership.
E:A ticket alone is not proof that the receiving team accepted time-sensitive responsibility; prioritizing that tier-one escalation mechanism would leave this triage versus investigation decision unresolved because disposition labels backed by recorded evidence and follow-up ownership is the direct fit.
Question 577
Responders suspect service-based execution based on this observation: Short-lived service registration executes an unfamiliar command on a remote host. Which artifact should be examined first?
- Process command line, remote destination and downloaded-file reputation
- WMI activity logs, process creation and authenticated source identity
- EDR process tree, command-line parameters and document provenance
- Service Control Manager events, service binary path and remote logon evidence
Explanation
Correct Answer
D:Temporal sequence identifies who created and started the service. This is particularly useful after the initial sign of short-lived service registration executes an unfamiliar command on a remote host; the two forms of evidence test different parts of the case.
Incorrect Answers
A:Behavior and provenance matter more than whether the launcher is Microsoft signed; applied to this service-based execution case, it addresses living-off-the-land binaries instead of the required step: service Control Manager events, service binary path and remote logon evidence.
B:The alternative concerns WMI remote execution: cross-host correlation establishes both initiation and executed payload; however, the described service-based execution situation calls for service Control Manager events, service binary path and remote logon evidence.
C:The parent executable and launch arguments identify macro-mediated execution; prioritizing that office child process mechanism would leave this service-based execution decision unresolved because service Control Manager events, service binary path and remote logon evidence is the direct fit.
Question 578
A Tier 1 analyst receives a high-confidence endpoint alert involving a payment system. Which THREE facts most directly support severity and escalation decisions? Choose THREE.
- The affected asset's business criticality and current service exposure
- The total number of unrelated low-priority alerts across the SOC queue
- The product's default severity rating used without local asset context
- The historical false-positive rate of unrelated endpoint alert rules
- The incident's apparent scope and whether attacker access remains active
- A timeline of corroborating endpoint, identity and network evidence
Explanation
Correct Answers
A:The same technical event can have very different consequences on a payment system and a disposable lab machine. Impact drives priority.
E:Ongoing access and multiple impacted hosts increase urgency and influence containment decisions. Scope must be evidence based.
F:Related telemetry helps distinguish an isolated alert from an active compromise. It also lets responders reproduce the conclusion.
Incorrect Answers
B:Aggregate queue volume may determine staffing and prioritization logistics, but it does not establish the payment system's compromise severity. Evaluate the affected asset, confirmed evidence and attacker activity instead.
C:Generic product severity is a starting signal, not an assessment of this payment service's exposure, business criticality or validated attacker scope. It should not replace case-specific evidence.
D:Noise statistics for other analytic rules do not measure whether this particular high-confidence payment system incident has business impact or active attacker control. Establish current asset context and corroborated scope.
Question 579
Partner teams exchange threat intelligence using incompatible proprietary spreadsheets. Which finding best distinguishes this activity from a routine operational change?
- Source-imposed sharing constraints restrict onward dissemination
- Threat objects lack standardized relationships and machine-readable semantics
- A recurring exchange needs an API transport rather than manual document copies
- Technique-oriented mapping captures behavior independent of product label
Explanation
Correct Answer
B:STIX represents indicators, malware, relationships and associated context. Confirmation should then examine shared objects' types, relationships and version identifiers; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
A:The alternative concerns TLP handling: traffic Light Protocol markings communicate how intelligence may be shared; however, the described STIX structured sharing situation calls for threat objects lack standardized relationships and machine-readable semantics.
C:This relates to TAXII feed transport: TAXII defines exchange services for threat intelligence and commonly carries STIX content; the STIX structured sharing question instead requires recognizing the distinguishing signal, specifically threat objects lack standardized relationships and machine-readable semantics.
D:ATT&CK techniques describe adversary actions and support detection-gap analysis; that is suited to investigating MITRE ATTACK hunt map, whereas the STIX structured sharing case requires threat objects lack standardized relationships and machine-readable semantics for recognizing the distinguishing signal.
Question 580
To verify remediation of horizontal port scan, the team reports taking this action: Investigate the source and suppress unauthorized scanning at the edge. Which outcome should the analyst demand?
- Legitimate user success rates and backend capacity return to baseline
- The sweep stops and the source is confirmed unauthorized or approved
- Unapproved connection attempts cease and network telemetry confirms containment
- Clients resolve the real gateway MAC and no further spoofed ARP appears
Explanation
Correct Answer
B:A drop in alerts without source attribution could hide continuing reconnaissance. That verification specifically tests whether the intervention to investigate the source and suppress unauthorized scanning at the edge corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:The alternative concerns distributed denial of service: traffic reduction is insufficient if real users still cannot complete transactions; however, the described horizontal port scan situation calls for the sweep stops and the source is confirmed unauthorized or approved.
C:A dashboard alert count alone cannot validate that all probes stopped; prioritizing that vertical port scan mechanism would leave this horizontal port scan decision unresolved because the sweep stops and the source is confirmed unauthorized or approved is the direct fit.
D:This relates to ARP cache poisoning: a successful web refresh without ARP validation does not prove that interception ended; the horizontal port scan question instead requires demonstrating that the remediation or control took effect, specifically the sweep stops and the source is confirmed unauthorized or approved.