Question 340
Executives track average alert handling time but cannot see how long confirmed intrusions ran before discovery. The analyst has not yet established malicious intent or downstream impact. Which caveat most directly affects assessment of the evidence?
- A low alert count does not automatically identify the best rule
- A successful query over received logs is not proof of complete visibility
- Incident start time may be estimated rather than observed
- An average below the target does not mean every case met its SLA
Explanation
Correct Answer
C:Given “Executives track average alert handling time but cannot see how long confirmed intrusions ran before discovery”, MTTD reporting should acknowledge uncertainty in the earliest known malicious action; that best addresses interpretation limit in Incident detection latency dashboard.
Incorrect Answers
A:In Noisy use-case Pareto dashboard, a rarely triggered high-impact rule can be extremely valuable; the reported Incident detection latency dashboard case calls for a different interpretation limit conclusion because MTTD reporting should acknowledge uncertainty in the earliest known malicious action.
B:For the alternative SOC data-source coverage dashboard situation, uncollected events are invisible to every search and rule; by contrast, for Incident detection latency dashboard interpretation limit, MTTD reporting should acknowledge uncertainty in the earliest known malicious action.
D:For the alternative SLA breach trend by incident tier situation, a few severe outliers still require explicit reporting; by contrast, for Incident detection latency dashboard interpretation limit, MTTD reporting should acknowledge uncertainty in the earliest known malicious action.
Question 341
An organization has clean offline backups but has not tested whether restored application databases start consistently. Which technical explanation is most defensible from the evidence?
- Response improvement after incident closure
- Incomplete post-containment eradication
- Untrusted endpoint recovery state
- Recovery functionality verification
- Compromised identity reuse during recovery
Explanation
Correct Answer
D:For classification in Ransomware isolated restore validation, readable backup files do not establish that dependent services can operate after restoration; this applies to the reported “An organization has clean offline backups but has not tested whether restored application databases start consistently”.
Incorrect Answers
A:In Post-incident lessons-learned review, a structured retrospective identifies process and detection gaps independent of blame; the reported Ransomware isolated restore validation case calls for a different classification conclusion because readable backup files do not establish that dependent services can operate after restoration.
B:For the alternative Incident eradication verification situation, threat removal requires evidence that malicious processes and network pathways have ceased; by contrast, for Ransomware isolated restore validation classification, readable backup files do not establish that dependent services can operate after restoration.
C:In Trusted endpoint rebuild, a host with uncertain system integrity should not be treated as safe after one artifact is deleted; the reported Ransomware isolated restore validation case calls for a different classification conclusion because readable backup files do not establish that dependent services can operate after restoration.
E:In Credential recovery after domain compromise, restoration can reintroduce attacker access when old credentials and trust paths remain valid; the reported Ransomware isolated restore validation case calls for a different classification conclusion because readable backup files do not establish that dependent services can operate after restoration.
Question 342
A departing researcher copies confidential designs to a personal file-sharing account hours before access termination. What record is most useful for confirming this specific pattern?
- DLP records, file classification and sanctioned-transfer approvals
- Payroll row-change audit, account session and approval history
- DLP evidence, policy scope and legal approval record
- Contract end date, identity status and portal session logs
Explanation
Correct Answer
A:In the Suspected employee intellectual-property export case, data labels and destination context distinguish approved handoff from suspicious transfer; the observation “A departing researcher copies confidential designs to a personal file-sharing account hours before access termination” makes this corroboration choice the fitting one.
Incorrect Answers
B:For the alternative Unauthorized change to payroll records situation, before-and-after values identify the alteration and its responsible principal; by contrast, for Suspected employee intellectual-property export corroboration, data labels and destination context distinguish approved handoff from suspicious transfer.
C:In Employee privacy during insider case, an incident indicator does not by itself justify unrestricted monitoring of private content; the reported Suspected employee intellectual-property export case calls for a different corroboration conclusion because data labels and destination context distinguish approved handoff from suspicious transfer.
D:For the alternative Former contractor access remains active situation, those records demonstrate the mismatch between authorization period and current access; by contrast, for Suspected employee intellectual-property export corroboration, data labels and destination context distinguish approved handoff from suspicious transfer.
Question 343
An exposed API receives many unauthorized requests with rotating tokens and a small set of sensitive resource endpoints. Which technical explanation is most defensible from the evidence?
- Token enumeration against protected API
- Application-layer exploit attempt reaching backend
- Unauthorized application privilege assignment
- Potential application-mediated data staging
- Possible web-shell command execution
Explanation
Correct Answer
A:In the API bearer-token guessing case, high invalid-token rates near privileged routes indicate automated attempts to obtain usable credentials; the observation “An exposed API receives many unauthorized requests with rotating tokens and a small set of sensitive resource endpoints” makes this classification choice the fitting one.
Incorrect Answers
B:This option addresses WAF bypass with origin success because an allowed edge request plus server-side error increases concern about exploit reachability; the API bearer-token guessing classification question instead turns on the fact that high invalid-token rates near privileged routes indicate automated attempts to obtain usable credentials.
C:That option fits Unexpected web administrative role assignment since sensitive role changes can establish persistent access even without further exploits; it does not fit the API bearer-token guessing classification scenario, where high invalid-token rates near privileged routes indicate automated attempts to obtain usable credentials.
D:This option addresses Massive object-storage upload through web app because an export feature can be used to move sensitive records to an attacker-controlled destination; the API bearer-token guessing classification question instead turns on the fact that high invalid-token rates near privileged routes indicate automated attempts to obtain usable credentials.
E:That option fits Web-shell request and process correlation since unexpected shell children from a web worker can reveal remote command execution via a malicious script; it does not fit the API bearer-token guessing classification scenario, where high invalid-token rates near privileged routes indicate automated attempts to obtain usable credentials.
Question 344
A SIEM shows one laptop as two assets because the EDR reports hostname while the DHCP feed uses an old name. The finding has been corroborated and the response team has authorization to act. What action should the incident owner take to reduce the immediate risk?
- Restore the broken collection path and replay retained events
- Repair the enrichment feed and reprioritize unresolved alerts
- Fix asset entity stitching with identity provenance
- Document and test archive retrieval for incident response
Explanation
Correct Answer
C:In the Cross-source entity duplication case, reconciliation should not merge distinct hosts sharing reused address labels; the observation “A SIEM shows one laptop as two assets because the EDR reports hostname while the DHCP feed uses an old name” makes this response decision choice the fitting one.
Incorrect Answers
A:In SIEM ingestion freshness gap, historical backfill closes investigative gaps after live delivery resumes; the reported Cross-source entity duplication case calls for a different response decision conclusion because reconciliation should not merge distinct hosts sharing reused address labels.
B:For the alternative Context enrichment delay situation, updating criticality must affect open high-risk cases, not only new events; by contrast, for Cross-source entity duplication response decision, reconciliation should not merge distinct hosts sharing reused address labels.
D:For the alternative SIEM hot-search retention mismatch situation, cold data must be searchable within the required investigation SLA; by contrast, for Cross-source entity duplication response decision, reconciliation should not merge distinct hosts sharing reused address labels.
Question 345
A Tier 1 analyst forwards a critical incident with only the detector title and no affected host or timeline. What follow-up analysis most effectively distinguishes this case?
- Verify key timestamps, confidence and attempted triage actions
- Compare the flagged sequence with verified maintenance artifacts
- Validate whether the observed action touched sensitive assets
- Cluster alerts by host, parent process and causal sequence
- Trace network path and confirm target process or application state
Explanation
Correct Answer
A:The Alert escalation missing supporting evidence evidence “A Tier 1 analyst forwards a critical incident with only the detector title and no affected host or timeline” is decisive for scope analysis because handoff quality depends on communicating known facts and unresolved questions.
Incorrect Answers
B:This option addresses Benign admin activity resembling attack because the analyst must test the explanation instead of closing every matching alert; the Alert escalation missing supporting evidence scope analysis question instead turns on the fact that handoff quality depends on communicating known facts and unresolved questions.
C:That option fits Low-confidence alert with crown-jewel impact since impact scoping can raise priority before final attack attribution; it does not fit the Alert escalation missing supporting evidence scope analysis scenario, where handoff quality depends on communicating known facts and unresolved questions.
D:This option addresses Repeated duplicate detection tickets because grouping helps distinguish overlapping detections from separate compromises; the Alert escalation missing supporting evidence scope analysis question instead turns on the fact that handoff quality depends on communicating known facts and unresolved questions.
E:That option fits Conflicting alert severity from two sources since a perimeter signature does not imply on-host compromise; it does not fit the Alert escalation missing supporting evidence scope analysis scenario, where handoff quality depends on communicating known facts and unresolved questions.
Question 346
A departing researcher copies confidential designs to a personal file-sharing account hours before access termination. The finding has been corroborated and the response team has authorization to act. What action should the incident owner take to reduce the immediate risk?
- Freeze the compromised workflow and restore validated records
- Route intrusive collection requests through legal and HR authorization
- Revoke suspicious vault access and rotate potentially exposed secrets
- Restrict unapproved access under coordinated legal and HR procedures
Explanation
Correct Answer
D:In the Suspected employee intellectual-property export case, preserve evidence and ensure proportionate action before final conclusions; the observation “A departing researcher copies confidential designs to a personal file-sharing account hours before access termination” makes this response decision choice the fitting one.
Incorrect Answers
A:That option fits Unauthorized change to payroll records since controlled correction avoids further corruption while preserving original evidence; it does not fit the Suspected employee intellectual-property export response decision scenario, where preserve evidence and ensure proportionate action before final conclusions.
B:This option addresses Employee privacy during insider case because controlled approvals protect the investigation and employee rights; the Suspected employee intellectual-property export response decision question instead turns on the fact that preserve evidence and ensure proportionate action before final conclusions.
C:That option fits Privileged vault secret retrieval anomaly since response must address both vault entitlement and secrets already retrieved; it does not fit the Suspected employee intellectual-property export response decision scenario, where preserve evidence and ensure proportionate action before final conclusions.
Question 347
An object-storage bucket containing internal invoices is accidentally configured for public reading during a deployment. The analyst has not yet established malicious intent or downstream impact. What caution prevents an unsupported inference from these records?
- Public readability is not proof every object was downloaded
- A namespace name is not automatically a hard security boundary
- Deleting the exposed log does not revoke the service-account key
- Disabling a human user does not disable an unrelated app principal
Explanation
Correct Answer
A:The Cloud storage anonymous exposure evidence “An object-storage bucket containing internal invoices is accidentally configured for public reading during a deployment” is decisive for interpretation limit because access logs and distribution caches are needed to estimate real disclosure.
Incorrect Answers
B:For interpretation limit in Cloud storage anonymous exposure, Kubernetes compromised workload token is a different mechanism: cluster-scoped roles and network privileges can cross workload boundaries; here, access logs and distribution caches are needed to estimate real disclosure.
C:The choice is relevant to GCP service account key exposed, where credential invalidation is mandatory after confirmed disclosure; for interpretation limit in Cloud storage anonymous exposure, access logs and distribution caches are needed to estimate real disclosure.
D:For interpretation limit in Cloud storage anonymous exposure, Azure automation identity misuse is a different mechanism: service identities maintain independent credentials and permissions; here, access logs and distribution caches are needed to estimate real disclosure.
Question 348
A standard user is added to a high-privilege group by a previously unused administrator account. The finding has been corroborated and the response team has authorization to act. What action should the incident owner take to reduce the immediate risk?
- Disable or rotate the leaked key and replace it safely
- Revoke suspicious sessions and reset credentials and factors
- Revoke unauthorized membership and investigate both principals
- Rotate compromised signing keys and coordinate trust updates
Explanation
Correct Answer
C:The Privilege escalation via group membership evidence “A standard user is added to a high-privilege group by a previously unused administrator account” is decisive for response decision because removing new rights and securing the grantor address persistence and cause.
Incorrect Answers
A:For response decision in Privilege escalation via group membership, Exposed cloud API credential is a different mechanism: credential revocation stops continued use while affected workloads are updated; here, removing new rights and securing the grantor address persistence and cause.
B:The choice is relevant to Employee account takeover, where account restoration must close current access paths and prevent reentry; for response decision in Privilege escalation via group membership, removing new rights and securing the grantor address persistence and cause.
D:The choice is relevant to Compromised federation signing key, where relying parties must adopt trusted replacements without leaving old signatures valid; for response decision in Privilege escalation via group membership, removing new rights and securing the grantor address persistence and cause.
Question 349
An incident was contained rapidly but recurring alert-routing mistakes caused avoidable delays throughout the week. The finding has been corroborated and the response team has authorization to act. What containment or corrective change best addresses the confirmed finding?
- Rotate compromised privileges and rebuild trust through approved stages
- Reimage from trusted media and reissue exposed credentials
- Restore in stages and reopen network paths only after checks
- Assign owners and deadlines for measurable corrective actions
Explanation
Correct Answer
D:Given “An incident was contained rapidly but recurring alert-routing mistakes caused avoidable delays throughout the week”, a lessons-learned meeting without implementation does not reduce repeat risk; that best addresses response decision in Post-incident lessons-learned review.
Incorrect Answers
A:This option addresses Credential recovery after domain compromise because replacing credentials and tokens closes access paths inherited from the intrusion; the Post-incident lessons-learned review response decision question instead turns on the fact that a lessons-learned meeting without implementation does not reduce repeat risk.
B:That option fits Trusted endpoint rebuild since known-good rebuilding removes uncertain software state and closes identity risk; it does not fit the Post-incident lessons-learned review response decision scenario, where a lessons-learned meeting without implementation does not reduce repeat risk.
C:This option addresses Ransomware isolated restore validation because controlled recovery prevents premature reinfection or unstable production; the Post-incident lessons-learned review response decision question instead turns on the fact that a lessons-learned meeting without implementation does not reduce repeat risk.
Question 350
A third-party cloud app received persistent mailbox read permissions through a user consent flow after a phishing link. Which scoping query or comparison best tests the working hypothesis?
- Find recipients and hunt the spawned executable across devices
- Verify pending transactions with finance via known callback numbers
- Identify affected identities and all permission scopes
- Find all recipients and identify submitted accounts
- Map poster distribution and resulting identity sign-ins
Explanation
Correct Answer
C:In the Malicious OAuth app consent response case, incident scope depends on the app's grants, not only the initially clicked link; the observation “A third-party cloud app received persistent mailbox read permissions through a user consent flow after a phishing link” makes this scope analysis choice the fitting one.
Incorrect Answers
A:The choice is relevant to Malicious email attachment execution, where campaign scope requires both mail and endpoint visibility; for scope analysis in Malicious OAuth app consent response, incident scope depends on the app's grants, not only the initially clicked link.
B:For scope analysis in Malicious OAuth app consent response, Business email compromise wire request is a different mechanism: independent confirmation limits reliance on potentially compromised mail threads; here, incident scope depends on the app's grants, not only the initially clicked link.
D:For scope analysis in Malicious OAuth app consent response, Targeted phishing mail delivery is a different mechanism: campaign scoping goes beyond the first reporter to other targeted users; here, incident scope depends on the app's grants, not only the initially clicked link.
E:The choice is relevant to QR-code phishing landing page, where physical and web evidence jointly estimate exposed employee populations; for scope analysis in Malicious OAuth app consent response, incident scope depends on the app's grants, not only the initially clicked link.