Question 1010
Several hosts suddenly associate the default gateway IP with a different MAC address after gratuitous ARP traffic. Which artifact provides the strongest corroborating detail?
- Resolver query names and response-size chronology
- Switch ARP inspection events and host ARP tables
- Stored comment payload and affected page response source
- Application POST audit and CSRF validation outcomes
Explanation
Correct Answer
B:MAC-to-IP changes across peers corroborate neighbor cache poisoning; this is the relevant corroboration mechanism for ARP spoofing on local subnet given “Several hosts suddenly associate the default gateway IP with a different MAC address after gratuitous ARP traffic”.
Incorrect Answers
A:That option fits DNS tunneling over queries since full question names and timing reveal payload-like labels and repetitive transactions; it does not fit the ARP spoofing on local subnet corroboration scenario, where MAC-to-IP changes across peers corroborate neighbor cache poisoning.
C:That option fits Stored cross-site scripting since examining rendered output shows whether untrusted content is inserted into executable markup; it does not fit the ARP spoofing on local subnet corroboration scenario, where MAC-to-IP changes across peers corroborate neighbor cache poisoning.
D:This option addresses Cross-site request forgery because request metadata reveals whether a sensitive action lacked a valid per-session request token; the ARP spoofing on local subnet corroboration question instead turns on the fact that MAC-to-IP changes across peers corroborate neighbor cache poisoning.
Question 1011
A SIEM rule deployment removes a required host field and the rule stops producing matches after a parser update. The analyst has not yet established malicious intent or downstream impact. What qualification is most important before drawing a firm conclusion?
- Three alerts on one asset are not necessarily one attack
- An anomaly score is relative to the chosen baseline
- A threshold is meaningful only with its window semantics
- A syntactically valid SIEM query may still match nothing
Explanation
Correct Answer
D:For interpretation limit in Detection-as-code regression, correct parser fields and event semantics are necessary beyond syntax checks; this applies to the reported “A SIEM rule deployment removes a required host field and the rule stops producing matches after a parser update”.
Incorrect Answers
A:This option addresses Multi-stage attack sequence correlation because a causal interpretation requires timing, context and compatible process or session evidence; the Detection-as-code regression interpretation limit question instead turns on the fact that correct parser fields and event semantics are necessary beyond syntax checks.
B:That option fits Peer-group baseline mismatch since a high score may describe a normal job in the wrong comparison cohort; it does not fit the Detection-as-code regression interpretation limit scenario, where correct parser fields and event semantics are necessary beyond syntax checks.
C:This option addresses Sliding-window aggregation error because the same event rate can trigger or evade depending on aggregation design; the Detection-as-code regression interpretation limit question instead turns on the fact that correct parser fields and event semantics are necessary beyond syntax checks.
Question 1012
An external threat feed description includes instructions telling a summarization assistant to delete the security case. What qualification is most important before drawing a firm conclusion?
- An external IoC description cannot authorize incident closure
- Being a security investigation does not waive privacy obligations
- A quiet anomaly model is not proof the environment is safer
- Speed is not the only automation quality criterion
Explanation
Correct Answer
A:The Prompt injection in threat enrichment evidence “An external threat feed description includes instructions telling a summarization assistant to delete the security case” is decisive for interpretation limit because data provenance and control authority must remain separate.
Incorrect Answers
B:For the alternative Sensitive data entered into AI copilot situation, response urgency does not automatically authorize external sharing of raw personal data; by contrast, for Prompt injection in threat enrichment interpretation limit, data provenance and control authority must remain separate.
C:In AI alert score drift, new traffic distributions can invalidate scoring assumptions silently; the reported Prompt injection in threat enrichment case calls for a different interpretation limit conclusion because data provenance and control authority must remain separate.
D:For the alternative Automated response approval boundary situation, a response executed instantly can be harmful if its underlying classification is wrong; by contrast, for Prompt injection in threat enrichment interpretation limit, data provenance and control authority must remain separate.
Question 1013
Security staff discover that a token-signing key may have been extracted from an identity federation service. Which scoping query or comparison best tests the working hypothesis?
- Enumerate signing keys, token audiences and affected trust relationships
- Enumerate sessions, tokens, changes and accessed sensitive apps
- Enumerate API calls and accessible resources using the key
- Confirm the principal independently and review subsequent access
Explanation
Correct Answer
A:For scope analysis in Compromised federation signing key, response scope extends across services that rely on the compromised certificate; this applies to the reported “Security staff discover that a token-signing key may have been extracted from an identity federation service”.
Incorrect Answers
B:The choice is relevant to Employee account takeover, where scope includes persistence such as new authenticators or OAuth grants; for scope analysis in Compromised federation signing key, response scope extends across services that rely on the compromised certificate.
C:For scope analysis in Compromised federation signing key, Exposed cloud API credential is a different mechanism: permission scope and observed operations determine potential impact; here, response scope extends across services that rely on the compromised certificate.
D:The choice is relevant to Unauthorized MFA factor registration, where the attacker may have gained access before suspicious enrollment was flagged; for scope analysis in Compromised federation signing key, response scope extends across services that rely on the compromised certificate.
Question 1014
A file server shows 4624 logon type 3 for an account during access to a shared folder. What evidence should be obtained to validate the suspected mechanism?
- 4688 new-process and creator-process fields
- 4624 event with logon type and source network address
- 4720 subject and new target-account identity fields
- 4672 subject logon ID aligned with event 4624
- Security event fields for 4625 including status and source address
Explanation
Correct Answer
B:In the Windows network logon type case, the destination host records how the authenticated session was established; the observation “A file server shows 4624 logon type 3 for an account during access to a shared folder” makes this corroboration choice the fitting one.
Incorrect Answers
A:In Windows process creation auditing, the linked process details help attribute unexpected interpreter execution to its parent; the reported Windows network logon type case calls for a different corroboration conclusion because the destination host records how the authenticated session was established.
C:In Windows new account creation, the initiating principal and target name help attribute account creation; the reported Windows network logon type case calls for a different corroboration conclusion because the destination host records how the authenticated session was established.
D:For the alternative Windows privileged logon indicator situation, shared logon identifiers provide an account and logon-type context for privileged sessions; by contrast, for Windows network logon type corroboration, the destination host records how the authenticated session was established.
E:In Windows 4625 authentication failures, failure status and logon type distinguish bad credentials from blocked logon rights; the reported Windows network logon type case calls for a different corroboration conclusion because the destination host records how the authenticated session was established.
Question 1015
A domain-joined server records repeated 4625 failures from one remote address before the help desk receives a login complaint. The analyst has not yet established malicious intent or downstream impact. Which caveat most directly affects assessment of the evidence?
- New account creation is an administrative event, not automatic compromise
- A 4672 record is common for privileged system activity
- Command-line details may be absent unless auditing is configured
- A failure event does not prove the attempted password was valid
Explanation
Correct Answer
D:Some status codes identify nonexistent accounts or policy restrictions rather than successful credential knowledge; this is the relevant interpretation limit mechanism for Windows 4625 authentication failures given “A domain-joined server records repeated 4625 failures from one remote address before the help desk receives a login complaint”.
Incorrect Answers
A:For the alternative Windows new account creation situation, provisioning systems legitimately create accounts and require context; by contrast, for Windows 4625 authentication failures interpretation limit, some status codes identify nonexistent accounts or policy restrictions rather than successful credential knowledge.
B:In Windows privileged logon indicator, its presence alone cannot establish attacker-controlled administrator access; the reported Windows 4625 authentication failures case calls for a different interpretation limit conclusion because some status codes identify nonexistent accounts or policy restrictions rather than successful credential knowledge.
C:For the alternative Windows process creation auditing situation, a 4688 record alone need not contain complete argument text; by contrast, for Windows 4625 authentication failures interpretation limit, some status codes identify nonexistent accounts or policy restrictions rather than successful credential knowledge.
Question 1016
Internal staff triage identity alarms while an external team manages network alerts; incidents crossing both queues repeatedly lose context. What follow-up analysis most effectively distinguishes this case?
- Trace a sample escalation through provider and customer roles
- Follow one linked identity-network alert from intake to closure
- Compare overnight alert backlog with staffing rosters
- Audit outstanding cases at regional shift boundaries
Explanation
Correct Answer
B:Given “Internal staff triage identity alarms while an external team manages network alerts; incidents crossing both queues repeatedly lose context”, a complete timeline exposes which team failed to preserve evidence or assign a decision maker; that best addresses scope analysis in Co-managed SOC handoff.
Incorrect Answers
A:The choice is relevant to Managed SOC provider accountability, where reconstructing an actual handoff identifies the decision owner and missing authorization point; for scope analysis in Co-managed SOC handoff, a complete timeline exposes which team failed to preserve evidence or assign a decision maker.
C:The choice is relevant to In-house SOC staffing, where aligning coverage windows with actual response delays distinguishes scheduling gaps from detection failures; for scope analysis in Co-managed SOC handoff, a complete timeline exposes which team failed to preserve evidence or assign a decision maker.
D:For scope analysis in Co-managed SOC handoff, Follow-the-sun SOC transfer is a different mechanism: comparing end-of-shift and start-of-shift records identifies lost context during transfer; here, a complete timeline exposes which team failed to preserve evidence or assign a decision maker.
Question 1017
Event 4672 appears near a privileged service start and the analyst assumes it proves credential theft. What security condition most directly explains the pattern?
- Windows audit-log clearance
- Windows special-privilege assignment audit
- Failed Windows logon audit evidence
- Windows account-provisioning event
Explanation
Correct Answer
B:For classification in Windows privileged logon indicator, event 4672 notes a new logon assigned sensitive privileges and needs correlation with its session; this applies to the reported “Event 4672 appears near a privileged service start and the analyst assumes it proves credential theft”.
Incorrect Answers
A:For classification in Windows privileged logon indicator, Windows security log clearing is a different mechanism: event 1102 indicates the Security audit log was cleared on that system; here, event 4672 notes a new logon assigned sensitive privileges and needs correlation with its session.
C:For classification in Windows privileged logon indicator, Windows 4625 authentication failures is a different mechanism: event 4625 represents an unsuccessful logon with reason and attempted account context on the audited host; here, event 4672 notes a new logon assigned sensitive privileges and needs correlation with its session.
D:The choice is relevant to Windows new account creation, where event 4720 can signal a user account being created when relevant audit policy is active; for classification in Windows privileged logon indicator, event 4672 notes a new logon assigned sensitive privileges and needs correlation with its session.
Question 1018
A finance user unexpectedly grants another account broad access to audit storage and then signs out. Which interpretation best fits the observed evidence?
- Nonhuman identity scope deviation
- Sensitive privilege change outside established role
- Possible data loss over removable storage
- Audit-control evasion sequence
Explanation
Correct Answer
B:Given “A finance user unexpectedly grants another account broad access to audit storage and then signs out”, administrative grants by an unusual principal can indicate role abuse or credential compromise; that best addresses classification in Privileged identity rare administrative action.
Incorrect Answers
A:This option addresses Service principal unusual resource access because service principals should access only resources consistent with workload purpose and role grants; the Privileged identity rare administrative action classification question instead turns on the fact that administrative grants by an unusual principal can indicate role abuse or credential compromise.
C:This option addresses DLP alert for removable media transfer because bulk copying to portable media increases exfiltration risk when sensitive files and role context align; the Privileged identity rare administrative action classification question instead turns on the fact that administrative grants by an unusual principal can indicate role abuse or credential compromise.
D:That option fits SIEM audit policy tampering since security telemetry configuration changes followed by sensitive activity can indicate deliberate concealment; it does not fit the Privileged identity rare administrative action classification scenario, where administrative grants by an unusual principal can indicate role abuse or credential compromise.
Question 1019
A hunt finds rare destinations in Zeek connection metadata, but full packet payload capture was not enabled. Which THREE limits should constrain the incident finding? Choose THREE.
- Connection metadata can identify endpoints, timing and volumes without revealing every application-layer command.
- A rare destination is a prioritization signal rather than proof of malicious intent.
- A connection record always identifies the initiating local process name.
- No packet payload capture proves the destination never returned data.
- Unusual volume alone shows that transferred bytes were regulated customer data.
- Sensor placement and visibility gaps can hide other hosts or portions of the communication path.
Explanation
Correct Answers
A:Zeek connection logs describe flows and may not include content. Payload conclusions need other authorized records, such as endpoint traces or specific protocol logs.
B:Legitimate updates and business integrations may be uncommon. The analyst should combine peer baselines and destination context before turning rarity into an attribution claim.
F:SPAN/TAP design, encryption and segment coverage constrain what the hunt observed. An absence of records on a sensor should not be interpreted as enterprise-wide absence.
Incorrect Answers
C:Basic network-flow logs do not inherently include endpoint process attribution. EDR or host instrumentation is needed to tie the flow to a specific executable.
D:A telemetry collection choice does not establish network absence. Flow sizes and duration may show data movement even when content was not stored.
E:Byte counts do not classify contents. Data-loss monitoring, application records or other evidence is needed before naming information types.
Question 1020
An object-storage bucket containing internal invoices is accidentally configured for public reading during a deployment. What lasting monitoring control should be added after the case?
- Alert on unusual role assumption followed by privilege changes
- Detect public keys and unusual service-account API activity
- Alert on unusual service-account verbs outside workload profiles
- Enforce public-access restrictions and configuration drift alerts
Explanation
Correct Answer
D:In the Cloud storage anonymous exposure case, preventive guardrails catch future policy mistakes earlier; the observation “An object-storage bucket containing internal invoices is accidentally configured for public reading during a deployment” makes this ongoing detection improvement choice the fitting one.
Incorrect Answers
A:For the alternative AWS unauthorized role assumption situation, behavioral correlation is stronger than treating every STS call as hostile; by contrast, for Cloud storage anonymous exposure ongoing detection improvement, preventive guardrails catch future policy mistakes earlier.
B:In GCP service account key exposed, preventing long-lived key publication reduces machine-credential risk; the reported Cloud storage anonymous exposure case calls for a different ongoing detection improvement conclusion because preventive guardrails catch future policy mistakes earlier.
C:For the alternative Kubernetes compromised workload token situation, role-aware API monitoring highlights privilege abuse beyond normal controllers; by contrast, for Cloud storage anonymous exposure ongoing detection improvement, preventive guardrails catch future policy mistakes earlier.