Question 580
A network appliance displays an unfamiliar administrator account recreated after every configuration rollback. Which measurement demonstrates that expected protections now hold?
- Verify secure boot measurements and expected startup behavior
- Confirm the process does not recur at the former execution interval
- Verify no unexpected launch after logoff, reboot and monitored sign-in
- Audit accounts and configuration after a clean reboot and management login
Explanation
Correct Answer
D:For recovery and closure validation involving “Audit accounts and configuration after” and the report “administrator account recreated after every configuration rollback”, persistent control must not reappear during normal operation. “Apply verified firmware/configuration recovery and remove malicious identities” is the preventive step behind this check.
Incorrect Answers
A:For recovery and closure validation, contrasting “Verify secure boot measurements and” with “administrator account recreated after every configuration rollback”, endpoint trust requires evidence the verified boot chain is restored. The incident detail “administrator account recreated after every configuration rollback” still calls for “clean reboot and management login”.
B:For recovery and closure validation, contrasting “Confirm the process does not” with “administrator account recreated after every configuration rollback”, a targeted observation window tests the actual persistence mechanism. “configuration after a clean reboot and management” addresses a gap left by the “administrator account recreated after every configuration rollback” observation.
C:For recovery and closure validation, contrasting “Verify no unexpected launch after” with “administrator account recreated after every configuration rollback”, testing the trigger path checks that persistence was genuinely removed. Against “administrator account recreated after every configuration rollback”, this does not establish “accounts and configuration after a clean”.
Question 581
A cloud API key appears in a public code repository, but no suspicious infrastructure has yet been identified. Which near-term intervention best fits these operational constraints?
- Revoke suspicious grants and suspend the misused identity
- Revoke the exposed key and move workloads to unaffected credentials
- Invalidate affected sessions where feasible and reduce excessive permissions
- Restrict suspect storage access and preserve available access logs immediately
Explanation
Correct Answer
B:For immediate response and containment involving “Revoke the exposed key and” and the report “no suspicious infrastructure has yet been identified”, rapid rotation prevents continued use while maintaining approved service access. “Preserve secret-exposure timing, audit events and repository revision history” is the artifact-preservation requirement.
Incorrect Answers
A:For immediate response and containment, contrasting “Revoke suspicious grants and suspend” with “no suspicious infrastructure has yet been identified”, containment closes newly created access while preserving legitimate administration. For the “no suspicious infrastructure has yet been identified” observation, “exposed key and move workloads to unaffected” remains open.
C:For immediate response and containment, contrasting “Invalidate affected sessions where feasible” with “no suspicious infrastructure has yet been identified”, short-term least privilege limits further abuse without deleting the workload blindly. “the exposed key and move workloads” remains unverified against the reported “no suspicious infrastructure has yet been identified”.
D:For immediate response and containment, contrasting “Restrict suspect storage access and” with “no suspicious infrastructure has yet been identified”, immediate access control limits further disclosure while gaps are assessed. For “no suspicious infrastructure has yet been identified”, the missing check concerns “exposed key and move workloads to unaffected”.
Question 582
A web application fails under floods of seemingly valid HTTP requests aimed at an expensive search endpoint. Which security assessment best distinguishes this event from a routine exception?
- Recognize disproportionate collateral impact from overly broad blackholing
- Recognize application-layer resource exhaustion rather than raw bandwidth saturation
- Recognize a state-exhaustion attack involving unfinished handshakes
- Recognize random-subdomain DNS exhaustion against authoritative resolution
- Recognize a volumetric distributed denial-of-service pattern
Explanation
Correct Answer
B:For assessment and interpretation involving “Recognize application-layer resource exhaustion rather” and the report “requests aimed at an expensive search endpoint”, valid-looking requests can exhaust backend CPU or databases at modest traffic volume. “Capture request patterns, client behavior, endpoint latency and backend utilization” is a source for testing the inference.
Incorrect Answers
A:For assessment and interpretation, contrasting “Recognize disproportionate collateral impact from” with “requests aimed at an expensive search endpoint”, subnet-wide null routing can disrupt unrelated business services. Here, “application-layer resource exhaustion rather than raw” must account for “requests aimed at an expensive search endpoint”.
C:For assessment and interpretation, contrasting “Recognize a state-exhaustion attack involving” with “requests aimed at an expensive search endpoint”, half-open connections can consume state resources before application traffic arrives. The comparison turns on “requests aimed at an expensive search endpoint” versus “application-layer resource exhaustion rather than raw bandwidth”.
D:Unique labels reduce cache effectiveness and force expensive query processing. The case fact “requests aimed at an expensive search endpoint” makes “rather than raw bandwidth” the better test.
E:For assessment and interpretation, contrasting “Recognize a volumetric distributed denial-of-service” with “requests aimed at an expensive search endpoint”, large distributed flows can saturate bandwidth before reaching application logic. “resource exhaustion rather than raw bandwidth” is the criterion not satisfied for “requests aimed at an expensive search endpoint”.
Question 583
A compromised Windows host is live and may hold decrypted ransomware keys only in memory. Which near-term intervention best fits these operational constraints?
- Restrict the suspicious communication path while preserving approved live access
- Keep the host isolated while acquiring volatile data under the response plan
- Delay nonessential restart until approved volatile collection is complete
- Pause replacement only through an approved safe containment mechanism
Explanation
Correct Answer
B:For immediate response and containment involving “Keep the host isolated while” and the report “hold decrypted ransomware keys only in memory”, network restriction limits propagation without needlessly erasing memory. “Capture a memory image using an approved trusted acquisition method” is a time-sensitive forensic step.
Incorrect Answers
A:For immediate response and containment, contrasting “Restrict the suspicious communication path” with “hold decrypted ransomware keys only in memory”, targeted containment can limit command traffic without a full service outage. Only “acquiring volatile data under the response plan” would test the “hold decrypted ransomware keys only in memory” condition.
C:For immediate response and containment, contrasting “Delay nonessential restart until approved” with “hold decrypted ransomware keys only in memory”, a brief controlled hold preserves evidence when continued operation is safe. In “hold decrypted ransomware keys only in memory”, the necessary control concerns “Keep the host isolated while”.
D:For immediate response and containment, contrasting “Pause replacement only through an” with “hold decrypted ransomware keys only in memory”, coordinated retention protects evidence without creating an unbounded service risk. For this “hold decrypted ransomware keys only in memory” event, “isolated while acquiring volatile data” is still outstanding.
Question 584
An account portal lets users change the email field in a privileged update request and silently apply changes to another account. Which fix most closely matches the failure mechanism identified?
- Require successful authentication without checking the target account or writable fields
- Allowlist writable fields and enforce object-level access checks
- Implement centralized role or permission verification for each action
- Enforce issuer, audience, expiry and signing algorithm checks
Explanation
Correct Answer
B:For eradication and systemic correction involving “Allowlist writable fields and enforce” and the report “and silently apply changes to another account”, a server-side schema should not map arbitrary client keys into privileged properties. “Disable dangerous update fields until server-side checks are deployed” is the short-term measure to contrast with remediation.
Incorrect Answers
A:A logged-in user can still alter another account when object authorization is absent. Authentication alone also does not restrict sensitive properties that the client should not control.
C:For eradication and systemic correction, contrasting “Implement centralized role or permission” with “and silently apply changes to another account”, authorization must be applied consistently in request handlers. “and silently apply changes to another account” is why proof of “writable fields and enforce object-level access” matters here.
D:For eradication and systemic correction, contrasting “Enforce issuer, audience, expiry and” with “and silently apply changes to another account”, full validation binds identity assertions to the specific consumer. The option does not link “and silently apply changes to another account” to “Allowlist writable fields”.
Question 585
A database administrator exports large tables late at night despite no authorized maintenance ticket. Which condition should the service owner confirm before final sign-off?
- Confirm privileged exports require approval and no unreviewed data transfers persist
- Confirm executive mail is accessible only under documented approved grants
- Verify sensitive changes map to identifiable users and approved sessions
- Verify no dormant emergency roles remain and authorized break-glass access works
Explanation
Correct Answer
A:For recovery and closure validation involving “Confirm privileged exports require approval” and the report “at night despite no authorized maintenance ticket”, closure needs both factual investigation and functioning controls. “Introduce just-in-time privileged roles and sensitive export approval controls” is the remediation record that supports sign-off.
Incorrect Answers
B:For recovery and closure validation, contrasting “Confirm executive mail is accessible” with “at night despite no authorized maintenance ticket”, a full permission review must include inherited and delegated rights. For “at night despite no authorized maintenance ticket”, the missing check concerns “approval and no unreviewed data transfers persist”.
C:For recovery and closure validation, contrasting “Verify sensitive changes map to” with “at night despite no authorized maintenance ticket”, a logging system is useful only if identities are personally attributable. “at night despite no authorized maintenance ticket” gives a different evidentiary target: “privileged exports require approval and”.
D:For recovery and closure validation, contrasting “Verify no dormant emergency roles” with “at night despite no authorized maintenance ticket”, the organization needs both least privilege and a tested emergency process. The incident detail “at night despite no authorized maintenance ticket” still calls for “require approval and no unreviewed data transfers”.
Question 586
A user repeatedly approves unfamiliar mobile push requests and then finds a new trusted device registered to their account. What records would most clearly support validation of the reported activity?
- Preserve container inventory, MDM ownership state and managed-app access
- Preserve network profile settings, certificate chain and connection events
- Preserve application storage findings and token usage audit traces securely
- Preserve MFA prompt history, device registration and session details
Explanation
Correct Answer
D:For evidence selection and preservation involving “Preserve MFA prompt history, device” and the report “new trusted device registered to their account”, the evidence links a push event to resulting account changes. “Revoke suspicious sessions and remove unauthorized registered authenticators” is the specific follow-up action.
Incorrect Answers
A:For evidence selection and preservation, contrasting “Preserve container inventory, MDM ownership” with “new trusted device registered to their account”, accurate scope identifies data the enterprise is permitted to remove. The comparison turns on “new trusted device registered to their account” versus “history device registration and session details”.
B:For evidence selection and preservation, contrasting “Preserve network profile settings, certificate” with “new trusted device registered to their account”, the record identifies what identity checks the client actually performed. The case fact “new trusted device registered to their account” makes “MFA prompt history device registration” the better test.
C:For evidence selection and preservation, contrasting “Preserve application storage findings and” with “new trusted device registered to their account”, evidence should demonstrate exploitability without publishing live credentials. “MFA prompt history device registration and session” is the criterion not satisfied for “new trusted device registered to their account”.
Question 587
An online catalog search endpoint produces SQL error details when a quotation mark is entered and returns unexpected records for crafted input. Which action best balances containment and preservation needs?
- Suspend unsafe XML handling and restrict the service's internal egress
- Block access from the workload to metadata and unapproved private ranges
- Restrict the vulnerable endpoint or deploy a narrowly tested virtual patch
- Disable the vulnerable deserialization endpoint and isolate implicated hosts
- Restrict the affected query feature and review directory account permissions
- Disable the affected conversion feature and isolate the execution host
Explanation
Correct Answer
C:For immediate response and containment involving “Restrict the vulnerable endpoint or” and the report “and returns unexpected records for crafted input”, short-term control reduces exploitation while code owners prepare a durable fix. “Preserve application requests, sanitized SQL telemetry and affected database access logs” is the artifact-preservation requirement.
Incorrect Answers
A:Containment prevents further retrieval of protected resources. In “and returns unexpected records for crafted input”, the necessary control concerns “or deploy a narrowly tested virtual patch”.
B:For immediate response and containment, contrasting “Block access from the workload” with “and returns unexpected records for crafted input”, network restrictions reduce immediate exploitability while code changes proceed. For this “and returns unexpected records for crafted input” event, “vulnerable endpoint or deploy a narrowly tested” is still outstanding.
D:For immediate response and containment, contrasting “Disable the vulnerable deserialization endpoint” with “and returns unexpected records for crafted input”, temporary containment limits further code execution while the flaw is investigated. Here, “or deploy a narrowly tested virtual patch” must account for “and returns unexpected records for crafted input”.
E:For immediate response and containment, contrasting “Restrict the affected query feature” with “and returns unexpected records for crafted input”, containment reduces improper directory exposure without deleting evidence. “and returns unexpected records for crafted input” needs a more direct result for “or deploy a narrowly tested virtual patch”.
F:For immediate response and containment, contrasting “Disable the affected conversion feature” with “and returns unexpected records for crafted input”, containment stops new command execution while preserving service alternatives. The comparison turns on “and returns unexpected records for crafted input” versus “deploy a narrowly tested virtual patch”.
Question 588
A user clicks a crafted link and an authenticated banking site performs a sensitive state change without a deliberate confirmation. Which post-response observation most strongly supports resolution?
- Test cross-origin submissions are denied while legitimate workflows work
- Verify the payment page cannot be embedded inside an external frame
- Verify dangerous markup is inert in every supported display context
- Verify approved scripts load and sensitive fields are not read unexpectedly
Explanation
Correct Answer
A:For recovery and closure validation involving “Test cross-origin submissions are denied” and the report “sensitive state change without a deliberate confirmation”, the control should reject forged actions rather than disable account updates. “Implement CSRF tokens and appropriate SameSite or origin validation” is a control change requiring validation.
Incorrect Answers
B:Frame restrictions mitigate clickjacking, not an authenticated cross-origin request that changes state. The recovery test must confirm forged submissions are rejected.
C:For recovery and closure validation, contrasting “Verify dangerous markup is inert” with “sensitive state change without a deliberate confirmation”, input filtering alone is not a reliable cross-context guarantee. “cross-origin submissions are denied while” cannot be inferred from that “sensitive state change without a deliberate confirmation” finding.
D:For recovery and closure validation, contrasting “Verify approved scripts load and” with “sensitive state change without a deliberate confirmation”, browser-side behavior must be assessed beyond server access logs. Only “submissions are denied while legitimate workflows” would test the “sensitive state change without a deliberate confirmation” condition.
Question 589
A low-severity endpoint alert sits on a workstation that administers the production backup system. Which immediate control should responders apply to this situation?
- Escalate the shared incident to identity response and warn affected users
- Merge coordination under a single owner while retaining child evidence
- Escalate to privacy and incident leadership according to policy
- Restrict the workstation's privileged sessions pending verification
Explanation
Correct Answer
D:For immediate response and containment involving “Restrict the workstation's privileged sessions” and the report “workstation that administers the production backup system”, reducing privileged reachability limits damage without assuming the suspicious binary is already confirmed malware. “Capture endpoint identity, privileged access paths, and linked backup assets” is the corroboration step, where safe.
Incorrect Answers
A:For immediate response and containment, contrasting “Escalate the shared incident to” with “workstation that administers the production backup system”, a coordinated communication avoids inconsistent individual password-reset instructions. “workstation that administers the production backup system” gives a different evidentiary target: “the workstation's privileged sessions pending”.
B:For immediate response and containment, contrasting “Merge coordination under a single” with “workstation that administers the production backup system”, deduplication should remove duplicate effort rather than discard separate observations. The incident detail “workstation that administers the production backup system” still calls for “the workstation's privileged sessions pending verification”.
C:For immediate response and containment, contrasting “Escalate to privacy and incident” with “workstation that administers the production backup system”, potential legal obligations require authorized evaluation without prematurely declaring a reportable breach. “workstation's privileged sessions pending verification” addresses a gap left by the “workstation that administers the production backup system” observation.
Question 590
Evidence collected at a remote office is sent through an unsecured consumer file-sharing link. What information should the first responder secure for later analysis?
- Document sender, recipient, transfer time, purpose and seal condition
- Photograph packaging condition and record the storage environment
- Preserve original file hashes and a log of who accessed the transfer
- Document legal approvals, destination examiner and transfer purpose
- Record retention triggers, holds, access roles and disposition authority
Explanation
Correct Answer
C:For evidence selection and preservation involving “Preserve original file hashes and” and the report “sent through an unsecured consumer file-sharing link”, source integrity and access history permit later review of exposure. “Revoke broad sharing and move evidence to an approved restricted repository” is the intervention evaluated after collection.
Incorrect Answers
A:For evidence selection and preservation, contrasting “Document sender, recipient, transfer time” with “sent through an unsecured consumer file-sharing link”, a complete custody entry supports accountability at the handoff. “original file hashes and” is the criterion not satisfied for “sent through an unsecured consumer file-sharing link”.
B:For evidence selection and preservation, contrasting “Photograph packaging condition and record” with “sent through an unsecured consumer file-sharing link”, documenting the defect distinguishes later handling from preexisting problems. For the “sent through an unsecured consumer file-sharing link” observation, “hashes and a log of who accessed” remains open.
D:For evidence selection and preservation, contrasting “Document legal approvals, destination examiner” with “sent through an unsecured consumer file-sharing link”, written authority supports lawful possession and use of the evidence. “original file hashes and” remains unverified against the reported “sent through an unsecured consumer file-sharing link”.
E:For evidence selection and preservation, contrasting “Record retention triggers, holds, access” with “sent through an unsecured consumer file-sharing link”, a custody plan needs explicit ownership and lawful storage duration. For “sent through an unsecured consumer file-sharing link”, the missing check concerns “original file hashes and a log”.