Question 1
A SOC analyst is investigating log retention tiers and records this observation: Hot search and long-term archive need distinct retention policies. Which source or comparison would most directly corroborate it?
- Retention schedule, immutable archive settings and retrieval procedures
- Raw CEF sample compared with extracted deviceEventClassId and source fields
- Raw timestamp, time-zone offset, ingest time and NTP health
- Collector receipt metadata, immutable storage controls and hashes
Explanation
Correct Answer
A:Searchability and legal preservation are separate operational requirements. This is particularly useful after the initial sign of hot search and long-term archive need distinct retention policies; the two forms of evidence test different parts of the case.
Incorrect Answers
B:The mapping reveals whether the parser handles escaped delimiters and extensions, which would be relevant to CEF parsing, but not the log retention tiers scenario that requires retention schedule, immutable archive settings and retrieval procedures.
C:For timestamp normalization, distinguishing source time from collection time exposes drift and parser errors; here the narrower objective is independently corroborating the suspected behavior in log retention tiers, best addressed by retention schedule, immutable archive settings and retrieval procedures.
D:This relates to log integrity: provenance and tamper resistance strengthen the reliability of subsequent investigation; the log retention tiers question instead requires independently corroborating the suspected behavior, specifically retention schedule, immutable archive settings and retrieval procedures.
Question 2
The working evidence for cloud shared responsibility includes this observation: Cloud provider platform security does not remove customer identity-configuration duties. Which intervention is the best fit for the established finding?
- Correct least-privilege access and monitor use of service identities
- Enable appropriate SCC services and route high-risk findings into SOC workflow
- Design region-appropriate collection with normalized central findings where allowed
- Investigate the activation and enforce appropriate privileged access policy
Explanation
Correct Answer
A:Demanding host hypervisor logs from the provider would not fix tenant grants. The response must subsequently be checked by confirming unauthorized database access fails and approved application operations remain functional; otherwise the original exposure may persist.
Incorrect Answers
B:For GCP Security Command Center, a generic log sink alone does not organize posture findings; here the narrower objective is choosing the immediate operational response in cloud shared responsibility, best addressed by correct least-privilege access and monitor use of service identities.
C:A universal export rule can conflict with residency obligations; prioritizing that multi-cloud log residency mechanism would leave this cloud shared responsibility decision unresolved because correct least-privilege access and monitor use of service identities is the direct fit.
D:Rotating a storage account key would not constrain directory role activation; applied to this cloud shared responsibility case, it addresses Azure privileged identity instead of the required step: correct least-privilege access and monitor use of service identities.
Question 3
A SIEM case includes network, endpoint and identity events recorded in different time zones. Supporting evidence includes: Original event time, UTC normalization and collection timestamps. Which next step most directly reduces the described risk?
- Keep the incident open until remediation, validation and ownership are recorded
- Restore the rule at the approved deadline and test for renewed signal
- Build a unified timeline and note uncertain source clocks explicitly
- Attach the supporting indicators and specific containment request to the case
Explanation
Correct Answer
C:Sorting by ingestion time alone can fabricate an incorrect chain of events. Operational success is not assumed until a known sequence from test hosts is represented in correct causal order, the relevant outcome for this response.
Incorrect Answers
A:Reducing ticket backlog is not a substitute for security restoration; this evidence or action is associated with case closure standard, whereas the case concerns case evidence timeline and calls for build a unified timeline and note uncertain source clocks explicitly.
B:Deleting alert history does not close the original risk; that is suited to investigating rule suppression expiry, whereas the case evidence timeline case requires build a unified timeline and note uncertain source clocks explicitly for choosing the immediate operational response.
D:The alternative concerns ticket escalation evidence: escalation should pass an actionable decision rather than merely a notification; however, the described case evidence timeline situation calls for build a unified timeline and note uncertain source clocks explicitly.
Question 4
Responders addressed living-off-the-land binaries using this measure: Build behavior-focused detection for the specific binary and suspicious arguments. What should the SOC test before considering closure?
- A controlled test service triggers while approved installer activity is classified
- Authorized admin commands remain permitted while external payload retrieval alerts
- The detection catches controlled test chains without flagging routine document opens
- Test payloads are detected using parent and script behavior rather than encoding alone
Explanation
Correct Answer
B:Overbroad blocking can punish routine operating system maintenance. It documents the result of this response step—Build behavior-focused detection for the specific binary and suspicious arguments—and helps determine whether the protective state persists.
Incorrect Answers
A:Service name randomness alone should not determine maliciousness; this evidence or action is associated with service-based execution, whereas the case concerns living-off-the-land binaries and calls for authorized admin commands remain permitted while external payload retrieval alerts.
C:This relates to office child process: parent-child conditions should discriminate malicious automation from normal workflows; the living-off-the-land binaries question instead requires demonstrating that the remediation or control took effect, specifically authorized admin commands remain permitted while external payload retrieval alerts.
D:A simple Base64 keyword rule is both bypassable and noisy; applied to this living-off-the-land binaries case, it addresses encoded PowerShell instead of the required step: authorized admin commands remain permitted while external payload retrieval alerts.
Question 5
Endpoint logs arrive several hours late after a collector's disk fills during a traffic spike. What finding is the strongest distinguishing indicator for triage?
- An increasing queue age indicates delayed security-event visibility
- CEF header and extension key-value fields were not parsed into schema
- Mixed local timestamps without consistent time-zone interpretation
- Best-effort UDP syslog can lose messages during congestion
Explanation
Correct Answer
A:Ingestion lag can hide urgent events even when the source is generating logs. The follow-up evidence is forwarder queue depth, disk utilization and event-to-ingest latency, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
B:For CEF parsing, unparsed structured messages cannot support reliable field-based correlation; here the narrower objective is recognizing the distinguishing signal in collector backlog monitoring, best addressed by an increasing queue age indicates delayed security-event visibility.
C:Chronological investigations fail when event times are normalized incorrectly; this evidence or action is associated with timestamp normalization, whereas the case concerns collector backlog monitoring and calls for an increasing queue age indicates delayed security-event visibility.
D:Traditional UDP transport provides no built-in delivery acknowledgement; that is suited to investigating Syslog transport reliability, whereas the collector backlog monitoring case requires an increasing queue age indicates delayed security-event visibility for recognizing the distinguishing signal.
Question 6
The first-line team is investigating AWS Security Hub aggregation. Its preliminary finding is: Security findings reside in several services and AWS accounts. What corroborating material is most decisive?
- CloudTrail eventName, userIdentity, sourceIPAddress and requestParameters
- GuardDuty finding details plus VPC and workload activity context
- Sentinel workspace data tables, connector status and analytic rule query
- Activity Log operation, caller, scope and result fields
- Security Hub finding provider, account, region and compliance status
Explanation
Correct Answer
E:Account and region enrollment determine whether aggregation is complete. This is particularly useful after the initial sign of security findings reside in several services and AWS accounts; the two forms of evidence test different parts of the case.
Incorrect Answers
A:The alternative concerns CloudTrail administrative audit: these fields identify which actor requested the privilege change; however, the described AWS Security Hub aggregation situation calls for security Hub finding provider, account, region and compliance status.
B:An enriched finding must still be validated against actual affected assets; that is suited to investigating GuardDuty compromise finding, whereas the AWS Security Hub aggregation case requires security Hub finding provider, account, region and compliance status for independently corroborating the suspected behavior.
C:Correct data ingestion and schema mapping are prerequisites for an effective rule; prioritizing that Microsoft Sentinel analytic mechanism would leave this AWS Security Hub aggregation decision unresolved because security Hub finding provider, account, region and compliance status is the direct fit.
D:This relates to Azure activity log visibility: these fields support attribution of resource administration actions; the AWS Security Hub aggregation question instead requires independently corroborating the suspected behavior, specifically security Hub finding provider, account, region and compliance status.
Question 7
The first-line team is investigating collection outage ownership. Its preliminary finding is: Ingestion freshness has breached the data-collection health threshold. What corroborating material is most decisive?
- Ticket cross-references, assignment history, and on-call roster
- The current case timeline, pending actions, and shift-transfer acknowledgement
- Intrusion timeline and timestamp of earliest defensible alert
- Collector heartbeat, event-time lag, and queue backlog telemetry
Explanation
Correct Answer
D:These signals separate source silence from transport or indexing failures. Linking these records back to ingestion freshness has breached the data-collection health threshold reduces reliance on an isolated indicator.
Incorrect Answers
A:This relates to incident ownership: ownership must be determined from workflow records rather than from who first viewed the alert; the collection outage ownership question instead requires independently corroborating the suspected behavior, specifically collector heartbeat, event-time lag, and queue backlog telemetry.
B:The alternative concerns follow-the-sun transfer: a complete handover includes hypotheses, collected evidence, decisions and deadlines; however, the described collection outage ownership situation calls for collector heartbeat, event-time lag, and queue backlog telemetry.
C:The gap can be measured only if onset and detection evidence are both established; this evidence or action is associated with mean time to detect, whereas the case concerns collection outage ownership and calls for collector heartbeat, event-time lag, and queue backlog telemetry.
Question 8
The SOC has completed this action: Alert on unexpected account creation and review role assignments. Which result provides the strongest assurance that the specific problem was addressed?
- Required audit subcategories are active and representative events reach collectors
- The service resumes authentication without new unexpected lockout events
- Authorized membership changes are traceable and unapproved additions are reversed
- An approved provisioning test is logged and unauthorized new accounts are investigated
Explanation
Correct Answer
D:Account creation events should be contextualized with change requests. That verification specifically tests whether the intervention to alert on unexpected account creation and review role assignments corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:For Windows policy change, effective state and ingestion must both be tested after remediation; here the narrower objective is demonstrating that the remediation or control took effect in Windows account created, best addressed by an approved provisioning test is logged and unauthorized new accounts are investigated.
B:A successful unlock alone does not establish that the triggering condition ended; this evidence or action is associated with Windows account lockouts, whereas the case concerns Windows account created and calls for an approved provisioning test is logged and unauthorized new accounts are investigated.
C:Success requires validating actual directory group membership; that is suited to investigating Windows group membership, whereas the Windows account created case requires an approved provisioning test is logged and unauthorized new accounts are investigated for demonstrating that the remediation or control took effect.
Question 9
To verify remediation of legal hold preservation, the team reports taking this action: Coordinate with legal and preserve specified records with controlled access. Which outcome should the analyst demand?
- Held records remain recoverable with documented custody and access auditing
- The assessment, required notices and containment outcomes have accountable owners
- CSIRT acknowledges ownership and the SOC continues relevant monitoring
- Follow-up tests demonstrate completed corrections and tracked residual risks
Explanation
Correct Answer
A:A screenshot is not a substitute for protected original records. The measure should be evaluated against the actual action, coordinate with legal and preserve specified records with controlled access, rather than against ticket status.
Incorrect Answers
B:Technical cleanup alone does not discharge governance obligations; that is suited to investigating privacy impact escalation, whereas the legal hold preservation case requires held records remain recoverable with documented custody and access auditing for demonstrating that the remediation or control took effect.
C:This relates to SOC to CSIRT transfer: escalation should preserve both handoff and ongoing detection; the legal hold preservation question instead requires demonstrating that the remediation or control took effect, specifically held records remain recoverable with documented custody and access auditing.
D:A completed slide deck is not evidence of operational improvement; this evidence or action is associated with postincident review, whereas the case concerns legal hold preservation and calls for held records remain recoverable with documented custody and access auditing.
Question 10
A privileged account establishes a remote session on a jump host outside its normal working hours. Which observation most directly identifies the concern that needs investigation?
- Windows Security event 4625 reflects failed logon attempts
- Windows Security event 4624 records a successful logon
- Security event 1102 denotes a cleared Security audit log
- Security event 4648 records an attempted logon with explicit credentials
Explanation
Correct Answer
B:Its logon type and account fields help distinguish interactive and network access. The follow-up evidence is event 4624 logon type, authentication package and source host correlation, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
A:The event records unsuccessful authentication and may include status, workstation and source network fields; that is suited to investigating Windows failed logons, whereas the Windows successful logons case requires Windows Security event 4624 records a successful logon for recognizing the distinguishing signal.
C:This high-value administrative action can obscure earlier security evidence; prioritizing that Windows audit log cleared mechanism would leave this Windows successful logons decision unresolved because Windows Security event 4624 records a successful logon is the direct fit.
D:For Windows explicit credentials, it indicates explicit credential use and should be interpreted alongside target authentication results; here the narrower objective is recognizing the distinguishing signal in Windows successful logons, best addressed by Windows Security event 4624 records a successful logon.