Question 250
One public IP attempts thousands of distinct usernames with a small set of passwords against a customer portal. Which artifact provides the strongest corroborating detail?
- Web request bodies and database error telemetry
- Name-resolution captures with responder source addresses
- Resolver query names and response-size chronology
- Identity sign-in failure reasons and source clustering
Explanation
Correct Answer
D:For corroboration in Credential stuffing on web login, distinct account counts and password attempt patterns expose broad reuse testing; this applies to the reported “One public IP attempts thousands of distinct usernames with a small set of passwords against a customer portal”.
Incorrect Answers
A:For corroboration in Credential stuffing on web login, SQL injection probing is a different mechanism: paired request and error records connect suspect input to query execution changes; here, distinct account counts and password attempt patterns expose broad reuse testing.
B:The choice is relevant to LLMNR or NBNS name-resolution poisoning, where the request and first matching response reveal whether an unofficial peer supplied the address; for corroboration in Credential stuffing on web login, distinct account counts and password attempt patterns expose broad reuse testing.
C:For corroboration in Credential stuffing on web login, DNS tunneling over queries is a different mechanism: full question names and timing reveal payload-like labels and repetitive transactions; here, distinct account counts and password attempt patterns expose broad reuse testing.
Question 251
A rule flags every nightly large file copy from backup servers because it uses the workstation transfer baseline. What evidence should be obtained to validate the suspected mechanism?
- Raw event timestamps and rule aggregation window settings
- Shared host identity and chronological events across sensors
- Asset role labels alongside historical transfer distributions
- Rule diff, parser schema and last-successful test results
Explanation
Correct Answer
C:In the Peer-group baseline mismatch case, separating backup servers from office endpoints exposes why the baseline is distorted; the observation “A rule flags every nightly large file copy from backup servers because it uses the workstation transfer baseline” makes this corroboration choice the fitting one.
Incorrect Answers
A:This option addresses Sliding-window aggregation error because the data reveals whether a cluster was split across reporting boundaries; the Peer-group baseline mismatch corroboration question instead turns on the fact that separating backup servers from office endpoints exposes why the baseline is distorted.
B:That option fits Multi-stage attack sequence correlation since stable entity joins and event time establish whether signals form one progression; it does not fit the Peer-group baseline mismatch corroboration scenario, where separating backup servers from office endpoints exposes why the baseline is distorted.
D:That option fits Detection-as-code regression since changes and prior outcomes pinpoint the regression rather than assuming attacks ceased; it does not fit the Peer-group baseline mismatch corroboration scenario, where separating backup servers from office endpoints exposes why the baseline is distorted.
Question 252
A laptop requests an unknown internal hostname and receives a rapid responder answer from an unexpected workstation. Which working hypothesis is best supported by these facts?
- Responder-based local name spoofing
- Persistent browser script injection
- DNS data tunneling behavior
- Cross-origin authenticated request abuse
Explanation
Correct Answer
A:The LLMNR or NBNS name-resolution poisoning evidence “A laptop requests an unknown internal hostname and receives a rapid responder answer from an unexpected workstation” is decisive for classification because broadcast or multicast fallback resolution permits an untrusted peer to claim an unresolved name.
Incorrect Answers
B:For classification in LLMNR or NBNS name-resolution poisoning, Stored cross-site scripting is a different mechanism: unsanitized content stored server-side can run in the viewing user's browser context; here, broadcast or multicast fallback resolution permits an untrusted peer to claim an unresolved name.
C:The choice is relevant to DNS tunneling over queries, where high-entropy subdomains can carry encoded payload fragments through permitted DNS resolution; for classification in LLMNR or NBNS name-resolution poisoning, broadcast or multicast fallback resolution permits an untrusted peer to claim an unresolved name.
D:For classification in LLMNR or NBNS name-resolution poisoning, Cross-site request forgery is a different mechanism: the browser may attach existing session credentials to an unwanted request unless defenses reject it; here, broadcast or multicast fallback resolution permits an untrusted peer to claim an unresolved name.
Question 253
A production connection string containing a database secret is found in a publicly served configuration file. The analyst has not yet established malicious intent or downstream impact. Which limitation should shape how the analyst interprets this evidence?
- An HTTPS connection does not prove a webhook came from its vendor
- Filtering obvious SQL keywords alone is an incomplete fix
- A clean vulnerability scan does not prove the host is no longer compromised
- Rate limiting alone cannot correct broken object-level authorization
- Removing the public file alone does not make the old password safe
Explanation
Correct Answer
E:For interpretation limit in Leaked application database password, anyone who copied the string can still attempt authentication until rotation; this applies to the reported “A production connection string containing a database secret is found in a publicly served configuration file”.
Incorrect Answers
A:For the alternative Compromised webhook endpoint situation, TLS protects the channel but does not inherently validate application-level payload authorization; by contrast, for Leaked application database password interpretation limit, anyone who copied the string can still attempt authentication until rotation.
B:In Confirmed SQL injection data exposure, input can be encoded or reformulated, while prepared statements preserve query structure; the reported Leaked application database password case calls for a different interpretation limit conclusion because anyone who copied the string can still attempt authentication until rotation.
C:For the alternative Web-shell persistence after patching situation, patch status and attacker artifact removal are separate requirements; by contrast, for Leaked application database password interpretation limit, anyone who copied the string can still attempt authentication until rotation.
D:In Automated scraping of protected records, a slow attacker may still access records belonging to other users; the reported Leaked application database password case calls for a different interpretation limit conclusion because anyone who copied the string can still attempt authentication until rotation.
Question 254
An employee endpoint creates a new service on a peer after an unusual network logon from that workstation. Which investigative step would most directly establish the relevant scope?
- Correlate user diversity, source reuse and any successful sign-ins
- Build a parent-to-child host movement timeline
- Review token use and mailbox access by the granted app
- Compare the requesting user with normal application-to-service usage
Explanation
Correct Answer
B:Correlating source account, remote host and service creation reconstructs traversal; this is the relevant scope analysis mechanism for Lateral movement via remote service given “An employee endpoint creates a new service on a peer after an unusual network logon from that workstation”.
Incorrect Answers
A:The choice is relevant to Password spraying across employees, where successes following the wave require immediate scoping of accessed services; for scope analysis in Lateral movement via remote service, correlating source account, remote host and service creation reconstructs traversal.
C:The choice is relevant to OAuth consent phishing, where scope assessment determines whether consent led to actual data retrieval; for scope analysis in Lateral movement via remote service, correlating source account, remote host and service creation reconstructs traversal.
D:For scope analysis in Lateral movement via remote service, Kerberoasting service-ticket harvesting is a different mechanism: unexpected breadth of SPNs and encryption types can suggest ticket harvesting; here, correlating source account, remote host and service creation reconstructs traversal.
Question 255
A user workstation requests many Kerberos service tickets for unusually privileged service principals. Which artifact provides the strongest corroborating detail?
- Version-control export audit and HR-approved access scope
- EDR file-change bursts and destructive process command lines
- Identity consent audit showing app ID and granted scopes
- Domain-controller 4769 events with service principal names
Explanation
Correct Answer
D:For corroboration in Kerberoasting service-ticket harvesting, ticket request patterns identify service accounts and the requester, subject to configured auditing; this applies to the reported “A user workstation requests many Kerberos service tickets for unusually privileged service principals”.
Incorrect Answers
A:For the alternative Insider bulk source-code copying situation, repository actions combined with business entitlement clarify whether the activity was authorized; by contrast, for Kerberoasting service-ticket harvesting corroboration, ticket request patterns identify service accounts and the requester, subject to configured auditing.
B:In Ransomware file encryption, linking file operations to processes distinguishes active encryption from normal bulk edits; the reported Kerberoasting service-ticket harvesting case calls for a different corroboration conclusion because ticket request patterns identify service accounts and the requester, subject to configured auditing.
C:For the alternative OAuth consent phishing situation, tenant logs reveal which application obtained permissions and who authorized it; by contrast, for Kerberoasting service-ticket harvesting corroboration, ticket request patterns identify service accounts and the requester, subject to configured auditing.
Question 256
An external monitoring provider forwards high-severity notices but cannot explain who is permitted to isolate a customer workstation. The finding has been corroborated and the response team has authorization to act. Which response is the most appropriate at this point?
- Introduce an on-call rotation with named escalation owners
- Define a joint response RACI and approval procedure
- Require structured handoff fields and acknowledgement
- Adopt common triage taxonomy and a shared escalation path
Explanation
Correct Answer
B:The Managed SOC provider accountability evidence “An external monitoring provider forwards high-severity notices but cannot explain who is permitted to isolate a customer workstation” is decisive for response decision because explicit responsibility and authorization prevent a critical event from stalling at a contractual boundary.
Incorrect Answers
A:That option fits In-house SOC staffing since a staffed or on-call responder closes the accountability gap without changing the detection technology itself; it does not fit the Managed SOC provider accountability response decision scenario, where explicit responsibility and authorization prevent a critical event from stalling at a contractual boundary.
C:That option fits Follow-the-sun SOC transfer since the receiving region should accept ownership with a clear next action before the outgoing team disengages; it does not fit the Managed SOC provider accountability response decision scenario, where explicit responsibility and authorization prevent a critical event from stalling at a contractual boundary.
D:This option addresses Virtual SOC tool integration because a standardized workflow lets decentralized analysts coordinate without relocating staff; the Managed SOC provider accountability response decision question instead turns on the fact that explicit responsibility and authorization prevent a critical event from stalling at a contractual boundary.
Question 257
The same weak password is tried once against hundreds of corporate users over a short window. What follow-up analysis most effectively distinguishes this case?
- Trace hash and message recipients across the fleet
- Compare downloads with job duties and approved migration tasks
- Correlate user diversity, source reuse and any successful sign-ins
- Identify first affected host and shared-volume write scope
Explanation
Correct Answer
C:For scope analysis in Password spraying across employees, successes following the wave require immediate scoping of accessed services; this applies to the reported “The same weak password is tried once against hundreds of corporate users over a short window”.
Incorrect Answers
A:For scope analysis in Password spraying across employees, Malicious Office macro delivery is a different mechanism: cross-recipient scoping shows whether the same attachment reached other users; here, successes following the wave require immediate scoping of accessed services.
B:The choice is relevant to Insider bulk source-code copying, where context is needed to distinguish theft from scheduled knowledge transfer; for scope analysis in Password spraying across employees, successes following the wave require immediate scoping of accessed services.
D:The choice is relevant to Ransomware file encryption, where filesystem and network-share telemetry locate where propagation or data impact began; for scope analysis in Password spraying across employees, successes following the wave require immediate scoping of accessed services.
Question 258
Two analysts handling the same suspected phishing event take incompatible containment steps because the playbook says only investigate. What monitoring improvement would best help detect recurrence?
- Review playbook exceptions after each exercise
- Audit priority overrides and their outcomes
- Require provenance fields before incident handoff
- Track rule precision alongside detection latency
Explanation
Correct Answer
A:The SOC runbook decision ambiguity evidence “Two analysts handling the same suspected phishing event take incompatible containment steps because the playbook says only investigate” is decisive for ongoing detection improvement because exceptions reveal conditions omitted from the published procedure.
Incorrect Answers
B:In Alert severity versus priority, comparing escalations with true incidents helps tune risk scoring and avoid overuse; the reported SOC runbook decision ambiguity case calls for a different ongoing detection improvement conclusion because exceptions reveal conditions omitted from the published procedure.
C:For the alternative SOC case evidence preservation situation, structured completeness checks reduce repeated requests for missing evidence; by contrast, for SOC runbook decision ambiguity ongoing detection improvement, exceptions reveal conditions omitted from the published procedure.
D:In SOC detection quality governance, reducing volume is useful only if true-event sensitivity remains acceptable; the reported SOC runbook decision ambiguity case calls for a different ongoing detection improvement conclusion because exceptions reveal conditions omitted from the published procedure.
Question 259
An investigation finds possible customer-data disclosure, but the SOC cannot determine the applicable reporting deadlines. Which investigative step would most directly establish the relevant scope?
- Separate established observations from hypotheses and pending checks
- Verify the received image digest against the acquisition record
- Consult legal and privacy teams using verified scope and discovery time
- Review dependency and sequencing of proposed containment steps
Explanation
Correct Answer
C:The External regulatory notification decision evidence “An investigation finds possible customer-data disclosure, but the SOC cannot determine the applicable reporting deadlines” is decisive for scope analysis because timing triggers and evidence thresholds can differ between obligations.
Incorrect Answers
A:In Public incident communications control, an uncertainty-aware briefing avoids exaggerating or minimizing impact; the reported External regulatory notification decision case calls for a different scope analysis conclusion because timing triggers and evidence thresholds can differ between obligations.
B:For the alternative Evidence transfer between response teams situation, matching hashes support bitwise consistency across the transfer; by contrast, for External regulatory notification decision scope analysis, timing triggers and evidence thresholds can differ between obligations.
D:For the alternative Incident commander coordination gap situation, some operations must precede others to preserve access and business continuity; by contrast, for External regulatory notification decision scope analysis, timing triggers and evidence thresholds can differ between obligations.
Question 260
A security team receives an AWS finding for unusual API activity suggestive of compromised access keys. Which interpretive boundary is most relevant to this situation?
- Security Hub is not a substitute for raw CloudTrail event history
- Microsoft Sentinel does not automatically ingest every Azure log category
- An Azure resource existing in a subscription does not guarantee its detailed logs are in Sentinel
- A GuardDuty finding is a lead, not a complete forensic record
Explanation
Correct Answer
D:Investigation still requires original service logs and corroboration; this is the relevant interpretation limit mechanism for AWS GuardDuty threat finding given “A security team receives an AWS finding for unusual API activity suggestive of compromised access keys”.
Incorrect Answers
A:For interpretation limit in AWS GuardDuty threat finding, AWS Security Hub finding consolidation is a different mechanism: findings summarize detections while detailed API reconstruction uses source logs; here, investigation still requires original service logs and corroboration.
B:The choice is relevant to Microsoft Sentinel analytic rule, where connectors and diagnostic settings must supply the intended source events; for interpretation limit in AWS GuardDuty threat finding, investigation still requires original service logs and corroboration.
C:For interpretation limit in AWS GuardDuty threat finding, Azure Monitor diagnostic data routing is a different mechanism: source configuration and connector scope control availability; here, investigation still requires original service logs and corroboration.