CompTIA CySA+ (CS0-003) CS0-003 Practice Test 29
Question 280
An adversary's tactics recur with different infrastructure, forcing behavioral rather than IOC detection. 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?
- Map endpoint and network behavior to ATT&CK technique patterns and process chains
- Confirm new infrastructure still triggers the technique-based hunt with measured precision
- Correlate recurring attacker actions across campaigns despite changing IPs and domains
- Prioritize hosts exhibiting malicious behavior even without a current IOC match
Explanation
Correct Answer
B:Confirm new infrastructure still triggers the technique-based hunt with measured precision. This addresses the recorded condition: An adversary's tactics recur with different infrastructure, forcing behavioral rather than IOC detection. 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 map endpoint and network behavior to ATT&CK technique patterns and process chains 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 correlate recurring attacker actions across campaigns despite changing IPs and domains could help with diagnosing the evidence in this case. An initial diagnostic comparison does not show that the approved response worked.
D:The alternative to prioritize hosts exhibiting malicious behavior even without a current IOC match could help with choosing the immediate disposition in this case. An immediate disposition is a decision, not measured proof of final effectiveness.
Question 281
An enrichment playbook blocks all IPs returned by reputation feeds without analyst validation. The relevant initial records have already been collected; the analyst is evaluating their meaning. Initial records are available but their meaning is disputed. What analysis most directly tests the suspected cause before any claim of compromise or noncompliance?
- Simulate a benign shared-IP indicator and confirm no disruptive automatic block occurs
- Inspect SOAR decision branches and enrich candidates with ownership and flow context
- Add analyst-gated containment, risk thresholds and documented rollback for reputation actions
- Separate reputation-feed suspicion from independently confirmed malice before blocking shared IPs
Explanation
Correct Answer
D:Separate reputation-feed suspicion from independently confirmed malice before blocking shared IPs. This addresses the recorded condition: An enrichment playbook blocks all IPs returned by reputation feeds without analyst validation. 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 simulate a benign shared-IP indicator and confirm no disruptive automatic block occurs could help with proving the outcome in this case. Closure testing is appropriate after a change; it does not resolve the original unknown cause.
B:The alternative to inspect SOAR decision branches and enrich candidates with ownership and flow context 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 add analyst-gated containment, risk thresholds and documented rollback for reputation actions could help with implementing a lasting control in this case. A permanent redesign cannot establish what caused the current observation.
Question 282
An enrichment playbook blocks all IPs returned by reputation feeds without analyst validation. The team has formed a hypothesis but has not yet collected the necessary primary evidence. The analyst needs a defensible technical method to obtain the necessary source information, before deciding containment or changing permanent controls. Which method is best?
- Separate reputation-feed suspicion from independently confirmed malice before blocking shared IPs
- Disable blanket auto-block pending controlled approval for high-impact destinations
- Inspect SOAR decision branches and enrich candidates with ownership and flow context
- Simulate a benign shared-IP indicator and confirm no disruptive automatic block occurs
Explanation
Correct Answer
C:Inspect SOAR decision branches and enrich candidates with ownership and flow context. This addresses the recorded condition: An enrichment playbook blocks all IPs returned by reputation feeds without analyst validation. 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 separate reputation-feed suspicion from independently confirmed malice before blocking shared IPs 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.
B:The alternative to disable blanket auto-block pending controlled approval for high-impact destinations could help with choosing the immediate disposition in this case. A containment or prioritization decision does not provide the missing collection method.
D:The alternative to simulate a benign shared-IP indicator and confirm no disruptive automatic block occurs could help with proving the outcome in this case. A completion test assumes that collection and the necessary corrective work have already occurred.
Question 283
An enrichment playbook blocks all IPs returned by reputation feeds without analyst validation. Triage findings are documented and the incident lead must now make an operational risk decision. Security and service owners need a near-term risk decision under current constraints. Which action should take precedence now, not after system redesign?
- Add analyst-gated containment, risk thresholds and documented rollback for reputation actions
- Disable blanket auto-block pending controlled approval for high-impact destinations
- Inspect SOAR decision branches and enrich candidates with ownership and flow context
- Separate reputation-feed suspicion from independently confirmed malice before blocking shared IPs
Explanation
Correct Answer
B:Disable blanket auto-block pending controlled approval for high-impact destinations. This addresses the recorded condition: An enrichment playbook blocks all IPs returned by reputation feeds without analyst validation. It selects a proportionate immediate action from the evidence while respecting safety, availability, authorization, and preservation needs.
Incorrect Answers
A:The alternative to add analyst-gated containment, risk thresholds and documented rollback for reputation actions 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 inspect SOAR decision branches and enrich candidates with ownership and flow context 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.
D:The alternative to separate reputation-feed suspicion from independently confirmed malice before blocking shared IPs could help with diagnosing the evidence in this case. Further diagnosis alone leaves the requested near-term risk disposition undecided.
Question 284
An enrichment playbook blocks all IPs returned by reputation feeds without analyst validation. The immediate response decision has already been made and authorized. The immediate risk has been triaged and engineering must prevent recurrence. Which sustainable control corrects the underlying failure mode rather than merely collecting more evidence?
- Simulate a benign shared-IP indicator and confirm no disruptive automatic block occurs
- Inspect SOAR decision branches and enrich candidates with ownership and flow context
- Add analyst-gated containment, risk thresholds and documented rollback for reputation actions
- Disable blanket auto-block pending controlled approval for high-impact destinations
Explanation
Correct Answer
C:Add analyst-gated containment, risk thresholds and documented rollback for reputation actions. This addresses the recorded condition: An enrichment playbook blocks all IPs returned by reputation feeds without analyst validation. 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 simulate a benign shared-IP indicator and confirm no disruptive automatic block occurs 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.
B:The alternative to inspect SOAR decision branches and enrich candidates with ownership and flow context 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 disable blanket auto-block pending controlled approval for high-impact destinations 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.
Question 285
An enrichment playbook blocks all IPs returned by reputation feeds without analyst validation. The necessary response and prerequisite corrective actions have been implemented; their effectiveness remains unproven. A reviewer requests evidence of effectiveness and residual limitations after remediation. Which validation is most persuasive?
- Add analyst-gated containment, risk thresholds and documented rollback for reputation actions
- Disable blanket auto-block pending controlled approval for high-impact destinations
- Simulate a benign shared-IP indicator and confirm no disruptive automatic block occurs
- Separate reputation-feed suspicion from independently confirmed malice before blocking shared IPs
Explanation
Correct Answer
C:Simulate a benign shared-IP indicator and confirm no disruptive automatic block occurs. This addresses the recorded condition: An enrichment playbook blocks all IPs returned by reputation feeds without analyst validation. 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 add analyst-gated containment, risk thresholds and documented rollback for reputation actions 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.
B:The alternative to disable blanket auto-block pending controlled approval for high-impact destinations 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 separate reputation-feed suspicion from independently confirmed malice before blocking shared IPs could help with diagnosing the evidence in this case. An initial diagnostic comparison does not show that the approved response worked.
Question 286
A SOAR ticket workflow retries a webhook and creates three incidents for one alert. 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?
- Replay a retry scenario and prove exactly one ticket is created for the alert
- Correlate SOAR retry headers, outbound request IDs and created-ticket metadata
- Merge duplicates and stop the retried action without suppressing the underlying alert
- Trace duplicate cases to webhook retries lacking a durable incident identifier
Explanation
Correct Answer
D:Trace duplicate cases to webhook retries lacking a durable incident identifier. This addresses the recorded condition: A SOAR ticket workflow retries a webhook and creates three incidents for one alert. 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 replay a retry scenario and prove exactly one ticket is created for the alert could help with proving the outcome in this case. Closure testing is appropriate after a change; it does not resolve the original unknown cause.
B:The alternative to correlate SOAR retry headers, outbound request IDs and created-ticket metadata 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 merge duplicates and stop the retried action without suppressing the underlying alert could help with choosing the immediate disposition in this case. A risk disposition before resolving the diagnostic uncertainty can misattribute the event.
Question 287
A SOAR ticket workflow retries a webhook and creates three incidents for one alert. 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?
- Merge duplicates and stop the retried action without suppressing the underlying alert
- Correlate SOAR retry headers, outbound request IDs and created-ticket metadata
- Trace duplicate cases to webhook retries lacking a durable incident identifier
- Implement idempotency keys and bounded retry with dead-letter handling
Explanation
Correct Answer
B:Correlate SOAR retry headers, outbound request IDs and created-ticket metadata. This addresses the recorded condition: A SOAR ticket workflow retries a webhook and creates three incidents for one alert. 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 merge duplicates and stop the retried action without suppressing the underlying alert 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 trace duplicate cases to webhook retries lacking a durable incident identifier 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.
D:The alternative to implement idempotency keys and bounded retry with dead-letter handling could help with implementing a lasting control in this case. An architectural control is a later intervention, not a low-impact evidence collection method.
Question 288
A SOAR ticket workflow retries a webhook and creates three incidents for one alert. 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?
- Replay a retry scenario and prove exactly one ticket is created for the alert
- Implement idempotency keys and bounded retry with dead-letter handling
- Merge duplicates and stop the retried action without suppressing the underlying alert
- Correlate SOAR retry headers, outbound request IDs and created-ticket metadata
Explanation
Correct Answer
C:Merge duplicates and stop the retried action without suppressing the underlying alert. This addresses the recorded condition: A SOAR ticket workflow retries a webhook and creates three incidents for one alert. It selects a proportionate immediate action from the evidence while respecting safety, availability, authorization, and preservation needs.
Incorrect Answers
A:The alternative to replay a retry scenario and prove exactly one ticket is created for the alert could help with proving the outcome in this case. Testing closure before the immediate response would be premature.
B:The alternative to implement idempotency keys and bounded retry with dead-letter handling could help with implementing a lasting control in this case. A durable fix follows an immediate risk decision and may require separate change authority.
D:The alternative to correlate SOAR retry headers, outbound request IDs and created-ticket metadata 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 289
A SOAR ticket workflow retries a webhook and creates three incidents for one alert. 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?
- Implement idempotency keys and bounded retry with dead-letter handling
- Trace duplicate cases to webhook retries lacking a durable incident identifier
- Merge duplicates and stop the retried action without suppressing the underlying alert
- Replay a retry scenario and prove exactly one ticket is created for the alert
Explanation
Correct Answer
A:Implement idempotency keys and bounded retry with dead-letter handling. This addresses the recorded condition: A SOAR ticket workflow retries a webhook and creates three incidents for one alert. 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
B:The alternative to trace duplicate cases to webhook retries lacking a durable incident identifier 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 merge duplicates and stop the retried action without suppressing the underlying alert 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.
D:The alternative to replay a retry scenario and prove exactly one ticket is created for the alert 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 290
A SOAR ticket workflow retries a webhook and creates three incidents for one alert. 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?
- Correlate SOAR retry headers, outbound request IDs and created-ticket metadata
- Implement idempotency keys and bounded retry with dead-letter handling
- Replay a retry scenario and prove exactly one ticket is created for the alert
- Trace duplicate cases to webhook retries lacking a durable incident identifier
Explanation
Correct Answer
C:Replay a retry scenario and prove exactly one ticket is created for the alert. This addresses the recorded condition: A SOAR ticket workflow retries a webhook and creates three incidents for one alert. 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 correlate SOAR retry headers, outbound request IDs and created-ticket metadata 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.
B:The alternative to implement idempotency keys and bounded retry with dead-letter handling 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.
D:The alternative to trace duplicate cases to webhook retries lacking a durable incident identifier could help with diagnosing the evidence in this case. An initial diagnostic comparison does not show that the approved response worked.