Question 100
During Willow Retail's post-change review, incident containment workflow was selected to stop verified ransomware from spreading through an enterprise segment. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- An unverified backup can reintroduce malware and persistence.
- A confidence score alone is not proof that the account is compromised.
- Restoring network access before validating eradication invites reinfection.
- Deleting the original alert does not isolate a compromised host.
Explanation
Correct Answer
D:The residual risk for this case is that deleting the original alert does not isolate a compromised host. This matters even after the measure to stop verified ransomware from spreading through an enterprise segment appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to incident recovery workflow under the different requirement to restore a formerly infected host to production safely. The current case instead requires managing the risk that deleting the original alert does not isolate a compromised host.
B:That caution belongs to incident confirmation workflow under the different requirement to avoid blocking a production asset based only on a low-confidence model anomaly. The current case instead requires managing the risk that deleting the original alert does not isolate a compromised host.
C:That caution belongs to incident eradication workflow under the different requirement to remove attacker persistence following endpoint containment. The current case instead requires managing the risk that deleting the original alert does not isolate a compromised host.
Question 101
Northstar Manufacturing's security operations team must remove attacker persistence following endpoint containment. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- Incident eradication workflow
- Incident containment workflow
- Incident recovery workflow
- Incident confirmation workflow
Explanation
Correct Answer
A:Incident eradication workflow addresses this case because the team should identify and remove the malicious mechanism and close its exploited access path. The direct verification is that post-remediation scanning and startup-task inspection show the cause removed.
Incorrect Answers
B:Incident containment workflow would address a different operational issue: stop verified ransomware from spreading through an enterprise segment. The separate task is to isolate confirmed affected endpoints using approved containment steps, rather than the requested outcome to remove attacker persistence following endpoint containment.
C:Incident recovery workflow would address a different operational issue: restore a formerly infected host to production safely. The separate task is to restore a known-good image verify fixes and monitor after controlled reconnection, rather than the requested outcome to remove attacker persistence following endpoint containment.
D:Incident confirmation workflow would address a different operational issue: avoid blocking a production asset based only on a low-confidence model anomaly. The separate task is to correlate the model alert with independent host or network evidence first, rather than the requested outcome to remove attacker persistence following endpoint containment.
Question 102
An authorized responder at Meridian Analytics has selected the incident eradication workflow approach to remove attacker persistence following endpoint containment. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Isolate confirmed affected endpoints using approved containment steps.
- Identify and remove the malicious mechanism and close its exploited access path.
- Restore a known-good image verify fixes and monitor after controlled reconnection.
- Correlate the model alert with independent host or network evidence first.
Explanation
Correct Answer
B:To remove attacker persistence following endpoint containment, this step operationalizes incident eradication workflow. In particular, identify and remove the malicious mechanism and close its exploited access path; acceptance requires that post-remediation scanning and startup-task inspection show the cause removed.
Incorrect Answers
A:This step implements incident containment workflow, aimed at stop verified ransomware from spreading through an enterprise segment. It does not carry out the needed step for incident eradication workflow, where responders must identify and remove the malicious mechanism and close its exploited access path.
C:This step implements incident recovery workflow, aimed at restore a formerly infected host to production safely. It does not carry out the needed step for incident eradication workflow, where responders must identify and remove the malicious mechanism and close its exploited access path.
D:This step implements incident confirmation workflow, aimed at avoid blocking a production asset based only on a low-confidence model anomaly. It does not carry out the needed step for incident eradication workflow, where responders must identify and remove the malicious mechanism and close its exploited access path.
Question 103
Highland Operations has performed this action as part of incident eradication workflow: Identify and remove the malicious mechanism and close its exploited access path. The requirement is to remove attacker persistence following endpoint containment. Which observation actually confirms the intended result?
- EDR containment state and east-west network observations show reduced reachability.
- Functional checks patch state and enhanced monitoring are documented.
- Post-remediation scanning and startup-task inspection show the cause removed.
- Case status documents true-positive assessment and corroborating artifacts.
Explanation
Correct Answer
C:The relevant acceptance signal is that post-remediation scanning and startup-task inspection show the cause removed. It verifies the requested result to remove attacker persistence following endpoint containment rather than merely measuring unrelated activity.
Incorrect Answers
A:This is an acceptance observation for incident containment workflow, which deals with stop verified ransomware from spreading through an enterprise segment. It does not verify that post-remediation scanning and startup-task inspection show the cause removed in the specified case.
B:This is an acceptance observation for incident recovery workflow, which deals with restore a formerly infected host to production safely. It does not verify that post-remediation scanning and startup-task inspection show the cause removed in the specified case.
D:This is an acceptance observation for incident confirmation workflow, which deals with avoid blocking a production asset based only on a low-confidence model anomaly. It does not verify that post-remediation scanning and startup-task inspection show the cause removed in the specified case.
Question 104
During Lakeside Finance's post-change review, incident eradication workflow was selected to remove attacker persistence following endpoint containment. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- Deleting the original alert does not isolate a compromised host.
- An unverified backup can reintroduce malware and persistence.
- A confidence score alone is not proof that the account is compromised.
- Restoring network access before validating eradication invites reinfection.
Explanation
Correct Answer
D:The residual risk for this case is that restoring network access before validating eradication invites reinfection. This matters even after the measure to remove attacker persistence following endpoint containment appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to incident containment workflow under the different requirement to stop verified ransomware from spreading through an enterprise segment. The current case instead requires managing the risk that restoring network access before validating eradication invites reinfection.
B:That caution belongs to incident recovery workflow under the different requirement to restore a formerly infected host to production safely. The current case instead requires managing the risk that restoring network access before validating eradication invites reinfection.
C:That caution belongs to incident confirmation workflow under the different requirement to avoid blocking a production asset based only on a low-confidence model anomaly. The current case instead requires managing the risk that restoring network access before validating eradication invites reinfection.
Question 105
Cedar Health's security operations team must restore a formerly infected host to production safely. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- Incident recovery workflow
- Incident eradication workflow
- Incident containment workflow
- Incident confirmation workflow
Explanation
Correct Answer
A:Incident recovery workflow addresses this case because the team should restore a known-good image verify fixes and monitor after controlled reconnection. The direct verification is that functional checks patch state and enhanced monitoring are documented.
Incorrect Answers
B:Incident eradication workflow would address a different operational issue: remove attacker persistence following endpoint containment. The separate task is to identify and remove the malicious mechanism and close its exploited access path, rather than the requested outcome to restore a formerly infected host to production safely.
C:Incident containment workflow would address a different operational issue: stop verified ransomware from spreading through an enterprise segment. The separate task is to isolate confirmed affected endpoints using approved containment steps, rather than the requested outcome to restore a formerly infected host to production safely.
D:Incident confirmation workflow would address a different operational issue: avoid blocking a production asset based only on a low-confidence model anomaly. The separate task is to correlate the model alert with independent host or network evidence first, rather than the requested outcome to restore a formerly infected host to production safely.
Question 106
An authorized responder at Mariner Logistics has selected the incident recovery workflow approach to restore a formerly infected host to production safely. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Identify and remove the malicious mechanism and close its exploited access path.
- Restore a known-good image verify fixes and monitor after controlled reconnection.
- Isolate confirmed affected endpoints using approved containment steps.
- Correlate the model alert with independent host or network evidence first.
Explanation
Correct Answer
B:To restore a formerly infected host to production safely, this step operationalizes incident recovery workflow. In particular, restore a known-good image verify fixes and monitor after controlled reconnection; acceptance requires that functional checks patch state and enhanced monitoring are documented.
Incorrect Answers
A:This step implements incident eradication workflow, aimed at remove attacker persistence following endpoint containment. It does not carry out the needed step for incident recovery workflow, where responders must restore a known-good image verify fixes and monitor after controlled reconnection.
C:This step implements incident containment workflow, aimed at stop verified ransomware from spreading through an enterprise segment. It does not carry out the needed step for incident recovery workflow, where responders must restore a known-good image verify fixes and monitor after controlled reconnection.
D:This step implements incident confirmation workflow, aimed at avoid blocking a production asset based only on a low-confidence model anomaly. It does not carry out the needed step for incident recovery workflow, where responders must restore a known-good image verify fixes and monitor after controlled reconnection.
Question 107
Pioneer Research has performed this action as part of incident recovery workflow: Restore a known-good image verify fixes and monitor after controlled reconnection. The requirement is to restore a formerly infected host to production safely. Which observation actually confirms the intended result?
- Post-remediation scanning and startup-task inspection show the cause removed.
- EDR containment state and east-west network observations show reduced reachability.
- Functional checks patch state and enhanced monitoring are documented.
- Case status documents true-positive assessment and corroborating artifacts.
Explanation
Correct Answer
C:The relevant acceptance signal is that functional checks patch state and enhanced monitoring are documented. It verifies the requested result to restore a formerly infected host to production safely rather than merely measuring unrelated activity.
Incorrect Answers
A:This is an acceptance observation for incident eradication workflow, which deals with remove attacker persistence following endpoint containment. It does not verify that functional checks patch state and enhanced monitoring are documented in the specified case.
B:This is an acceptance observation for incident containment workflow, which deals with stop verified ransomware from spreading through an enterprise segment. It does not verify that functional checks patch state and enhanced monitoring are documented in the specified case.
D:This is an acceptance observation for incident confirmation workflow, which deals with avoid blocking a production asset based only on a low-confidence model anomaly. It does not verify that functional checks patch state and enhanced monitoring are documented in the specified case.
Question 108
During Willow Retail's post-change review, incident recovery workflow was selected to restore a formerly infected host to production safely. The primary implementation looks successful. Which remaining limitation or failure mode is directly relevant to this specific approach?
- Restoring network access before validating eradication invites reinfection.
- Deleting the original alert does not isolate a compromised host.
- A confidence score alone is not proof that the account is compromised.
- An unverified backup can reintroduce malware and persistence.
Explanation
Correct Answer
D:The residual risk for this case is that an unverified backup can reintroduce malware and persistence. This matters even after the measure to restore a formerly infected host to production safely appears to work and should be reflected in the operational plan.
Incorrect Answers
A:That caution belongs to incident eradication workflow under the different requirement to remove attacker persistence following endpoint containment. The current case instead requires managing the risk that an unverified backup can reintroduce malware and persistence.
B:That caution belongs to incident containment workflow under the different requirement to stop verified ransomware from spreading through an enterprise segment. The current case instead requires managing the risk that an unverified backup can reintroduce malware and persistence.
C:That caution belongs to incident confirmation workflow under the different requirement to avoid blocking a production asset based only on a low-confidence model anomaly. The current case instead requires managing the risk that an unverified backup can reintroduce malware and persistence.
Question 109
Northstar Manufacturing's security operations team must measure the delay between first malicious activity and analyst detection. Several nearby defensive approaches are under consideration. Which approach is the most direct match for this specific requirement?
- Mean time to detect
- Mean time to respond
- Incident recurrence metric
- Insurance notification clock
Explanation
Correct Answer
A:Mean time to detect addresses this case because the team should subtract the first confirmed malicious event time from detection timestamp per incident. The direct verification is that the MTTD report uses consistent event and detection timestamps.
Incorrect Answers
B:Mean time to respond would address a different operational issue: measure the duration from acknowledged detection to a defined containment outcome. The separate task is to apply an agreed start and stop definition consistently across incidents, rather than the requested outcome to measure the delay between first malicious activity and analyst detection.
C:Incident recurrence metric would address a different operational issue: track whether containment quality improves after playbook changes. The separate task is to count repeat incidents of the same confirmed failure mode within a fixed follow-up window, rather than the requested outcome to measure the delay between first malicious activity and analyst detection.
D:Insurance notification clock would address a different operational issue: decide how to handle policy obligations when ransomware is suspected. The separate task is to notify the designated insurance and legal contacts within the policy conditions, rather than the requested outcome to measure the delay between first malicious activity and analyst detection.
Question 110
An authorized responder at Meridian Analytics has selected the mean time to detect approach to measure the delay between first malicious activity and analyst detection. Which concrete implementation step belongs to that approach instead of an adjacent but different SOC workflow?
- Apply an agreed start and stop definition consistently across incidents.
- Subtract the first confirmed malicious event time from detection timestamp per incident.
- Count repeat incidents of the same confirmed failure mode within a fixed follow-up window.
- Notify the designated insurance and legal contacts within the policy conditions.
Explanation
Correct Answer
B:To measure the delay between first malicious activity and analyst detection, this step operationalizes mean time to detect. In particular, subtract the first confirmed malicious event time from detection timestamp per incident; acceptance requires that the MTTD report uses consistent event and detection timestamps.
Incorrect Answers
A:This step implements mean time to respond, aimed at measure the duration from acknowledged detection to a defined containment outcome. It does not carry out the needed step for mean time to detect, where responders must subtract the first confirmed malicious event time from detection timestamp per incident.
C:This step implements incident recurrence metric, aimed at track whether containment quality improves after playbook changes. It does not carry out the needed step for mean time to detect, where responders must subtract the first confirmed malicious event time from detection timestamp per incident.
D:This step implements insurance notification clock, aimed at decide how to handle policy obligations when ransomware is suspected. It does not carry out the needed step for mean time to detect, where responders must subtract the first confirmed malicious event time from detection timestamp per incident.
Performing Cybersecurity Using Cisco Security Technologies (CBRCOR) (350-201) Practice Tests