Question 870
To return staff access after account takeover without accepting old sessions, what should defenders select?
- Lessons-learned workshop
- Recovery monitoring window
- Clean credential restoration
- Post-rebuild validation
- Incident root-cause analysis
Explanation
Correct Answer
C:New trusted credentials and token revocation reestablish access after root cause closure; this mechanism directly supports the requirement to return staff access after account takeover without accepting old sessions.
Incorrect Answers
A:Structured review captures evidence-backed changes to playbooks, training and technical controls; that is useful when the task is to improve handoffs after a slow ransomware containment exercise, not the stated requirement to return staff access after account takeover without accepting old sessions.
B:Heightened detection tests for missed persistence or renewed attacker activity during return to service; a team would select it to watch rebuilt endpoints closely after reconnecting to the enterprise, which does not provide the particular result to return staff access after account takeover without accepting old sessions.
D:Functional tests and monitored telemetry support confidence before reconnecting to production; applying it would serve prove restored servers are patched and no longer exhibit compromise indicators without directly satisfying the goal to return staff access after account takeover without accepting old sessions.
E:Causal investigation informs durable controls and reduces recurrence of the same failure chain; it addresses the different need to identify the original exploited access path rather than only the final malware, leaving the requested ability to return staff access after account takeover without accepting old sessions unresolved.
Question 871
To prove restored servers are patched and no longer exhibit compromise indicators, which mechanism best fits?
- Post-rebuild validation
- Incident metrics tracking
- Recovery monitoring window
- Clean credential restoration
Explanation
Correct Answer
A:Functional tests and monitored telemetry support confidence before reconnecting to production; it supplies the specific control needed to prove restored servers are patched and no longer exhibit compromise indicators.
Incorrect Answers
B:Elapsed-time metrics reveal response bottlenecks when cases use consistent start and end definitions; that is useful when the task is to measure time from initial detection to effective containment, not the stated requirement to prove restored servers are patched and no longer exhibit compromise indicators.
C:Heightened detection tests for missed persistence or renewed attacker activity during return to service; a team would select it to watch rebuilt endpoints closely after reconnecting to the enterprise, which does not provide the particular result to prove restored servers are patched and no longer exhibit compromise indicators.
D:New trusted credentials and token revocation reestablish access after root cause closure; its operational purpose is to return staff access after account takeover without accepting old sessions, not to achieve the specific requirement to prove restored servers are patched and no longer exhibit compromise indicators.
Question 872
To watch rebuilt endpoints closely after reconnecting to the enterprise, which measure best meets the requirement?
- Recovery monitoring window
- Lessons-learned workshop
- Post-rebuild validation
- Incident root-cause analysis
Explanation
Correct Answer
A:Heightened detection tests for missed persistence or renewed attacker activity during return to service; that is why it addresses the operational task to watch rebuilt endpoints closely after reconnecting to the enterprise.
Incorrect Answers
B:Structured review captures evidence-backed changes to playbooks, training and technical controls; it could help someone trying to improve handoffs after a slow ransomware containment exercise, but the problem is instead to watch rebuilt endpoints closely after reconnecting to the enterprise.
C:Functional tests and monitored telemetry support confidence before reconnecting to production; that is useful when the task is to prove restored servers are patched and no longer exhibit compromise indicators, not the stated requirement to watch rebuilt endpoints closely after reconnecting to the enterprise.
D:Causal investigation informs durable controls and reduces recurrence of the same failure chain; a team would select it to identify the original exploited access path rather than only the final malware, which does not provide the particular result to watch rebuilt endpoints closely after reconnecting to the enterprise.
Question 873
To identify the original exploited access path rather than only the final malware, what control should be selected?
- Incident closure criteria
- Post-rebuild validation
- Incident root-cause analysis
- Incident metrics tracking
Explanation
Correct Answer
C:Causal investigation informs durable controls and reduces recurrence of the same failure chain; its relevant protective or investigative effect is to identify the original exploited access path rather than only the final malware.
Incorrect Answers
A:Defined closure checks cover eradication, recovery, monitoring and outstanding actions; the outcome it supports is to avoid declaring a breach closed while malicious persistence remains possible, whereas this scenario asks defenders to identify the original exploited access path rather than only the final malware.
B:Functional tests and monitored telemetry support confidence before reconnecting to production; although relevant to prove restored servers are patched and no longer exhibit compromise indicators, it does not by itself achieve the required task to identify the original exploited access path rather than only the final malware.
D:Elapsed-time metrics reveal response bottlenecks when cases use consistent start and end definitions; that is useful when the task is to measure time from initial detection to effective containment, not the stated requirement to identify the original exploited access path rather than only the final malware.
Question 874
To improve handoffs after a slow ransomware containment exercise, which security control is most appropriate?
- Lessons-learned workshop
- Evidence release authorization
- Incident closure criteria
- Incident root-cause analysis
- Regulatory notification assessment
- Incident metrics tracking
Explanation
Correct Answer
A:Structured review captures evidence-backed changes to playbooks, training and technical controls; the requested outcome is precisely to improve handoffs after a slow ransomware containment exercise.
Incorrect Answers
B:Coordinated approval balances business recovery with retention and legal obligations; the outcome it supports is to prevent restoration teams destroying material still required for investigation, whereas this scenario asks defenders to improve handoffs after a slow ransomware containment exercise.
C:Defined closure checks cover eradication, recovery, monitoring and outstanding actions; although relevant to avoid declaring a breach closed while malicious persistence remains possible, it does not by itself achieve the required task to improve handoffs after a slow ransomware containment exercise.
D:Causal investigation informs durable controls and reduces recurrence of the same failure chain; it could help someone trying to identify the original exploited access path rather than only the final malware, but the problem is instead to improve handoffs after a slow ransomware containment exercise.
E:Legal, privacy and incident leads evaluate applicable thresholds and deadlines before external notice; that is useful when the task is to determine whether breach disclosure duties are triggered by affected data, not the stated requirement to improve handoffs after a slow ransomware containment exercise.
F:Elapsed-time metrics reveal response bottlenecks when cases use consistent start and end definitions; a team would select it to measure time from initial detection to effective containment, which does not provide the particular result to improve handoffs after a slow ransomware containment exercise.
Question 875
To measure time from initial detection to effective containment, what would a incident responder implement or use?
- Response readiness re-test
- Incident metrics tracking
- Incident root-cause analysis
- Regulatory notification assessment
- Recovery monitoring window
Explanation
Correct Answer
B:Elapsed-time metrics reveal response bottlenecks when cases use consistent start and end definitions; this choice fits the scenario because the team must measure time from initial detection to effective containment.
Incorrect Answers
A:Repeatable validation checks whether lessons translated into operational improvement; the technique works for situations involving confirm controls changed after an incident now detect a replayed attack path, rather than this need to measure time from initial detection to effective containment.
C:Causal investigation informs durable controls and reduces recurrence of the same failure chain; the outcome it supports is to identify the original exploited access path rather than only the final malware, whereas this scenario asks defenders to measure time from initial detection to effective containment.
D:Legal, privacy and incident leads evaluate applicable thresholds and deadlines before external notice; although relevant to determine whether breach disclosure duties are triggered by affected data, it does not by itself achieve the required task to measure time from initial detection to effective containment.
E:Heightened detection tests for missed persistence or renewed attacker activity during return to service; it could help someone trying to watch rebuilt endpoints closely after reconnecting to the enterprise, but the problem is instead to measure time from initial detection to effective containment.
Question 876
To determine whether breach disclosure duties are triggered by affected data, which practice addresses that objective?
- Regulatory notification assessment
- Improvement action ownership
- Incident metrics tracking
- Evidence release authorization
Explanation
Correct Answer
A:Legal, privacy and incident leads evaluate applicable thresholds and deadlines before external notice; this mechanism directly supports the requirement to determine whether breach disclosure duties are triggered by affected data.
Incorrect Answers
B:Tracked remediation includes accountable owners, due dates and verification of completion; the technique works for situations involving ensure a failed log forwarding path is fixed after incident review, rather than this need to determine whether breach disclosure duties are triggered by affected data.
C:Elapsed-time metrics reveal response bottlenecks when cases use consistent start and end definitions; its mechanism supports measure time from initial detection to effective containment, while the requested control must be able to determine whether breach disclosure duties are triggered by affected data.
D:Coordinated approval balances business recovery with retention and legal obligations; the outcome it supports is to prevent restoration teams destroying material still required for investigation, whereas this scenario asks defenders to determine whether breach disclosure duties are triggered by affected data.
Question 877
To prevent restoration teams destroying material still required for investigation, which tool, policy, or technique is appropriate?
- Improvement action ownership
- Incident closure criteria
- Incident metrics tracking
- Evidence release authorization
Explanation
Correct Answer
D:Coordinated approval balances business recovery with retention and legal obligations; it supplies the specific control needed to prevent restoration teams destroying material still required for investigation.
Incorrect Answers
A:Tracked remediation includes accountable owners, due dates and verification of completion; applying it would serve ensure a failed log forwarding path is fixed after incident review without directly satisfying the goal to prevent restoration teams destroying material still required for investigation.
B:Defined closure checks cover eradication, recovery, monitoring and outstanding actions; it addresses the different need to avoid declaring a breach closed while malicious persistence remains possible, leaving the requested ability to prevent restoration teams destroying material still required for investigation unresolved.
C:Elapsed-time metrics reveal response bottlenecks when cases use consistent start and end definitions; the technique works for situations involving measure time from initial detection to effective containment, rather than this need to prevent restoration teams destroying material still required for investigation.
Question 878
To avoid declaring a breach closed while malicious persistence remains possible, what safeguard would be most applicable?
- Incident metrics tracking
- Improvement action ownership
- Response readiness re-test
- Incident closure criteria
Explanation
Correct Answer
D:Defined closure checks cover eradication, recovery, monitoring and outstanding actions; that is why it addresses the operational task to avoid declaring a breach closed while malicious persistence remains possible.
Incorrect Answers
A:Elapsed-time metrics reveal response bottlenecks when cases use consistent start and end definitions; its operational purpose is to measure time from initial detection to effective containment, not to achieve the specific requirement to avoid declaring a breach closed while malicious persistence remains possible.
B:Tracked remediation includes accountable owners, due dates and verification of completion; applying it would serve ensure a failed log forwarding path is fixed after incident review without directly satisfying the goal to avoid declaring a breach closed while malicious persistence remains possible.
C:Repeatable validation checks whether lessons translated into operational improvement; it addresses the different need to confirm controls changed after an incident now detect a replayed attack path, leaving the requested ability to avoid declaring a breach closed while malicious persistence remains possible unresolved.
Question 879
To ensure a failed log forwarding path is fixed after incident review, what is the relevant defensive action?
- Incident metrics tracking
- Regulatory notification assessment
- Improvement action ownership
- Incident closure criteria
Explanation
Correct Answer
C:Tracked remediation includes accountable owners, due dates and verification of completion; its relevant protective or investigative effect is to ensure a failed log forwarding path is fixed after incident review.
Incorrect Answers
A:Elapsed-time metrics reveal response bottlenecks when cases use consistent start and end definitions; a team would select it to measure time from initial detection to effective containment, which does not provide the particular result to ensure a failed log forwarding path is fixed after incident review.
B:Legal, privacy and incident leads evaluate applicable thresholds and deadlines before external notice; its operational purpose is to determine whether breach disclosure duties are triggered by affected data, not to achieve the specific requirement to ensure a failed log forwarding path is fixed after incident review.
D:Defined closure checks cover eradication, recovery, monitoring and outstanding actions; it addresses the different need to avoid declaring a breach closed while malicious persistence remains possible, leaving the requested ability to ensure a failed log forwarding path is fixed after incident review unresolved.
Question 880
To confirm controls changed after an incident now detect a replayed attack path, which solution should be adopted?
- Incident closure criteria
- Improvement action ownership
- Regulatory notification assessment
- Evidence release authorization
- Response readiness re-test
Explanation
Correct Answer
E:Repeatable validation checks whether lessons translated into operational improvement; the requested outcome is precisely to confirm controls changed after an incident now detect a replayed attack path.
Incorrect Answers
A:Defined closure checks cover eradication, recovery, monitoring and outstanding actions; that is useful when the task is to avoid declaring a breach closed while malicious persistence remains possible, not the stated requirement to confirm controls changed after an incident now detect a replayed attack path.
B:Tracked remediation includes accountable owners, due dates and verification of completion; a team would select it to ensure a failed log forwarding path is fixed after incident review, which does not provide the particular result to confirm controls changed after an incident now detect a replayed attack path.
C:Legal, privacy and incident leads evaluate applicable thresholds and deadlines before external notice; its operational purpose is to determine whether breach disclosure duties are triggered by affected data, not to achieve the specific requirement to confirm controls changed after an incident now detect a replayed attack path.
D:Coordinated approval balances business recovery with retention and legal obligations; applying it would serve prevent restoration teams destroying material still required for investigation without directly satisfying the goal to confirm controls changed after an incident now detect a replayed attack path.