CompTIA CySA+ (CS0-003) CS0-003 Practice Test 1
Question 1
Windows domain controllers and VPN concentrators disagree by nine minutes, obscuring a lateral-movement timeline. The relevant initial records have already been collected; the analyst is evaluating their meaning. At triage, analysts have conflicting explanations and must decide what evidence distinguishes them, rather than take corrective action yet. What is the best analysis?
- Hold the lateral-movement conclusion until corrected timestamps reveal session order
- Export NTP health and authentication logs from both systems against one UTC reference
- Reconcile VPN and domain-controller events using measured nine-minute offsets and immutable event IDs
- Replay the timeline after synchronization and document any still-unattributed logon sequence
Explanation
Correct Answer
C:Reconcile VPN and domain-controller events using measured nine-minute offsets and immutable event IDs. This addresses the recorded condition: Windows domain controllers and VPN concentrators disagree by nine minutes, obscuring a lateral-movement timeline. It interprets the evidence needed to decide whether the observation is malicious, benign, or a monitoring defect before another step changes the environment.
Incorrect Answers
A:The alternative to hold the lateral-movement conclusion until corrected timestamps reveal session order could help with choosing the immediate disposition in this case. A risk disposition before resolving the diagnostic uncertainty can misattribute the event.
B:The alternative to export NTP health and authentication logs from both systems against one UTC reference could help with collecting trustworthy source data in this case. Collecting additional source records can be useful, but this scenario calls for interpreting the evidence and selecting the discriminating comparison.
D:The alternative to replay the timeline after synchronization and document any still-unattributed logon sequence could help with proving the outcome in this case. Closure testing is appropriate after a change; it does not resolve the original unknown cause.
Question 2
Windows domain controllers and VPN concentrators disagree by nine minutes, obscuring a lateral-movement timeline. The team has formed a hypothesis but has not yet collected the necessary primary evidence. The lead has authorized limited data collection, not a production redesign. What technique most directly gathers the records required for this case?
- Hold the lateral-movement conclusion until corrected timestamps reveal session order
- Export NTP health and authentication logs from both systems against one UTC reference
- Enforce common authenticated time sources and alert on drift beyond the correlation tolerance
- Reconcile VPN and domain-controller events using measured nine-minute offsets and immutable event IDs
Explanation
Correct Answer
B:Export NTP health and authentication logs from both systems against one UTC reference. This addresses the recorded condition: Windows domain controllers and VPN concentrators disagree by nine minutes, obscuring a lateral-movement timeline. It obtains the records, telemetry, or controlled test outcome at the relevant technical boundary rather than assuming the records are already complete.
Incorrect Answers
A:The alternative to hold the lateral-movement conclusion until corrected timestamps reveal session order could help with choosing the immediate disposition in this case. A containment or prioritization decision does not provide the missing collection method.
C:The alternative to enforce common authenticated time sources and alert on drift beyond the correlation tolerance could help with implementing a lasting control in this case. An architectural control is a later intervention, not a low-impact evidence collection method.
D:The alternative to reconcile VPN and domain-controller events using measured nine-minute offsets and immutable event IDs could help with diagnosing the evidence in this case. An investigative comparison describes what to assess but not how the required primary records should be acquired.
Question 3
Windows domain controllers and VPN concentrators disagree by nine minutes, obscuring a lateral-movement timeline. Triage findings are documented and the incident lead must now make an operational risk decision. The investigation has reached the immediate response decision. Which disposition is most proportionate to the evidence and business impact, before designing a long-term fix?
- Enforce common authenticated time sources and alert on drift beyond the correlation tolerance
- Replay the timeline after synchronization and document any still-unattributed logon sequence
- Hold the lateral-movement conclusion until corrected timestamps reveal session order
- Export NTP health and authentication logs from both systems against one UTC reference
Explanation
Correct Answer
C:Hold the lateral-movement conclusion until corrected timestamps reveal session order. This addresses the recorded condition: Windows domain controllers and VPN concentrators disagree by nine minutes, obscuring a lateral-movement timeline. It selects a proportionate immediate action from the evidence while respecting safety, availability, authorization, and preservation needs.
Incorrect Answers
A:The alternative to enforce common authenticated time sources and alert on drift beyond the correlation tolerance could help with implementing a lasting control in this case. A durable fix follows an immediate risk decision and may require separate change authority.
B:The alternative to replay the timeline after synchronization and document any still-unattributed logon sequence could help with proving the outcome in this case. Testing closure before the immediate response would be premature.
D:The alternative to export NTP health and authentication logs from both systems against one UTC reference could help with collecting trustworthy source data in this case. Collecting another dataset can inform the decision but does not select the proportionate operational response.
Question 4
Windows domain controllers and VPN concentrators disagree by nine minutes, obscuring a lateral-movement timeline. The immediate response decision has already been made and authorized. The incident or finding is stabilized. The team is selecting a durable preventive design that respects legitimate business operation. Which change best fits?
- Hold the lateral-movement conclusion until corrected timestamps reveal session order
- Enforce common authenticated time sources and alert on drift beyond the correlation tolerance
- Replay the timeline after synchronization and document any still-unattributed logon sequence
- Reconcile VPN and domain-controller events using measured nine-minute offsets and immutable event IDs
Explanation
Correct Answer
B:Enforce common authenticated time sources and alert on drift beyond the correlation tolerance. This addresses the recorded condition: Windows domain controllers and VPN concentrators disagree by nine minutes, obscuring a lateral-movement timeline. It changes the underlying access path, control, collection capability, or process so the same failure does not recur simply after the ticket closes.
Incorrect Answers
A:The alternative to hold the lateral-movement conclusion until corrected timestamps reveal session order could help with choosing the immediate disposition in this case. A temporary or immediate disposition may lower risk now without providing a durable corrective control.
C:The alternative to replay the timeline after synchronization and document any still-unattributed logon sequence could help with proving the outcome in this case. A validation step is needed after a sustained control exists, not in place of designing it.
D:The alternative to reconcile VPN and domain-controller events using measured nine-minute offsets and immutable event IDs could help with diagnosing the evidence in this case. Evidence analysis helps establish the cause but does not implement a prevention measure.
Question 5
Windows domain controllers and VPN concentrators disagree by nine minutes, obscuring a lateral-movement timeline. The necessary response and prerequisite corrective actions have been implemented; their effectiveness remains unproven. Management will accept closure only with a demonstrated result, not a claimed fix. Which follow-up check best verifies the security outcome?
- Reconcile VPN and domain-controller events using measured nine-minute offsets and immutable event IDs
- Export NTP health and authentication logs from both systems against one UTC reference
- Enforce common authenticated time sources and alert on drift beyond the correlation tolerance
- Replay the timeline after synchronization and document any still-unattributed logon sequence
Explanation
Correct Answer
D:Replay the timeline after synchronization and document any still-unattributed logon sequence. This addresses the recorded condition: Windows domain controllers and VPN concentrators disagree by nine minutes, obscuring a lateral-movement timeline. It demonstrates that the corrective decision achieved its intended effect, identifies any remaining uncertainty and provides auditable closure evidence.
Incorrect Answers
A:The alternative to reconcile VPN and domain-controller events using measured nine-minute offsets and immutable event IDs could help with diagnosing the evidence in this case. An initial diagnostic comparison does not show that the approved response worked.
B:The alternative to export NTP health and authentication logs from both systems against one UTC reference could help with collecting trustworthy source data in this case. A collection technique gathers information but alone does not prove the intended post-change outcome.
C:The alternative to enforce common authenticated time sources and alert on drift beyond the correlation tolerance could help with implementing a lasting control in this case. A preventive design may be sound but does not prove that it was implemented and tested.
Question 6
Container workloads are destroyed after autoscaling before security events reach the collector. The relevant initial records have already been collected; the analyst is evaluating their meaning. The case has not yet been attributed to a cause. Which targeted comparison most directly resolves the key evidentiary uncertainty?
- Preserve available runtime events and prioritize workloads that disappeared before ingestion
- Use a DaemonSet log forwarder with durable buffering and orchestration audit events
- Move security telemetry to lifecycle-independent centralized storage with delivery acknowledgments
- Match pod lifecycle IDs to collector ingestion gaps around each autoscaling termination
Explanation
Correct Answer
D:Match pod lifecycle IDs to collector ingestion gaps around each autoscaling termination. This addresses the recorded condition: Container workloads are destroyed after autoscaling before security events reach the collector. It interprets the evidence needed to decide whether the observation is malicious, benign, or a monitoring defect before another step changes the environment.
Incorrect Answers
A:The alternative to preserve available runtime events and prioritize workloads that disappeared before ingestion could help with choosing the immediate disposition in this case. A risk disposition before resolving the diagnostic uncertainty can misattribute the event.
B:The alternative to use a DaemonSet log forwarder with durable buffering and orchestration audit events could help with collecting trustworthy source data in this case. Collecting additional source records can be useful, but this scenario calls for interpreting the evidence and selecting the discriminating comparison.
C:The alternative to move security telemetry to lifecycle-independent centralized storage with delivery acknowledgments could help with implementing a lasting control in this case. A permanent redesign cannot establish what caused the current observation.
Question 7
Container workloads are destroyed after autoscaling before security events reach the collector. The team has formed a hypothesis but has not yet collected the necessary primary evidence. Investigators have agreed on the hypothesis but still need suitable primary records. Which scoped collection method will best establish facts with minimal disruption?
- Use a DaemonSet log forwarder with durable buffering and orchestration audit events
- Kill a test pod and confirm its final events arrive once with workload identity attached
- Move security telemetry to lifecycle-independent centralized storage with delivery acknowledgments
- Preserve available runtime events and prioritize workloads that disappeared before ingestion
Explanation
Correct Answer
A:Use a DaemonSet log forwarder with durable buffering and orchestration audit events. This addresses the recorded condition: Container workloads are destroyed after autoscaling before security events reach the collector. It obtains the records, telemetry, or controlled test outcome at the relevant technical boundary rather than assuming the records are already complete.
Incorrect Answers
B:The alternative to kill a test pod and confirm its final events arrive once with workload identity attached could help with proving the outcome in this case. A completion test assumes that collection and the necessary corrective work have already occurred.
C:The alternative to move security telemetry to lifecycle-independent centralized storage with delivery acknowledgments could help with implementing a lasting control in this case. An architectural control is a later intervention, not a low-impact evidence collection method.
D:The alternative to preserve available runtime events and prioritize workloads that disappeared before ingestion could help with choosing the immediate disposition in this case. A containment or prioritization decision does not provide the missing collection method.
Question 8
Container workloads are destroyed after autoscaling before security events reach the collector. Triage findings are documented and the incident lead must now make an operational risk decision. Responders must choose the next operational action, distinguishing confirmed exposure from an unproven suspicion. Which immediate response is most appropriate?
- Move security telemetry to lifecycle-independent centralized storage with delivery acknowledgments
- Preserve available runtime events and prioritize workloads that disappeared before ingestion
- Match pod lifecycle IDs to collector ingestion gaps around each autoscaling termination
- Kill a test pod and confirm its final events arrive once with workload identity attached
Explanation
Correct Answer
B:Preserve available runtime events and prioritize workloads that disappeared before ingestion. This addresses the recorded condition: Container workloads are destroyed after autoscaling before security events reach the collector. It selects a proportionate immediate action from the evidence while respecting safety, availability, authorization, and preservation needs.
Incorrect Answers
A:The alternative to move security telemetry to lifecycle-independent centralized storage with delivery acknowledgments could help with implementing a lasting control in this case. A durable fix follows an immediate risk decision and may require separate change authority.
C:The alternative to match pod lifecycle IDs to collector ingestion gaps around each autoscaling termination could help with diagnosing the evidence in this case. Further diagnosis alone leaves the requested near-term risk disposition undecided.
D:The alternative to kill a test pod and confirm its final events arrive once with workload identity attached could help with proving the outcome in this case. Testing closure before the immediate response would be premature.
Question 9
Container workloads are destroyed after autoscaling before security events reach the collector. The immediate response decision has already been made and authorized. With the acute response complete, engineering can change policy or architecture. Which enduring control is most directly linked to this root cause?
- Match pod lifecycle IDs to collector ingestion gaps around each autoscaling termination
- Move security telemetry to lifecycle-independent centralized storage with delivery acknowledgments
- Use a DaemonSet log forwarder with durable buffering and orchestration audit events
- Kill a test pod and confirm its final events arrive once with workload identity attached
Explanation
Correct Answer
B:Move security telemetry to lifecycle-independent centralized storage with delivery acknowledgments. This addresses the recorded condition: Container workloads are destroyed after autoscaling before security events reach the collector. It changes the underlying access path, control, collection capability, or process so the same failure does not recur simply after the ticket closes.
Incorrect Answers
A:The alternative to match pod lifecycle IDs to collector ingestion gaps around each autoscaling termination could help with diagnosing the evidence in this case. Evidence analysis helps establish the cause but does not implement a prevention measure.
C:The alternative to use a DaemonSet log forwarder with durable buffering and orchestration audit events could help with collecting trustworthy source data in this case. A data-gathering method improves visibility but does not itself eliminate the recurring mechanism.
D:The alternative to kill a test pod and confirm its final events arrive once with workload identity attached could help with proving the outcome in this case. A validation step is needed after a sustained control exists, not in place of designing it.
Question 10
Container workloads are destroyed after autoscaling before security events reach the collector. The necessary response and prerequisite corrective actions have been implemented; their effectiveness remains unproven. The response or authorized change is complete. Which specific outcome test best supports closure instead of relying on a ticket-status update?
- Use a DaemonSet log forwarder with durable buffering and orchestration audit events
- Kill a test pod and confirm its final events arrive once with workload identity attached
- Preserve available runtime events and prioritize workloads that disappeared before ingestion
- Match pod lifecycle IDs to collector ingestion gaps around each autoscaling termination
Explanation
Correct Answer
B:Kill a test pod and confirm its final events arrive once with workload identity attached. This addresses the recorded condition: Container workloads are destroyed after autoscaling before security events reach the collector. It demonstrates that the corrective decision achieved its intended effect, identifies any remaining uncertainty and provides auditable closure evidence.
Incorrect Answers
A:The alternative to use a DaemonSet log forwarder with durable buffering and orchestration audit events could help with collecting trustworthy source data in this case. A collection technique gathers information but alone does not prove the intended post-change outcome.
C:The alternative to preserve available runtime events and prioritize workloads that disappeared before ingestion could help with choosing the immediate disposition in this case. An immediate disposition is a decision, not measured proof of final effectiveness.
D:The alternative to match pod lifecycle IDs to collector ingestion gaps around each autoscaling termination could help with diagnosing the evidence in this case. An initial diagnostic comparison does not show that the approved response worked.