Question 970
A responder receives a list of suspected command domains with first-seen and last-seen timestamps. What caution prevents an unsupported inference from these records?
- A named ATT&CK technique is not automatically evidence of one actor
- Common malware use is not exclusive to one threat group
- Large intelligence volume is not synonymous with intelligence value
- An IP or domain is not inherently malicious forever
Explanation
Correct Answer
D:Shared hosting and legitimate reassignment make indicator age and context essential; this is the relevant interpretation limit mechanism for Technical threat indicator feed given “A responder receives a list of suspected command domains with first-seen and last-seen timestamps”.
Incorrect Answers
A:In Tactical intelligence of attacker procedures, multiple threat groups and legitimate tools can exhibit similar behaviors; the reported Technical threat indicator feed case calls for a different interpretation limit conclusion because shared hosting and legitimate reassignment make indicator age and context essential.
B:For the alternative Threat actor attribution uncertainty situation, commodity tooling produces misleading overlaps between unrelated campaigns; by contrast, for Technical threat indicator feed interpretation limit, shared hosting and legitimate reassignment make indicator age and context essential.
C:In Intelligence collection requirement, unfiltered feeds can overwhelm analysts while important gaps remain; the reported Technical threat indicator feed case calls for a different interpretation limit conclusion because shared hosting and legitimate reassignment make indicator age and context essential.
Question 971
A targeted email reached a finance employee and the user opened the message. Which TWO limits must be observed before describing the event as an account compromise? Choose TWO.
- Delivery and reading necessarily mean the employee submitted credentials.
- Opening a message does not by itself establish a malicious attachment executed or a password was entered.
- A message trace is irrelevant once delivery is confirmed.
- Even a recorded link click can precede an unsuccessful login or blocked destination.
- Only an antivirus alert can establish whether an employee saw a phishing message.
Explanation
Correct Answers
B:Mail-read metadata shows exposure to the lure, not the entire attack chain. Attachment execution and credential submission require different supporting artifacts.
D:A click shows navigation intent or an attempted request, not necessarily credential theft. Landing-page response, browser and authentication events should be correlated.
Incorrect Answers
A:Message delivery or opening is not the same as interacting with a fraudulent login form. Browser, click and identity records are needed to establish the user's actions.
C:Mail traces remain useful for identifying recipients, timestamps and follow-on similar messages. They should be retained rather than discarded during scoping.
E:Mail-client access records, secure-email gateway logs and user statements can help establish exposure. Endpoint malware detection is not the sole source for a phishing case.
Question 972
A server starts an unexpected job every ten minutes under an account that normally has no scheduled tasks. Which investigative step would most directly establish the relevant scope?
- Identify who modified the task and inspect invoked commands
- Compare source application counts with collector ingestion trends
- Correlate launch agent plist provenance with process events
- Match success to source IP, session and shell history
Explanation
Correct Answer
A:Change history and executable provenance establish whether persistence was planted; this is the relevant scope analysis mechanism for Linux cron persistence evidence given “A server starts an unexpected job every ten minutes under an account that normally has no scheduled tasks”.
Incorrect Answers
B:That option fits Linux dropped syslog messages since discrepancies isolate source-side loss from a central search issue; it does not fit the Linux cron persistence evidence scope analysis scenario, where change history and executable provenance establish whether persistence was planted.
C:This option addresses macOS unified log investigation because file and execution context can connect a scheduled launch with the observed program; the Linux cron persistence evidence scope analysis question instead turns on the fact that change history and executable provenance establish whether persistence was planted.
D:That option fits Linux SSH authentication messages since the overlap distinguishes a real foothold from unrelated logins; it does not fit the Linux cron persistence evidence scope analysis scenario, where change history and executable provenance establish whether persistence was planted.
Question 973
One account receives twenty push prompts within minutes before a single approval followed by privileged resource access. What focused analysis should the analyst perform next?
- Check device continuity, VPN egress and ASN changes
- Compare device compliance, grant type and token audience
- Contact the user and review the approving device context
- Verify employment status and compare first-use actions
Explanation
Correct Answer
C:Given “One account receives twenty push prompts within minutes before a single approval followed by privileged resource access”, user confirmation separates expected enrollment from unwanted authenticator prompts; that best addresses scope analysis in MFA fatigue notification storm.
Incorrect Answers
A:In Impossible travel sign-in correlation, known proxy routes and a stable device can explain an apparently impossible location jump; the reported MFA fatigue notification storm case calls for a different scope analysis conclusion because user confirmation separates expected enrollment from unwanted authenticator prompts.
B:For the alternative Unusual federation token issuance situation, changes in client or scope highlight an abnormal authorization path; by contrast, for MFA fatigue notification storm scope analysis, user confirmation separates expected enrollment from unwanted authenticator prompts.
D:For the alternative Dormant account revival situation, an approved return from leave must be separated from a compromised abandoned account; by contrast, for MFA fatigue notification storm scope analysis, user confirmation separates expected enrollment from unwanted authenticator prompts.
Question 974
A web form input triggers database syntax errors and subsequent payloads alter the query predicate. What record is most useful for confirming this specific pattern?
- Web request bodies and database error telemetry
- Resolver query names and response-size chronology
- Switch ARP inspection events and host ARP tables
- Identity sign-in failure reasons and source clustering
Explanation
Correct Answer
A:For corroboration in SQL injection probing, paired request and error records connect suspect input to query execution changes; this applies to the reported “A web form input triggers database syntax errors and subsequent payloads alter the query predicate”.
Incorrect Answers
B:This option addresses DNS tunneling over queries because full question names and timing reveal payload-like labels and repetitive transactions; the SQL injection probing corroboration question instead turns on the fact that paired request and error records connect suspect input to query execution changes.
C:That option fits ARP spoofing on local subnet since MAC-to-IP changes across peers corroborate neighbor cache poisoning; it does not fit the SQL injection probing corroboration scenario, where paired request and error records connect suspect input to query execution changes.
D:This option addresses Credential stuffing on web login because distinct account counts and password attempt patterns expose broad reuse testing; the SQL injection probing corroboration question instead turns on the fact that paired request and error records connect suspect input to query execution changes.
Question 975
A stolen workforce identity logs into Azure and then accesses an AWS application through federated SSO. The finding has been corroborated and the response team has authorization to act. Which targeted action should the authorized response team prioritize?
- Revoke compromised federation sessions and affected provider grants
- Assign remediation owners for validated exposure findings
- Roll back the suspect revision and protect workload secrets
- Deploy tested detection rules and route cases to response workflows
Explanation
Correct Answer
A:In the Cross-cloud incident correlation case, containment must cover all active relying-party sessions, not just the IdP console; the observation “A stolen workforce identity logs into Azure and then accesses an AWS application through federated SSO” makes this response decision choice the fitting one.
Incorrect Answers
B:For response decision in Cross-cloud incident correlation, Google Cloud Security Command Center posture is a different mechanism: a posture result requires workflow follow-through to reduce risk; here, containment must cover all active relying-party sessions, not just the IdP console.
C:The choice is relevant to Cloud function unusual outbound connections, where trusted deployment and credential rotation stop a malicious function from recurring; for response decision in Cross-cloud incident correlation, containment must cover all active relying-party sessions, not just the IdP console.
D:For response decision in Cross-cloud incident correlation, Google Security Operations threat correlation is a different mechanism: actionable investigations depend on tuned content and clear ownership; here, containment must cover all active relying-party sessions, not just the IdP console.
Question 976
A confidential report is shared through a new anonymous link shortly after a privileged user's suspicious sign-in. Which step would most precisely determine the affected entities?
- Check link usage, audience and any subsequent downloads
- Compare granted permissions with historic workloads and recent secret changes
- Check change approval and pre-change collector health
- Verify approved export exception and transferred file inventory
- Compare initiator permissions and approval history for the grant
Explanation
Correct Answer
A:In the Public sharing policy violation case, public availability alone must be separated from confirmed external retrieval; the observation “A confidential report is shared through a new anonymous link shortly after a privileged user's suspicious sign-in” makes this scope analysis choice the fitting one.
Incorrect Answers
B:In Service principal unusual resource access, an overprivileged app or stolen key can explain unexpected access; the reported Public sharing policy violation case calls for a different scope analysis conclusion because public availability alone must be separated from confirmed external retrieval.
C:For the alternative SIEM audit policy tampering situation, an authorized maintenance action can explain logging changes, but requires evidence; by contrast, for Public sharing policy violation scope analysis, public availability alone must be separated from confirmed external retrieval.
D:In DLP alert for removable media transfer, an approved project handover needs documentation before a theft inference; the reported Public sharing policy violation case calls for a different scope analysis conclusion because public availability alone must be separated from confirmed external retrieval.
E:For the alternative Privileged identity rare administrative action situation, the chain distinguishes a sanctioned emergency delegation from misuse; by contrast, for Public sharing policy violation scope analysis, public availability alone must be separated from confirmed external retrieval.
Question 977
Multiple file servers show rapid renames, encryption-like writes and suspicious recovery catalog deletion. Which technical explanation is most defensible from the evidence?
- Unauthorized compute-resource mining
- Malware replication between segments without confirmed file encryption
- Possible kernel-level concealment
- Ongoing ransomware impact containment
Explanation
Correct Answer
D:Given “Multiple file servers show rapid renames, encryption-like writes and suspicious recovery catalog deletion”, active encryption threatens data availability and can propagate through reachable shares; that best addresses classification in Active ransomware encryption response.
Incorrect Answers
A:In Cryptojacking in production cluster, cryptominers abuse processing capacity and may indicate broader workload credential compromise; the reported Active ransomware encryption response case calls for a different classification conclusion because active encryption threatens data availability and can propagate through reachable shares.
B:Worm propagation would require evidence of automated spread and new host infections. The current observations instead show active file-encryption and recovery-inhibition behavior, which calls for ransomware impact containment.
C:In Kernel rootkit suspected on endpoint, a rootkit may hide activity from local system interfaces that investigators normally trust; the reported Active ransomware encryption response case calls for a different classification conclusion because active encryption threatens data availability and can propagate through reachable shares.
Question 978
Critical incidents appear within target on an overall dashboard but several have exceeded the escalation SLA. The finding has been corroborated and the response team has authorization to act. Which targeted action should the authorized response team prioritize?
- Annotate trend reports with coverage and rule changes
- Tune high-cost rules with stored positive examples
- Escalate overdue critical cases and repair staffing bottlenecks
- Publish detection latency with severity and confidence qualifiers
Explanation
Correct Answer
C:The SLA breach trend by incident tier evidence “Critical incidents appear within target on an overall dashboard but several have exceeded the escalation SLA” is decisive for response decision because operational improvement must target the delayed stage identified by the data.
Incorrect Answers
A:For response decision in SLA breach trend by incident tier, Threat trend comparison without normalization is a different mechanism: readers can understand the effect of detection expansions on headline numbers; here, operational improvement must target the delayed stage identified by the data.
B:The choice is relevant to Noisy use-case Pareto dashboard, where retain known attack matches while removing documented benign patterns; for response decision in SLA breach trend by incident tier, operational improvement must target the delayed stage identified by the data.
D:The choice is relevant to Incident detection latency dashboard, where leadership can compare capabilities without mislabeling investigation lag; for response decision in SLA breach trend by incident tier, operational improvement must target the delayed stage identified by the data.
Question 979
A network IDS marks a flow critical while endpoint telemetry shows the target never executed a related process. The finding has been corroborated and the response team has authorization to act. Which operational remedy is best aligned to the verified issue?
- Reclassify based on observed impact and maintain investigative watch
- Close as benign only after documenting change evidence
- Complete the case summary and assign the correct responder
- Escalate under critical-asset procedures with evidence attached
Explanation
Correct Answer
A:The Conflicting alert severity from two sources evidence “A network IDS marks a flow critical while endpoint telemetry shows the target never executed a related process” is decisive for response decision because evidence-driven priority avoids overreaction while allowing follow-up.
Incorrect Answers
B:That option fits Benign admin activity resembling attack since disposition should preserve traceability for future occurrences and rule tuning; it does not fit the Conflicting alert severity from two sources response decision scenario, where evidence-driven priority avoids overreaction while allowing follow-up.
C:This option addresses Alert escalation missing supporting evidence because an explicit owner and findings reduce emergency back-and-forth; the Conflicting alert severity from two sources response decision question instead turns on the fact that evidence-driven priority avoids overreaction while allowing follow-up.
D:That option fits Low-confidence alert with crown-jewel impact since risk-based prioritization protects sensitive systems without declaring unverified compromise; it does not fit the Conflicting alert severity from two sources response decision scenario, where evidence-driven priority avoids overreaction while allowing follow-up.
Question 980
A departing engineer downloads hundreds of repository archives immediately before offboarding after months of limited activity. Which limitation should shape how the analyst interprets this evidence?
- A new file extension alone does not prove ransomware
- An Office process spawning a shell is suspicious but context-dependent
- A 4769 event is also normal Kerberos activity
- High download volume alone does not establish malicious intent
Explanation
Correct Answer
D:Legitimate release engineering or approved backups may have comparable patterns; this is the relevant interpretation limit mechanism for Insider bulk source-code copying given “A departing engineer downloads hundreds of repository archives immediately before offboarding after months of limited activity”.
Incorrect Answers
A:For interpretation limit in Insider bulk source-code copying, Ransomware file encryption is a different mechanism: backup, migration or compression software may legitimately rename large file sets; here, legitimate release engineering or approved backups may have comparable patterns.
B:The choice is relevant to Malicious Office macro delivery, where approved automation tools can create similar chains and require allowlisting by provenance; for interpretation limit in Insider bulk source-code copying, legitimate release engineering or approved backups may have comparable patterns.
C:For interpretation limit in Insider bulk source-code copying, Kerberoasting service-ticket harvesting is a different mechanism: the suspicious evidence is the context and pattern, not the event ID alone; here, legitimate release engineering or approved backups may have comparable patterns.