Question 210
A large disk image is delivered with a single checksum but the transfer ended unexpectedly. What acceptance test would provide the most relevant closure evidence?
- Test decryption only on a verified working copy under authorization
- Verify hashes and image size before beginning substantive analysis
- Validate only the checksum of the partial file received before transfer interruption
- Reconcile device labels with photographs and the scene sketch
Explanation
Correct Answer
B:For recovery and closure validation involving “Verify hashes and image size” and the report “single checksum but the transfer ended unexpectedly”, chain of custody cannot compensate for unverified file content. “Adopt resumable validated transfers with end-to-end integrity checks” is the permanent measure linked to the closure evidence.
Incorrect Answers
A:For recovery and closure validation, contrasting “Test decryption only on a” with “single checksum but the transfer ended unexpectedly”, a successful controlled access test leaves original evidence unchanged. Against “single checksum but the transfer ended unexpectedly”, this does not establish “hashes and image size before beginning substantive”.
C:An interrupted file can match a checksum calculated over the same truncated copy while still missing sectors. The accepted image must have the expected full length and trusted integrity values.
D:For recovery and closure validation, contrasting “Reconcile device labels with photographs” with “single checksum but the transfer ended unexpectedly”, the final inventory should show where each item originated. The option does not link “single checksum but the transfer ended unexpectedly” to “hashes and image size before beginning substantive”.
Question 211
Security analysts can query infrastructure changes but cannot tell which object data an attacker may have read. How should the responder classify the central risk described?
- Recognize exposed long-lived credentials as an incident even before confirmed misuse
- Recognize excessive IAM privilege increasing the breach blast radius
- Recognize the difference between management-plane and data-access telemetry
- Recognize administrative privilege escalation through a compromised workload identity
Explanation
Correct Answer
C:Administrative configuration logs may not cover every read of stored objects. “Identify enabled data-access logs, object paths and relevant request identities” is a separate source of incident context.
Incorrect Answers
A:An accessible secret may have been copied and used outside ordinary monitoring. “difference between management-plane and data-access telemetry” remains unverified against the reported “object data an attacker may have read”.
B:A role able to administer unrelated services makes one workload compromise much more damaging. For “object data an attacker may have read”, the missing check concerns “the difference between management-plane and data-access telemetry”.
D:Unusual grants can create persistent human or machine access long after a key rotates. The incident detail “object data an attacker may have read” still calls for “difference between management-plane and data-access telemetry”.
Question 212
A file server receives repeated authentication attempts against many accounts from one internal workstation. Which durable control should follow short-term containment?
- Require time-scoped vendor access and stronger identity conditions
- Remove the attack tool and harden credential and remote-access controls
- Implement expiry and peer review for emergency firewall changes
- Correct inter-VLAN policies and enforce dedicated management access
Explanation
Correct Answer
B:Remediation must address compromised endpoints and password-based exposure. “Isolate the origin workstation and protect targeted accounts” is an immediate safeguard rather than systemic prevention.
Incorrect Answers
A:Just-in-time authorization narrows the window in which stolen accounts remain useful. The comparison turns on “against many accounts from one internal workstation” versus “tool and harden credential and remote-access controls”.
C:Temporary controls should not become permanent unmanaged exposure. “the attack tool and harden credential” is the criterion not satisfied for “against many accounts from one internal workstation”.
D:A hardened path separates operator sessions from untrusted client networks. For the “against many accounts from one internal workstation” observation, “attack tool and harden credential and remote-access” remains open.
Question 213
A cloud API key appears in a public code repository, but no suspicious infrastructure has yet been identified. Which inference would best shape the next investigative step?
- Recognize an ephemeral evidence-readiness gap in automated infrastructure
- Recognize the difference between management-plane and data-access telemetry
- Recognize administrative privilege escalation through a compromised workload identity
- Recognize exposed long-lived credentials as an incident even before confirmed misuse
- Recognize excessive IAM privilege increasing the breach blast radius
Explanation
Correct Answer
D:For assessment and interpretation involving “Recognize exposed long-lived credentials as” and the report “no suspicious infrastructure has yet been identified”, an accessible secret may have been copied and used outside ordinary monitoring. “Preserve secret-exposure timing, audit events and repository revision history” is a check against premature attribution.
Incorrect Answers
A:Terminated instances can lose local state and associated short-retention logs. In “no suspicious infrastructure has yet been identified”, the necessary control concerns “an incident even before confirmed misuse”.
B:For assessment and interpretation, contrasting “Recognize the difference between management-plane” with “no suspicious infrastructure has yet been identified”, administrative configuration logs may not cover every read of stored objects. For this “no suspicious infrastructure has yet been identified” event, “exposed long-lived credentials as an incident even” is still outstanding.
C:For assessment and interpretation, contrasting “Recognize administrative privilege escalation through” with “no suspicious infrastructure has yet been identified”, unusual grants can create persistent human or machine access long after a key rotates. “no suspicious infrastructure has yet been identified” is not evaluated through the “exposed long-lived credentials as an incident” requirement.
E:For assessment and interpretation, contrasting “Recognize excessive IAM privilege increasing” with “no suspicious infrastructure has yet been identified”, a role able to administer unrelated services makes one workload compromise much more damaging. “no suspicious infrastructure has yet been identified” needs a more direct result for “exposed long-lived credentials as an incident even”.
Question 214
A compromised Windows host is live and may hold decrypted ransomware keys only in memory. What change best turns containment into lasting eradication?
- Configure trustworthy time synchronization and standardized response tooling
- Route workload logs off-host and automate ephemeral evidence capture
- Improve playbooks to collect RAM before shutdown when safe and lawful
- Add trusted live-response collection commands to the server runbook
Explanation
Correct Answer
C:For eradication and systemic correction involving “Improve playbooks to collect RAM” and the report “hold decrypted ransomware keys only in memory”, a defined order of volatility prevents irreversible evidence loss. “Keep the host isolated while acquiring volatile data under the response plan” is interim risk reduction.
Incorrect Answers
A:For eradication and systemic correction, contrasting “Configure trustworthy time synchronization and” with “hold decrypted ransomware keys only in memory”, consistent clocks and collector procedures improve correlation across responders. “hold decrypted ransomware keys only in memory” is why proof of “Improve playbooks to collect RAM before shutdown” matters here.
B:For eradication and systemic correction, contrasting “Route workload logs off-host and” with “hold decrypted ransomware keys only in memory”, centralized evidence survives routine container recycling. The option does not link “hold decrypted ransomware keys only in memory” to “collect RAM before shutdown when safe”.
D:For eradication and systemic correction, contrasting “Add trusted live-response collection commands” with “hold decrypted ransomware keys only in memory”, standardized minimal collection minimizes alteration and improves repeatability. Only “Improve playbooks to collect RAM before shutdown” would test the “hold decrypted ransomware keys only in memory” condition.
Question 215
A comment field stores script content that executes in other users' browsers when they view a ticket. Which condition should the service owner confirm before final sign-off?
- Confirm payloads appear as harmless text in browser tests
- Test unauthorized origins cannot embed the approval workflow
- Verify approved scripts load and sensitive fields are not read unexpectedly
- Verify dangerous markup is inert in every supported display context
Explanation
Correct Answer
D:For recovery and closure validation involving “Verify dangerous markup is inert” and the report “users' browsers when they view a ticket”, input filtering alone is not a reliable cross-context guarantee. “Apply context-appropriate output encoding and safe rich-text sanitization” is the permanent measure linked to the closure evidence.
Incorrect Answers
A:For recovery and closure validation, contrasting “Confirm payloads appear as harmless” with “users' browsers when they view a ticket”, an escaping fix should not break normal search output. “users' browsers when they view a ticket” gives a different evidentiary target: “is inert in every supported display context”.
B:For recovery and closure validation, contrasting “Test unauthorized origins cannot embed” with “users' browsers when they view a ticket”, a successful result checks rendered behavior in supported browsers. The incident detail “users' browsers when they view a ticket” still calls for “markup is inert in every supported display”.
C:For recovery and closure validation, contrasting “Verify approved scripts load and” with “users' browsers when they view a ticket”, browser-side behavior must be assessed beyond server access logs. “dangerous markup is inert in every supported” addresses a gap left by the “users' browsers when they view a ticket” observation.
Question 216
A developer can approve and deploy their own production security-rule changes without any peer review. Which measurement demonstrates that expected protections now hold?
- Verify sensitive changes map to identifiable users and approved sessions
- Test that a developer cannot merge and release unreviewed security changes
- Confirm executive mail is accessible only under documented approved grants
- Test EDR telemetry across previously excluded endpoints after restoration
Explanation
Correct Answer
B:For recovery and closure validation involving “Test that a developer cannot” and the report “production security-rule changes without any peer review”, workflow design must be proven with negative permission tests. “Separate author, reviewer and deployer privileges with protected branches” is a control change requiring validation.
Incorrect Answers
A:For recovery and closure validation, contrasting “Verify sensitive changes map to” with “production security-rule changes without any peer review”, a logging system is useful only if identities are personally attributable. “developer cannot merge and release unreviewed security” is the criterion not satisfied for “production security-rule changes without any peer review”.
C:For recovery and closure validation, contrasting “Confirm executive mail is accessible” with “production security-rule changes without any peer review”, a full permission review must include inherited and delegated rights. The “cannot merge and release unreviewed security” requirement follows from “production security-rule changes without any peer review”.
D:For recovery and closure validation, contrasting “Test EDR telemetry across previously” with “production security-rule changes without any peer review”, re-enabling a toggle does not prove events are reaching the SOC. “developer cannot merge and release unreviewed” remains unverified against the reported “production security-rule changes without any peer review”.
Question 217
An endpoint sends large outbound transfers to an unfamiliar server immediately after an archive process runs. Which immediate response is most proportionate to the stated risk?
- Restrict suspicious DNS destinations while preserving necessary resolver service
- Quarantine the endpoint and block the destination while preserving transfer logs
- Block untrusted retrieval paths and isolate the executing host
- Microsegment the host and suspend compromised lateral access routes
Explanation
Correct Answer
B:For immediate response and containment involving “Quarantine the endpoint and block” and the report “server immediately after an archive process runs”, swift containment limits further disclosure without altering historical records. “Correlate file access, archive creation, process lineage and network bytes” is the artifact-preservation requirement.
Incorrect Answers
A:For immediate response and containment, contrasting “Restrict suspicious DNS destinations while” with “server immediately after an archive process runs”, selective controls can stop covert channels without removing all DNS connectivity. “server immediately after an archive process runs” is not evaluated through the “Quarantine the endpoint and block the destination” requirement.
C:For immediate response and containment, contrasting “Block untrusted retrieval paths and” with “server immediately after an archive process runs”, containment interrupts subsequent payload delivery while preserving investigation context. “server immediately after an archive process runs” needs a more direct result for “while preserving transfer logs”.
D:For immediate response and containment, contrasting “Microsegment the host and suspend” with “server immediately after an archive process runs”, restricting east-west paths limits spread without taking all services offline. The comparison turns on “server immediately after an archive process runs” versus “the destination while preserving transfer logs”.
Question 218
A hard drive is stored in an unsealed plastic bag that offers little protection from static discharge. What should the team verify after implementing the corrective action?
- Inspect seal identifiers and condition at each receipt
- Compare received hashes and check recipient audit logs
- Verify an uninterrupted series of custody entries and seal checks
- Confirm lawful receipt, unchanged seals and recorded arrival time
Explanation
Correct Answer
A:For recovery and closure validation involving “Inspect seal identifiers and condition” and the report “that offers little protection from static discharge”, packaging integrity and custody continuity must be checked together. “Adopt evidence-specific packaging standards for electronic devices” is the permanent measure linked to the closure evidence.
Incorrect Answers
B:For recovery and closure validation, contrasting “Compare received hashes and check” with “that offers little protection from static discharge”, verification ensures the expected data reached only approved investigators. Only “seal identifiers and condition at each receipt” would test the “that offers little protection from static discharge” condition.
C:For recovery and closure validation, contrasting “Verify an uninterrupted series of” with “that offers little protection from static discharge”, the history should explain control of the exhibit from collection to storage. The “that offers little protection from static discharge” report requires a finding about “identifiers and condition at each receipt”.
D:Successful transport requires both regulatory compliance and physical integrity. In “that offers little protection from static discharge”, the necessary control concerns “Inspect seal identifiers and condition at”.
Question 219
An EDR console shows a device as isolated, but packet captures reveal continued traffic from a secondary network adapter. What observable outcome best supports an incident closure decision?
- Test outbound and lateral reachability on each physical and virtual adapter
- Test reboot behavior with full telemetry and confirm no task resurrection
- Replay the approved automation and verify unauthorized variants are blocked
- Verify no abnormal child processes occur during controlled application use
Explanation
Correct Answer
A:For recovery and closure validation involving “Test outbound and lateral reachability” and the report “continued traffic from a secondary network adapter”, a dashboard status alone is not evidence of complete isolation. “Repair EDR isolation policy or network segmentation for multi-homed devices” is the preventive step behind this check.
Incorrect Answers
B:Recovery should exercise the mechanism that previously relaunched code. Against “continued traffic from a secondary network adapter”, this does not establish “reachability on each physical and virtual adapter”.
C:For recovery and closure validation, contrasting “Replay the approved automation and” with “continued traffic from a secondary network adapter”, the control must preserve expected administrative functionality. For “outbound and lateral reachability on”, the case record must resolve “continued traffic from a secondary network adapter”.
D:For recovery and closure validation, contrasting “Verify no abnormal child processes” with “continued traffic from a secondary network adapter”, recovery requires watching the exploited behavior, not just the file name. “continued traffic from a secondary network adapter” is why proof of “lateral reachability on each physical and virtual” matters here.
Question 220
An organization deploys an email-reporting button, but reporters receive no ticket or acknowledgment. Which result would most convincingly demonstrate safe recovery?
- Replay legitimate and malicious samples against the revised mail policy
- Verify delivery for approved sources and rejection of forged messages
- Test reporting from desktop and mobile with end-to-end confirmation
- Run test cases proving exercises do not trigger account suspension
- Monitor new arrivals for linked indicators and measure missed recipients
Explanation
Correct Answer
C:For recovery and closure validation involving “Test reporting from desktop and” and the report “but reporters receive no ticket or acknowledgment”, validation spans user action, triage record and feedback delivery. “Integrate the button with case management and response SLAs” is the lasting control change.
Incorrect Answers
A:For recovery and closure validation, contrasting “Replay legitimate and malicious samples” with “but reporters receive no ticket or acknowledgment”, quality assurance must measure both delivery and detection outcomes. The “reporting from desktop and mobile” requirement follows from “but reporters receive no ticket or acknowledgment”.
B:For recovery and closure validation, contrasting “Verify delivery for approved sources” with “but reporters receive no ticket or acknowledgment”, both business continuity and anti-spoofing assurance are release criteria. “from desktop and mobile with end-to-end confirmation” remains unverified against the reported “but reporters receive no ticket or acknowledgment”.
D:For recovery and closure validation, contrasting “Run test cases proving exercises” with “but reporters receive no ticket or acknowledgment”, a verified safeguard prevents repeat operational harm. “but reporters receive no ticket or acknowledgment” gives a different evidentiary target: “desktop and mobile with end-to-end confirmation”.
E:For recovery and closure validation, contrasting “Monitor new arrivals for linked” with “but reporters receive no ticket or acknowledgment”, closure requires sustained detection and recipient coverage. The incident detail “but reporters receive no ticket or acknowledgment” still calls for “reporting from desktop and mobile”.