Question 160
A responder investigating collector backlog monitoring has corroborated this finding: An increasing queue age indicates delayed security-event visibility. What action belongs next in the approved workflow?
- Use a reliable protected syslog transport or local buffering relay
- Restore queue capacity and prioritize lossless backlog processing
- Normalize event time to UTC while retaining source-time metadata
- Deploy the correct CEF parser and map source fields to the target schema
Explanation
Correct Answer
B:Dropping old records indiscriminately risks destroying evidence for the delayed period. The response must subsequently be checked by confirming backlog clears and generated test events reach the index within the SLA; otherwise the original exposure may persist.
Incorrect Answers
A:Transport acknowledgement and queueing improve survivability under packet loss, which would be relevant to Syslog transport reliability, but not the collector backlog monitoring scenario that requires restore queue capacity and prioritize lossless backlog processing.
C:Overwriting source timestamps without traceability makes later timeline review harder; prioritizing that timestamp normalization mechanism would leave this collector backlog monitoring decision unresolved because restore queue capacity and prioritize lossless backlog processing is the direct fit.
D:This relates to CEF parsing: changing alert thresholds cannot compensate for missing event attributes; the collector backlog monitoring question instead requires choosing the immediate operational response, specifically restore queue capacity and prioritize lossless backlog processing.
Question 161
A production automation secret appears in a public repository and unexpected API calls begin. Which additional finding would most directly support the suspected security interpretation?
- Unexpected enrollment gives an attacker a durable authentication factor
- Privilege abuse creates persistence and expands the incident beyond one user
- Successful attacker session follows known credential disclosure
- A nonhuman credential is exposed with permissions to alter cloud resources
Explanation
Correct Answer
D:Service principals have independent secrets and tokens outside human password resets. Investigators should still corroborate it with repository exposure, principal sign-in logs and assigned API permissions before assigning definitive scope or attribution.
Incorrect Answers
A:Password resets alone may not remove newly registered MFA methods, which would be relevant to suspicious MFA enrollment, but not the service principal exposure scenario that requires a nonhuman credential is exposed with permissions to alter cloud resources.
B:New identities and grants can survive the loss of the original stolen credential; that is suited to investigating compromised privileged account, whereas the service principal exposure case requires a nonhuman credential is exposed with permissions to alter cloud resources for recognizing the distinguishing signal.
C:The alternative concerns stolen user password: password theft can create active sessions and refresh tokens beyond the original login; however, the described service principal exposure situation calls for a nonhuman credential is exposed with permissions to alter cloud resources.
Question 162
An alert suggests impossible travel triage. The recorded clue is: Geographic separation is inconsistent with plausible physical movement. What evidence would best test this hypothesis?
- Session device IDs, IP ownership, VPN egress and MFA context
- Account last-use history, current access rights and session event data
- MFA challenge history, device binding and subsequent sign-in activity
- Distinct username count by source plus success and MFA details
- Authentication event time, username normalization and five-minute grouping
Explanation
Correct Answer
A:Device and network metadata help separate account takeover from egress relocation. The result can be compared with geographic separation is inconsistent with plausible physical movement to verify that the suspected mechanism is actually present.
Incorrect Answers
B:Risk assessment requires both dormancy and the actual privileged action; prioritizing that dormant-account access mechanism would leave this impossible travel triage decision unresolved because session device IDs, IP ownership, VPN egress and MFA context is the direct fit.
C:This relates to MFA fatigue attempts: the sequence is more revealing than a single accepted push notification; the impossible travel triage question instead requires independently corroborating the suspected behavior, specifically session device IDs, IP ownership, VPN egress and MFA context.
D:For password-spray rule, identity diversity and later authentications help determine attack progression; here the narrower objective is independently corroborating the suspected behavior in impossible travel triage, best addressed by session device IDs, IP ownership, VPN egress and MFA context.
E:Correct grouping keys and event-time windows are required to count attempts accurately; this evidence or action is associated with authentication failure window, whereas the case concerns impossible travel triage and calls for session device IDs, IP ownership, VPN egress and MFA context.
Question 163
A user grants an unfamiliar application extensive mail-read scopes after receiving a convincing message. Which additional finding would most directly support the suspected security interpretation?
- New third-party consent grants unusually broad delegated permissions
- Account enrollment is missing an audit connector or organization trail scope
- Unexpected allow-all rule modification expands exposed network access
- Certificate issuer or fingerprint differs from a known pinned service identity
Explanation
Correct Answer
A:OAuth consent attacks can establish access without repeated password use. The follow-up evidence is identity audit of application consent, publisher and granted scopes, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
B:Cloud growth can create blind spots unless sources are onboarded automatically; applied to this oAuth consent anomaly case, it addresses cloud logging gap instead of the required step: new third-party consent grants unusually broad delegated permissions.
C:Cloud audit events capture configuration changes that ordinary flow logs cannot, which would be relevant to cloud control-plane edit, but not the oAuth consent anomaly scenario that requires new third-party consent grants unusually broad delegated permissions.
D:Unexpected certificate changes can indicate interception or legitimate rotation, which would be relevant to TLS certificate anomaly, but not the oAuth consent anomaly scenario that requires new third-party consent grants unusually broad delegated permissions.
Question 164
The working evidence for unauthorized removable media includes this observation: Removable media connection aligns with bulk reads of restricted files. Which intervention is the best fit for the established finding?
- Preserve evidence and work with insider-risk owners on proportionate access limits
- Secure the exceptional identity and launch high-priority access review
- Suspend unauthorized transfer and initiate a controlled insider-risk investigation
- Disable expired access and investigate post-termination activity
Explanation
Correct Answer
C:Deleting files from the employee's device may destroy evidence prematurely. Operational success is not assumed until restricted file transfer is blocked under policy and authorized workflows remain available, the relevant outcome for this response.
Incorrect Answers
A:Blanket deletion of repositories would damage business operations; this evidence or action is associated with suspicious source-code export, whereas the case concerns unauthorized removable media and calls for suspend unauthorized transfer and initiate a controlled insider-risk investigation.
B:Normalizing this account into routine operations defeats its emergency purpose; that is suited to investigating misuse of break-glass account, whereas the unauthorized removable media case requires suspend unauthorized transfer and initiate a controlled insider-risk investigation for choosing the immediate operational response.
D:Only deleting a badge record would not revoke network credentials; applied to this unauthorized removable media case, it addresses departing contractor access instead of the required step: suspend unauthorized transfer and initiate a controlled insider-risk investigation.
Question 165
An identity generates many push MFA challenges followed by one unexpected approval. What finding is the strongest distinguishing indicator for triage?
- High-frequency push denials immediately precede an accepted prompt
- Geographic separation is inconsistent with plausible physical movement
- Daily ingestion varies sharply beyond the local fixed-capacity design
- Short-window failures exceed a per-identity threshold
Explanation
Correct Answer
A:Repeated approval requests may indicate a prompt-bombing attempt or user coercion. Confirmation should then examine MFA challenge history, device binding and subsequent sign-in activity; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
B:IP geolocation is a risk signal but can be distorted by VPNs and proxies; that is suited to investigating impossible travel triage, whereas the MFA fatigue attempts case requires high-frequency push denials immediately precede an accepted prompt for recognizing the distinguishing signal.
C:A consumption-oriented service can help scale analysis but still needs cost governance, which would be relevant to cloud SIEM elasticity, but not the MFA fatigue attempts scenario that requires high-frequency push denials immediately precede an accepted prompt.
D:Time-bounded aggregation differentiates active attack bursts from scattered mistakes; applied to this MFA fatigue attempts case, it addresses authentication failure window instead of the required step: high-frequency push denials immediately precede an accepted prompt.
Question 166
To verify remediation of domain admin group change, the team reports taking this action: Escalate unauthorized membership and monitor subsequent privileged logons. Which outcome should the analyst demand?
- Malicious registration tests alert and approved system tasks remain distinguishable
- A crafted unusual-SPN test alerts without flooding on normal application tickets
- A test autorun modification is attributed correctly and removed entries stay absent
- Group membership matches the approved baseline and actor activity is reviewed
Explanation
Correct Answer
D:Reversing one change is insufficient without checking its use. It documents the result of this response step—Escalate unauthorized membership and monitor subsequent privileged logons—and helps determine whether the protective state persists.
Incorrect Answers
A:For scheduled task persistence, a periodic executable alert does not demonstrate task-creation visibility; here the narrower objective is demonstrating that the remediation or control took effect in domain admin group change, best addressed by group membership matches the approved baseline and actor activity is reviewed.
B:The rule should measure identity-specific behavior rather than raw volume; applied to this domain admin group change case, it addresses Kerberos ticket anomaly instead of the required step: group membership matches the approved baseline and actor activity is reviewed.
C:Monitoring must capture both creation and later modifications, which would be relevant to run key persistence, but not the domain admin group change scenario that requires group membership matches the approved baseline and actor activity is reviewed.
Question 167
A standard user receives HTTP 200 for administrator-only API resources after changing an object ID. What finding is the strongest distinguishing indicator for triage?
- SQL metacharacters coincide with database behavior change or errors
- Known token identity appears from an unapproved client origin and action set
- A low-privilege identity successfully accesses a forbidden object
- Crash bursts align with malformed inputs and suspicious process behavior
Explanation
Correct Answer
C:Authorization failure is proven by the resource policy and success, not by URL pattern alone. Investigators should still corroborate it with API access logs joined to role entitlements and object ownership before assigning definitive scope or attribution.
Incorrect Answers
A:A request payload alone is not proof of successful query manipulation; applied to this broken access control case, it addresses SQL injection detection instead of the required step: a low-privilege identity successfully accesses a forbidden object.
B:Bearer token misuse may bypass password-alert patterns; this evidence or action is associated with API token misuse, whereas the case concerns broken access control and calls for a low-privilege identity successfully accesses a forbidden object.
D:For application crash exploitation, repeated faults can indicate attempted exploitation but need corroboration; here the narrower objective is recognizing the distinguishing signal in broken access control, best addressed by a low-privilege identity successfully accesses a forbidden object.
Question 168
To verify remediation of Google SecOps investigation, the team reports taking this action: Ingest and map relevant logs then test behavioral detections in Google SecOps. Which outcome should the analyst demand?
- A test attack sequence correlates to an explainable detection with linked evidence
- Cross-cloud alerts correlate while restricted raw evidence stays in approved locations
- A known suspicious sign-in produces an incident with correct user and IP entities
- Sample findings from all in-scope accounts are visible to authorized analysts
- A controlled misconfiguration yields a traceable finding with resource ownership
Explanation
Correct Answer
A:Connected log sources without matching analytics are incomplete. The measure should be evaluated against the actual action, ingest and map relevant logs then test behavioral detections in Google SecOps, rather than against ticket status.
Incorrect Answers
B:Confirm both SOC utility and data handling compliance; that is suited to investigating multi-cloud log residency, whereas the Google SecOps investigation case requires a test attack sequence correlates to an explainable detection with linked evidence for demonstrating that the remediation or control took effect.
C:Testing ingestion alone does not validate incident generation; that is suited to investigating Microsoft Sentinel analytic, whereas the Google SecOps investigation case requires a test attack sequence correlates to an explainable detection with linked evidence for demonstrating that the remediation or control took effect.
D:This relates to AWS Security Hub aggregation: a dashboard showing only one account could mask gaps; the Google SecOps investigation question instead requires demonstrating that the remediation or control took effect, specifically a test attack sequence correlates to an explainable detection with linked evidence.
E:Finding visibility should be tested at intended organization scope; applied to this Google SecOps investigation case, it addresses GCP Security Command Center instead of the required step: a test attack sequence correlates to an explainable detection with linked evidence.
Question 169
A responder investigating disk forensic imaging has corroborated this finding: Direct examination of a writable original risks changing evidence. What action belongs next in the approved workflow?
- Reconstruct the session and correlate with server and endpoint artifacts
- Create and verify a forensic image using controlled read-only acquisition
- Build a sourced timeline that marks uncertain or inferred timestamps
- Seal and label the device and document each authorized transfer
Explanation
Correct Answer
B:Ordinary file copying can omit deleted data and filesystem structures. For safe case progression, preserve the evidence and later verify image verification matches acquisition expectations and source remains protected.
Incorrect Answers
A:Do not claim decrypted content from encrypted packets without keys, which would be relevant to network packet evidence, but not the disk forensic imaging scenario that requires create and verify a forensic image using controlled read-only acquisition.
C:For forensic timeline, a story based only on file modification time may misorder execution; here the narrower objective is choosing the immediate operational response in disk forensic imaging, best addressed by create and verify a forensic image using controlled read-only acquisition.
D:The alternative concerns chain of custody: an unlabeled device handed across desks invites mix-ups and challenge; however, the described disk forensic imaging situation calls for create and verify a forensic image using controlled read-only acquisition.
Question 170
An AI assistant drafts a SIEM detection for suspicious PowerShell execution. Which THREE checks should precede production deployment? Choose THREE.
- Suppress all PowerShell activity from the entire organization
- Verify that the referenced fields exist in the current ingestion schema
- Deploy immediately because a language model produced syntactically fluent text
- Obtain human rule review and change approval with rollback criteria
- Replay known suspicious and benign process events to evaluate discrimination
- Judge rule quality only by the number of characters in its query
Explanation
Correct Answers
B:A query using invented or stale field names may compile poorly or silently miss the behavior. Field mapping must reflect real source events.
D:A responsible owner must examine detection logic, operational risk and deployment scope. Generated content does not bypass governance.
E:Positive and negative examples identify misses and false positives before analysts are burdened by production noise. Test evidence should be retained.
Incorrect Answers
A:An unrestricted exclusion defeats the objective of recognizing abuse of the scripting engine. Narrowly vetted exceptions are different.
C:Fluent text is not proof of technical correctness or safety. Automatic promotion can create coverage gaps and unexpected costs.
F:Query length has no reliable correlation with precision or recall. Behavior and measured results determine detection value.