Question 680
A remote office retains events on disk while the central SIEM displays a growing delay during a WAN outage. Which measure would make future alerts about this activity more useful?
- Monitor collector transport failures and certificate expiry
- Alert on ingestion lag and forwarder disk utilization
- Monitor deletion attempts and retention compliance drift
- Track duplicate ratios by sensor and route
Explanation
Correct Answer
B:The Forwarder queue saturation evidence “A remote office retains events on disk while the central SIEM displays a growing delay during a WAN outage” is decisive for ongoing detection improvement because queue growth can exhaust local storage long before analysts notice missing alerts.
Incorrect Answers
A:This option addresses Secure syslog transport mismatch because encrypted pipelines still need certificate and delivery-health supervision; the Forwarder queue saturation ongoing detection improvement question instead turns on the fact that queue growth can exhaust local storage long before analysts notice missing alerts.
C:This option addresses Immutable log retention requirements because policy violations need their own audit trail independent of event-search dashboards; the Forwarder queue saturation ongoing detection improvement question instead turns on the fact that queue growth can exhaust local storage long before analysts notice missing alerts.
D:That option fits Duplicate event ingestion since a sudden change flags collection topology regressions after deployments; it does not fit the Forwarder queue saturation ongoing detection improvement scenario, where queue growth can exhaust local storage long before analysts notice missing alerts.
Question 681
An organization needs to prioritize exposed cloud assets and misconfigurations identified across Google Cloud projects. 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?
- Assign remediation owners for validated exposure findings
- Revoke compromised federation sessions and affected provider grants
- Revoke confirmed abusive access and correct IAM bindings
- Deploy tested detection rules and route cases to response workflows
Explanation
Correct Answer
A:A posture result requires workflow follow-through to reduce risk; this is the relevant response decision mechanism for Google Cloud Security Command Center posture given “An organization needs to prioritize exposed cloud assets and misconfigurations identified across Google Cloud projects”.
Incorrect Answers
B:For response decision in Google Cloud Security Command Center posture, Cross-cloud incident correlation is a different mechanism: containment must cover all active relying-party sessions, not just the IdP console; here, a posture result requires workflow follow-through to reduce risk.
C:The choice is relevant to Google Cloud audit log principal investigation, where response should address both stolen key paths and grants already made; for response decision in Google Cloud Security Command Center posture, a posture result requires workflow follow-through to reduce risk.
D:For response decision in Google Cloud Security Command Center posture, Google Security Operations threat correlation is a different mechanism: actionable investigations depend on tuned content and clear ownership; here, a posture result requires workflow follow-through to reduce risk.
Question 682
An analyst pastes raw incident logs containing customer identifiers into an external generative service without data-processing approval. The finding has been corroborated and the response team has authorization to act. What containment or corrective change best addresses the confirmed finding?
- Add approval gates and reversible actions for high-impact containment
- Recalibrate the model and restore coverage using verified rules
- Correct the fields and require human approval before deployment
- Use approved redaction and enterprise-controlled AI workflows
Explanation
Correct Answer
D:Controlled preprocessing supports analysis without gratuitously exposing private incident data; this is the relevant response decision mechanism for Sensitive data entered into AI copilot given “An analyst pastes raw incident logs containing customer identifiers into an external generative service without data-processing approval”.
Incorrect Answers
A:That option fits Automated response approval boundary since human review or stronger multi-signal triggers reduce business harm; it does not fit the Sensitive data entered into AI copilot response decision scenario, where controlled preprocessing supports analysis without gratuitously exposing private incident data.
B:This option addresses AI alert score drift because a fallback deterministic detector can protect high-risk gaps during retraining; the Sensitive data entered into AI copilot response decision question instead turns on the fact that controlled preprocessing supports analysis without gratuitously exposing private incident data.
C:That option fits AI-generated SIEM rule hallucination since generated rules are drafts until syntax, behavior and scope are verified; it does not fit the Sensitive data entered into AI copilot response decision scenario, where controlled preprocessing supports analysis without gratuitously exposing private incident data.
Question 683
A finance user unexpectedly grants another account broad access to audit storage and then signs out. The finding has been corroborated and the response team has authorization to act. Which operational remedy is best aligned to the verified issue?
- Restore auditing and investigate the modifying administrator
- Disable unauthorized anonymous links and review access grants
- Revoke excessive access and rotate proven compromised app credentials
- Block unauthorized removable-media transfers and preserve records
- Remove unauthorized grants and examine the initiator's session
Explanation
Correct Answer
E:In the Privileged identity rare administrative action case, both the newly privileged principal and grant actor require examination; the observation “A finance user unexpectedly grants another account broad access to audit storage and then signs out” makes this response decision choice the fitting one.
Incorrect Answers
A:For the alternative SIEM audit policy tampering situation, reinstating coverage and preserving remote records limit the blind spot; by contrast, for Privileged identity rare administrative action response decision, both the newly privileged principal and grant actor require examination.
B:In Public sharing policy violation, closing share paths prevents further access while retrieval evidence is preserved; the reported Privileged identity rare administrative action case calls for a different response decision conclusion because both the newly privileged principal and grant actor require examination.
C:For the alternative Service principal unusual resource access situation, changes should restore minimal function while interrupting misuse; by contrast, for Privileged identity rare administrative action response decision, both the newly privileged principal and grant actor require examination.
D:In DLP alert for removable media transfer, device controls should be applied proportionately through the approved insider-response process; the reported Privileged identity rare administrative action case calls for a different response decision conclusion because both the newly privileged principal and grant actor require examination.
Question 684
An alert is created before the asset inventory labels the targeted host as a payment-processing system. Which technical explanation is most defensible from the evidence?
- Identity entity-normalization mismatch
- Missing SIEM data-source heartbeat
- Late asset-context enrichment
- Hot versus archival search boundary
Explanation
Correct Answer
C:For classification in Context enrichment delay, detection ranking can be wrong when criticality metadata is unavailable at alert creation; this applies to the reported “An alert is created before the asset inventory labels the targeted host as a payment-processing system”.
Incorrect Answers
A:The choice is relevant to Cross-vendor user identifier normalization, where different identifier representations can prevent related events from being grouped into one actor; for classification in Context enrichment delay, detection ranking can be wrong when criticality metadata is unavailable at alert creation.
B:For classification in Context enrichment delay, SIEM ingestion freshness gap is a different mechanism: a sudden source silence can disable detections even when the sensor continues operating; here, detection ranking can be wrong when criticality metadata is unavailable at alert creation.
D:For classification in Context enrichment delay, SIEM hot-search retention mismatch is a different mechanism: operational indexing windows can be shorter than required incident lookback periods; here, detection ranking can be wrong when criticality metadata is unavailable at alert creation.
Question 685
A remote office retains events on disk while the central SIEM displays a growing delay during a WAN outage. Which artifact provides the strongest corroborating detail?
- Packet capture showing UDP 514 log payloads in clear text
- Forwarder queue depth, retry and acknowledgement metrics
- Raw sample versus parsed field mapping and parser version
- Archive lifecycle and object-lock configuration evidence
Explanation
Correct Answer
B:These show whether events are delayed in transit rather than absent at the source; this is the relevant corroboration mechanism for Forwarder queue saturation given “A remote office retains events on disk while the central SIEM displays a growing delay during a WAN outage”.
Incorrect Answers
A:The choice is relevant to Secure syslog transport mismatch, where the wire trace confirms both transport choice and exposure of event content; for corroboration in Forwarder queue saturation, these show whether events are delayed in transit rather than absent at the source.
C:The choice is relevant to SIEM parser field loss, where direct comparison identifies which structured field no longer matches source syntax; for corroboration in Forwarder queue saturation, these show whether events are delayed in transit rather than absent at the source.
D:For corroboration in Forwarder queue saturation, Immutable log retention requirements is a different mechanism: retention settings reveal whether deletion or rewriting is possible by privileged operators; here, these show whether events are delayed in transit rather than absent at the source.
Question 686
Malware is removed from a privileged admin laptop, but a hidden persistence mechanism may remain after local cleanup. 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 in stages and reopen network paths only after checks
- Rotate compromised privileges and rebuild trust through approved stages
- Assign owners and deadlines for measurable corrective actions
- Reimage from trusted media and reissue exposed credentials
Explanation
Correct Answer
D:In the Trusted endpoint rebuild case, known-good rebuilding removes uncertain software state and closes identity risk; the observation “Malware is removed from a privileged admin laptop, but a hidden persistence mechanism may remain after local cleanup” makes this response decision choice the fitting one.
Incorrect Answers
A:In Ransomware isolated restore validation, controlled recovery prevents premature reinfection or unstable production; the reported Trusted endpoint rebuild case calls for a different response decision conclusion because known-good rebuilding removes uncertain software state and closes identity risk.
B:For the alternative Credential recovery after domain compromise situation, replacing credentials and tokens closes access paths inherited from the intrusion; by contrast, for Trusted endpoint rebuild response decision, known-good rebuilding removes uncertain software state and closes identity risk.
C:In Post-incident lessons-learned review, a lessons-learned meeting without implementation does not reduce repeat risk; the reported Trusted endpoint rebuild case calls for a different response decision conclusion because known-good rebuilding removes uncertain software state and closes identity risk.
Question 687
A valid automation access key appears in a public source repository and its usage logs show new foreign IPs. What evidence should be obtained to validate the suspected mechanism?
- Helpdesk reset ticket and authenticator registration audit
- Repository exposure history and cloud credential use audit
- Directory group-change event and initiating account sign-ins
- Identity provider key audit and relying-party validation records
Explanation
Correct Answer
B:Given “A valid automation access key appears in a public source repository and its usage logs show new foreign IPs”, source records reveal exposure interval and actual API activity; that best addresses corroboration in Exposed cloud API credential.
Incorrect Answers
A:For the alternative Unauthorized MFA factor registration situation, the requester, new factor and approval record support the legitimacy check; by contrast, for Exposed cloud API credential corroboration, source records reveal exposure interval and actual API activity.
C:For the alternative Privilege escalation via group membership situation, actor, target and timestamps identify the delegation path; by contrast, for Exposed cloud API credential corroboration, source records reveal exposure interval and actual API activity.
D:In Compromised federation signing key, trust configuration determines which applications could accept forged tokens; the reported Exposed cloud API credential case calls for a different corroboration conclusion because source records reveal exposure interval and actual API activity.
Question 688
The SOC sends a copied disk image to an outside expert but has no record of checksum, custodian or transfer time. How should the detection program improve coverage for this pattern?
- Run cross-team exercises focused on conflicting actions
- Review severity-change timeliness in incident metrics
- Require checksum verification at each evidence handoff
- Exercise executive and customer statement approval workflows
Explanation
Correct Answer
C:In the Evidence transfer between response teams case, routine integrity checks reduce uncertainty during inter-team collaboration; the observation “The SOC sends a copied disk image to an outside expert but has no record of checksum, custodian or transfer time” makes this ongoing detection improvement choice the fitting one.
Incorrect Answers
A:The choice is relevant to Incident commander coordination gap, where joint drills expose dependencies missing from isolated playbooks; for ongoing detection improvement in Evidence transfer between response teams, routine integrity checks reduce uncertainty during inter-team collaboration.
B:For ongoing detection improvement in Evidence transfer between response teams, Incident severity change during response is a different mechanism: delayed escalation can allow a broad compromise to grow unnoticed; here, routine integrity checks reduce uncertainty during inter-team collaboration.
D:For ongoing detection improvement in Evidence transfer between response teams, Public incident communications control is a different mechanism: prepared templates and owners reduce delays during genuine disclosures; here, routine integrity checks reduce uncertainty during inter-team collaboration.
Question 689
An application audit shows an ordinary customer granted administrator access shortly after a suspicious support session. Which artifact provides the strongest corroborating detail?
- WAF disposition joined to web and database error events
- Application export logs and outbound transfer metadata
- Web request identifier matched to server process creation
- Application RBAC audit showing actor, target and before-after values
Explanation
Correct Answer
D:The change history identifies which principal modified the user's privileges; this is the relevant corroboration mechanism for Unexpected web administrative role assignment given “An application audit shows an ordinary customer granted administrator access shortly after a suspicious support session”.
Incorrect Answers
A:This option addresses WAF bypass with origin success because the same request identifier connects filtering decision with downstream behavior; the Unexpected web administrative role assignment corroboration question instead turns on the fact that the change history identifies which principal modified the user's privileges.
B:That option fits Massive object-storage upload through web app since destination, size, user and dataset establish how much data the application sent; it does not fit the Unexpected web administrative role assignment corroboration scenario, where the change history identifies which principal modified the user's privileges.
C:This option addresses Web-shell request and process correlation because linkage shows which HTTP request was followed by command execution; the Unexpected web administrative role assignment corroboration question instead turns on the fact that the change history identifies which principal modified the user's privileges.
Question 690
An employee endpoint launches remote administration sessions to several servers using an account not normally assigned to it. Which limitation should shape how the analyst interprets this evidence?
- SMB traffic can be legitimate enterprise administration
- Blocking one malicious domain may not remove host persistence
- Blocking single source IPs rarely stops a distributed flood
- A bad DNS answer need not mean the authoritative zone was compromised
- A listening RDP port is an exposure, not proof of compromise
Explanation
Correct Answer
A:For interpretation limit in SMB lateral spread response, account role, maintenance records and remote activity must inform containment; this applies to the reported “An employee endpoint launches remote administration sessions to several servers using an account not normally assigned to it”.
Incorrect Answers
B:This option addresses Malware command-channel response because the attacker can switch infrastructure while the implanted process remains; the SMB lateral spread response interpretation limit question instead turns on the fact that account role, maintenance records and remote activity must inform containment.
C:That option fits Distributed denial-of-service incident since botnet traffic can span many hosts and spoofable source contexts; it does not fit the SMB lateral spread response interpretation limit scenario, where account role, maintenance records and remote activity must inform containment.
D:This option addresses Internal DNS poisoning response because client resolver configuration and local poisoning can explain redirection; the SMB lateral spread response interpretation limit question instead turns on the fact that account role, maintenance records and remote activity must inform containment.
E:That option fits Public RDP exposure compromise since successful sessions and unauthorized actions are needed to conclude entry; it does not fit the SMB lateral spread response interpretation limit scenario, where account role, maintenance records and remote activity must inform containment.