Question 800
Following an exploit, the web team deploys a WAF signature and declares the root cause fixed without changing code. What change best turns containment into lasting eradication?
- Expand WAF signatures and retain more detailed web access logs
- Correct the vulnerable server-side logic and regression-test its boundary
- Adopt append-only or immutable log storage with restricted administrative roles
- Rebuild from patched dependencies and enforce image provenance gates
- Rebuild affected session state and validate dependency recovery order
Explanation
Correct Answer
B:For eradication and systemic correction involving “Correct the vulnerable server-side logic” and the report “the root cause fixed without changing code”, a code or configuration fix removes the exploitable behavior. “Keep the WAF rule active while scheduling verified application repair” is an immediate safeguard rather than systemic prevention.
Incorrect Answers
A:Filtering and instrumentation may reduce exposure or improve investigation, but vulnerable server-side logic still exists. A bypass or alternate input can reach the unchanged flaw.
C:For eradication and systemic correction, contrasting “Adopt append-only or immutable log” with “the root cause fixed without changing code”, evidence integrity requires controls outside ordinary application permissions. Against “the root cause fixed without changing code”, this does not establish “Correct the vulnerable server-side logic and regression-test”.
D:For eradication and systemic correction, contrasting “Rebuild from patched dependencies and” with “the root cause fixed without changing code”, the repair must reach the delivered runtime, not only the repository. For “Correct the vulnerable server-side logic and regression-test”, the case record must resolve “the root cause fixed without changing code”.
E:For eradication and systemic correction, contrasting “Rebuild affected session state and” with “the root cause fixed without changing code”, service restoration must include shared backing components. “the root cause fixed without changing code” is why proof of “vulnerable server-side logic and regression-test” matters here.
Question 801
Following an exploit, the web team deploys a WAF signature and declares the root cause fixed without changing code. Which verification best confirms that the original weakness is controlled?
- Test that application service identities cannot erase security audit history
- Exercise unauthorized API calls and confirm meaningful alerts are generated
- Verify deployed digests and dependency versions across every replica
- Confirm both direct origin tests and WAF-protected paths reject exploitation
Explanation
Correct Answer
D:For recovery and closure validation involving “Confirm both direct origin tests” and the report “the root cause fixed without changing code”, a passing WAF dashboard alone cannot certify the application. “Correct the vulnerable server-side logic and regression-test its boundary” is the correction whose effectiveness is being retested.
Incorrect Answers
A:For recovery and closure validation, contrasting “Test that application service identities” with “the root cause fixed without changing code”, the intended trust boundary should withstand a compromised workload identity. For the “the root cause fixed without changing code” observation, “both direct origin tests and WAF-protected” remains open.
B:For recovery and closure validation, contrasting “Exercise unauthorized API calls and” with “the root cause fixed without changing code”, log generation is useful only when detection and escalation work. The “tests and WAF-protected paths reject exploitation” requirement follows from “the root cause fixed without changing code”.
C:For recovery and closure validation, contrasting “Verify deployed digests and dependency” with “the root cause fixed without changing code”, validation should inspect actual running images rather than CI results alone. “both direct origin tests and WAF-protected” remains unverified against the reported “the root cause fixed without changing code”.
Question 802
A storage bucket unexpectedly becomes readable by anonymous internet clients after an IaC deployment. What action most directly limits ongoing harm while inquiry continues?
- Apply a restrictive instance security-group strategy and preserve snapshots
- Restore protected audit delivery and restrict who may modify trails
- Limit access to the original instance while snapshot operations proceed
- Restore a private effective policy and block unintended public access
Explanation
Correct Answer
D:For immediate response and containment involving “Restore a private effective policy” and the report “anonymous internet clients after an IaC deployment”, immediate permission tightening contains the exposure. “Preserve policy versions, configuration history and object access evidence” is the collection task to coordinate with containment.
Incorrect Answers
A:For immediate response and containment, contrasting “Apply a restrictive instance security-group” with “anonymous internet clients after an IaC deployment”, scoped isolation limits egress while maintaining approved forensic access where necessary. Here, “Restore a private effective policy and block” must account for “anonymous internet clients after an IaC deployment”.
B:For immediate response and containment, contrasting “Restore protected audit delivery and” with “anonymous internet clients after an IaC deployment”, containment limits further suppression while retaining investigation state. “anonymous internet clients after an IaC deployment” needs a more direct result for “effective policy and block unintended public”.
C:For immediate response and containment, contrasting “Limit access to the original” with “anonymous internet clients after an IaC deployment”, containment prevents further writes or attacker activity from obscuring findings. The comparison turns on “anonymous internet clients after an IaC deployment” versus “effective policy and block unintended public”.
Question 803
A database administrator exports large tables late at night despite no authorized maintenance ticket. What should be changed to prevent recurrence rather than only quiet alerts?
- Separate author, reviewer and deployer privileges with protected branches
- Introduce just-in-time privileged roles and sensitive export approval controls
- Require peer approval and immutable auditing for security-control exceptions
- Separate access request, approval and implementation duties
Explanation
Correct Answer
B:For eradication and systemic correction involving “Introduce just-in-time privileged roles and” and the report “at night despite no authorized maintenance ticket”, constrained access and dual review reduce abuse opportunities. “Limit further export rights pending validated review with HR and legal” is interim risk reduction.
Incorrect Answers
A:For eradication and systemic correction, contrasting “Separate author, reviewer and deployer” with “at night despite no authorized maintenance ticket”, enforced independent review limits both fraud and accidental misconfiguration. Only “Introduce just-in-time privileged roles and sensitive export” would test the “at night despite no authorized maintenance ticket” condition.
C:For eradication and systemic correction, contrasting “Require peer approval and immutable” with “at night despite no authorized maintenance ticket”, independent oversight reduces deliberate and accidental monitoring suppression. In “at night despite no authorized maintenance ticket”, the necessary control concerns “just-in-time privileged roles and sensitive export”.
D:For eradication and systemic correction, contrasting “Separate access request, approval and” with “at night despite no authorized maintenance ticket”, segregation prevents one insider from unilaterally granting sensitive access. For this “at night despite no authorized maintenance ticket” event, “Introduce just-in-time privileged roles and sensitive” is still outstanding.
Question 804
A Kubernetes pod in a cloud cluster repeatedly restarts and its local logs disappear with every new container. What should the analyst recognize before making a response decision?
- Recognize possible malicious deployment or secret misuse in serverless execution
- Recognize administrative privilege escalation through a compromised workload identity
- Recognize a potentially compromised workload rather than solely a firewall fault
- Recognize ephemeral logging loss in orchestrated workloads
Explanation
Correct Answer
D:For assessment and interpretation involving “Recognize ephemeral logging loss in” and the report “local logs disappear with every new container”, container replacement can discard local context needed to trace an exploit. “Capture pod events, audit logs and centrally exported container output” is a source for testing the inference.
Incorrect Answers
A:For assessment and interpretation, contrasting “Recognize possible malicious deployment or” with “local logs disappear with every new container”, short-lived functions can leak data without leaving persistent VM artifacts. Against “local logs disappear with every new container”, this does not establish “ephemeral logging loss in orchestrated”.
B:For assessment and interpretation, contrasting “Recognize administrative privilege escalation through” with “local logs disappear with every new container”, unusual grants can create persistent human or machine access long after a key rotates. For “ephemeral logging loss in orchestrated workloads”, the case record must resolve “local logs disappear with every new container”.
C:For assessment and interpretation, contrasting “Recognize a potentially compromised workload” with “local logs disappear with every new container”, outbound command traffic can originate from changed guest software. “local logs disappear with every new container” is why proof of “ephemeral logging loss in orchestrated” matters here.
Question 805
A managed tablet connects to public Wi-Fi using a profile that does not validate the enterprise VPN server certificate. What should be preserved to support a defensible investigation?
- Preserve MFA prompt history, device registration and session details
- Preserve container inventory, MDM ownership state and managed-app access
- Preserve network profile settings, certificate chain and connection events
- Preserve MDM last check-in, compliance status and relevant access logs
Explanation
Correct Answer
C:For evidence selection and preservation involving “Preserve network profile settings, certificate” and the report “not validate the enterprise VPN server certificate”, the record identifies what identity checks the client actually performed. “Suspend sensitive access over the unverified profile until it is corrected” is a response decision requiring reliable provenance.
Incorrect Answers
A:For evidence selection and preservation, contrasting “Preserve MFA prompt history, device” with “not validate the enterprise VPN server certificate”, the evidence links a push event to resulting account changes. “settings certificate chain and connection events” remains unverified against the reported “not validate the enterprise VPN server certificate”.
B:For evidence selection and preservation, contrasting “Preserve container inventory, MDM ownership” with “not validate the enterprise VPN server certificate”, accurate scope identifies data the enterprise is permitted to remove. For “not validate the enterprise VPN server certificate”, the missing check concerns “network profile settings certificate chain”.
D:For evidence selection and preservation, contrasting “Preserve MDM last check-in, compliance” with “not validate the enterprise VPN server certificate”, these records support a realistic exposure and recovery assessment. The incident detail “not validate the enterprise VPN server certificate” still calls for “settings certificate chain and connection events”.
Question 806
An exploited web server has been patched, but analysts have not established whether attacker credentials still work. What is the best immediate step for the on-call response team?
- Apply a temporary least-privilege rule while initiating systemic review
- Require step-up authentication and revoke confirmed suspicious sessions
- Limit the shared service's exposure while fixing impacted hosts
- Keep write traffic restricted until reconciliations are complete
- Revoke suspicious sessions and rotate affected credentials before reconnecting
Explanation
Correct Answer
E:For immediate response and containment involving “Revoke suspicious sessions and rotate” and the report “not established whether attacker credentials still work”, identity containment addresses access paths that remain after software repair. “Review identity logs and active sessions linked to the intrusion window” is the evidence path to retain.
Incorrect Answers
A:For immediate response and containment, contrasting “Apply a temporary least-privilege rule” with “not established whether attacker credentials still work”, short-term protection reduces exposure without claiming permanent resolution. The comparison turns on “not established whether attacker credentials still work” versus “suspicious sessions and rotate affected credentials”.
B:For immediate response and containment, contrasting “Require step-up authentication and revoke” with “not established whether attacker credentials still work”, containment targets identities potentially affected during the attack period. The case fact “not established whether attacker credentials still work” makes “and rotate affected credentials before” the better test.
C:For immediate response and containment, contrasting “Limit the shared service's exposure” with “not established whether attacker credentials still work”, containing the common pathway protects otherwise clean endpoints. “suspicious sessions and rotate affected credentials” is the criterion not satisfied for “not established whether attacker credentials still work”.
D:For immediate response and containment, contrasting “Keep write traffic restricted until” with “not established whether attacker credentials still work”, controlled access prevents an unverified restoration from contaminating new transactions. For the “not established whether attacker credentials still work” observation, “sessions and rotate affected credentials before reconnecting” remains open.
Question 807
A domain owner enforces DMARC reject and a forwarded message fails SPF at the final receiving server. What observable outcome best supports an incident closure decision?
- Confirm recipients no longer receive unreviewed lookalike messages
- Verify the same message verifies correctly across authorized relay paths
- Run SPF evaluations for every approved sender and unauthorized test source
- Test representative forwarded messages and spoofing attempts after correction
Explanation
Correct Answer
D:For recovery and closure validation involving “Test representative forwarded messages and” and the report “fails SPF at the final receiving server”, validation must confirm both interoperability and continued rejection of impostors. “Use aligned DKIM signing and consider standards-based forwarding accommodations” is the lasting control change.
Incorrect Answers
A:For recovery and closure validation, contrasting “Confirm recipients no longer receive” with “fails SPF at the final receiving server”, effectiveness requires watching the new sender identity, not only SPF failure counts. In “fails SPF at the final receiving server”, the necessary control concerns “spoofing attempts after correction”.
B:For recovery and closure validation, contrasting “Verify the same message verifies” with “fails SPF at the final receiving server”, a passing check establishes integrity for the signed portions of that message. For this “fails SPF at the final receiving server” event, “representative forwarded messages and spoofing attempts” is still outstanding.
C:For recovery and closure validation, contrasting “Run SPF evaluations for every” with “fails SPF at the final receiving server”, the fixed policy must authorize known infrastructure without broadly permitting others. “fails SPF at the final receiving server” is not evaluated through the “representative forwarded messages and spoofing attempts after” requirement.
Question 808
Two laptops are found at an incident location, but a staff member begins moving them to clear a desk. Which acquisition should receive priority for documenting this event?
- Photograph the screen and note displayed session, time and connections
- Photograph the connection, ports, serial numbers and nearby devices
- Record visible damage from a safe position and consult facility safety staff
- Capture overall, midrange and close-up photographs before movement
Explanation
Correct Answer
D:For evidence selection and preservation involving “Capture overall, midrange and close-up” and the report “begins moving them to clear a desk”, layered photos preserve scene orientation and equipment-level details. “Stop unnecessary relocation and document any movement already made” is the containment decision supported by those artifacts.
Incorrect Answers
A:For evidence selection and preservation, contrasting “Photograph the screen and note” with “begins moving them to clear a desk”, a contemporaneous visual record preserves observable state before interactions change it. “begins moving them to clear a desk” is why proof of “overall midrange and close-up photographs” matters here.
B:For evidence selection and preservation, contrasting “Photograph the connection, ports, serial” with “begins moving them to clear a desk”, context links the removable medium to the system as it was found. The option does not link “begins moving them to clear a desk” to “overall midrange and close-up photographs before movement”.
C:For evidence selection and preservation, contrasting “Record visible damage from a” with “begins moving them to clear a desk”, evidence gathering should not disturb an unsafe area before specialist clearance. “overall midrange and close-up photographs before” cannot be inferred from that “begins moving them to clear a desk” finding.
Question 809
An attacker exploits a public UDP reflector, causing responses far larger than requests to flood a victim. Which response action should be prioritized while the facts are confirmed?
- Apply SYN cookies or upstream SYN flood protection where supported
- Coordinate upstream filtering and anti-spoofing response with providers
- Apply a tightly scoped diversion or filtering rule for the attacked service
- Engage upstream DDoS mitigation and apply traffic filtering at the edge
Explanation
Correct Answer
B:For immediate response and containment involving “Coordinate upstream filtering and anti-spoofing” and the report “larger than requests to flood a victim”, victims often cannot block enough traffic after the access link is saturated. “Preserve protocol ratios, source distributions and reflected response signatures” is the evidence path to retain.
Incorrect Answers
A:For immediate response and containment, contrasting “Apply SYN cookies or upstream” with “larger than requests to flood a victim”, state-saving defenses reduce exhaustion without blocking every client. “larger than requests to flood a victim” gives a different evidentiary target: “and anti-spoofing response with providers”.
C:For immediate response and containment, contrasting “Apply a tightly scoped diversion” with “larger than requests to flood a victim”, proportionate mitigation preserves unaffected destinations. “and anti-spoofing response with providers” addresses a gap left by the “larger than requests to flood a victim” observation.
D:For immediate response and containment, contrasting “Engage upstream DDoS mitigation and” with “larger than requests to flood a victim”, filtering before the saturated link is more useful than host-only blocks. Against “larger than requests to flood a victim”, this does not establish “anti-spoofing response with providers”.
Question 810
A Google Cloud workload may have read sensitive objects, but only configuration-change events are currently being reviewed. What should the team verify after implementing the corrective action?
- Generate authorized test reads and verify their audit visibility
- Verify exported logs survive pod replacement and identities cannot overreach
- Verify that no additional external network connections originate from the workload
- Test approved invocations against a verified revision and monitor outbound calls
Explanation
Correct Answer
A:For recovery and closure validation involving “Generate authorized test reads and” and the report “only configuration-change events are currently being reviewed”, successful configuration means relevant data events can actually be retrieved. “Enable appropriate Data Access audit logging and protected retention” is the lasting control change.
Incorrect Answers
B:For recovery and closure validation, contrasting “Verify exported logs survive pod” with “only configuration-change events are currently being reviewed”, a stable cluster dashboard alone does not test forensic readiness. For the “only configuration-change events are currently being reviewed” observation, “test reads and verify their audit visibility” remains open.
C:Network egress tests do not prove that cloud object-read events are appearing in audit logs. A controlled read with verified data-access logging addresses the reported visibility gap.
D:For recovery and closure validation, contrasting “Test approved invocations against a” with “only configuration-change events are currently being reviewed”, recovery requires normal business function with no unexplained external requests. “verify their audit visibility” remains unverified against the reported “only configuration-change events are currently being reviewed”.