Question 850
Security analysts can query infrastructure changes but cannot tell which object data an attacker may have read. Which post-response observation most strongly supports resolution?
- Simulate denied out-of-scope operations and review continuing audit logs
- Confirm no unauthorized principals or inherited permissions remain
- Verify denied use of old credentials and approved data reads still succeed
- Verify snapshots and logs map to the original instance and time window
- Test representative reads are captured and alerts correlate with identities
Explanation
Correct Answer
E:For recovery and closure validation involving “Test representative reads are captured” and the report “object data an attacker may have read”, a policy statement without observed log entries is not verification. “Enable appropriately scoped object data-access auditing and retention” is a control change requiring validation.
Incorrect Answers
A:For recovery and closure validation, contrasting “Simulate denied out-of-scope operations and” with “object data an attacker may have read”, recovery must prove the role cannot repeat the observed overreach. The comparison turns on “object data an attacker may have read” versus “representative reads are captured and alerts”.
B:For recovery and closure validation, contrasting “Confirm no unauthorized principals or” with “object data an attacker may have read”, removing one obvious role binding may leave other escalated identities. The case fact “object data an attacker may have read” makes “representative reads are captured and alerts” the better test.
C:For recovery and closure validation, contrasting “Verify denied use of old” with “object data an attacker may have read”, a clean management log does not confirm data-plane security. “and alerts correlate with identities” is the criterion not satisfied for “object data an attacker may have read”.
D:For recovery and closure validation, contrasting “Verify snapshots and logs map” with “object data an attacker may have read”, chain of custody requires cloud resource identifiers and integrity records. For the “object data an attacker may have read” observation, “representative reads are captured and alerts correlate” remains open.
Question 851
A help desk receives five reports of suspicious password-reset prompts affecting one department at the same hour. What handling decision most directly interrupts further exposure?
- Escalate the shared incident to identity response and warn affected users
- Confirm the scan authorization before applying disruptive containment
- Restrict the workstation's privileged sessions pending verification
- Assign a single incident commander and escalate on the high-impact criteria
Explanation
Correct Answer
A:For immediate response and containment involving “Escalate the shared incident to” and the report “affecting one department at the same hour”, a coordinated communication avoids inconsistent individual password-reset instructions. “Create linked case records retaining each reporter and authentication timestamp” is the corroboration step, where safe.
Incorrect Answers
B:For immediate response and containment, contrasting “Confirm the scan authorization before” with “affecting one department at the same hour”, blocking approved assessment traffic without validation could interrupt a legitimate control test. For this “affecting one department at the same hour” event, “shared incident to identity response and warn” is still outstanding.
C:For immediate response and containment, contrasting “Restrict the workstation's privileged sessions” with “affecting one department at the same hour”, reducing privileged reachability limits damage without assuming the suspicious binary is already confirmed malware. “affecting one department at the same hour” is not evaluated through the “Escalate the shared incident to identity response” requirement.
D:For immediate response and containment, contrasting “Assign a single incident commander” with “affecting one department at the same hour”, central ownership prevents conflicting containment orders while the potential data exposure is assessed. Here, “to identity response and warn affected users” must account for “affecting one department at the same hour”.
Question 852
An endpoint sends large outbound transfers to an unfamiliar server immediately after an archive process runs. Which data source would most directly establish scope and provenance?
- Preserve proxy logs, DNS responses, endpoint processes and TLS metadata
- Preserve full DNS query logs, resolver traces and originating process data
- Collect east-west flow records, EDR process tree and account activity
- Correlate file access, archive creation, process lineage and network bytes
Explanation
Correct Answer
D:For evidence selection and preservation involving “Correlate file access, archive creation” and the report “server immediately after an archive process runs”, a combined timeline links the collected data to the external transfer. “Quarantine the endpoint and block the destination while preserving transfer logs” is the specific follow-up action.
Incorrect Answers
A:For evidence selection and preservation, contrasting “Preserve proxy logs, DNS responses” with “server immediately after an archive process runs”, cross-layer evidence helps attribute the communication to its initiating process. “server immediately after an archive process runs” is why proof of “file access archive creation process lineage” matters here.
B:For evidence selection and preservation, contrasting “Preserve full DNS query logs” with “server immediately after an archive process runs”, domain-only summaries miss the labels that can contain encoded payloads. The option does not link “server immediately after an archive process runs” to “file access archive creation”.
C:For evidence selection and preservation, contrasting “Collect east-west flow records, EDR” with “server immediately after an archive process runs”, these sources reveal whether the scans preceded credential reuse or payload movement. “file access archive creation” cannot be inferred from that “server immediately after an archive process runs” finding.
Question 853
A tenant shows a surge of new privileged access grants from a service identity that should never manage IAM. Which conclusion is the best starting hypothesis for triage?
- Recognize excessive IAM privilege increasing the breach blast radius
- Recognize an ephemeral evidence-readiness gap in automated infrastructure
- Recognize administrative privilege escalation through a compromised workload identity
- Recognize the difference between management-plane and data-access telemetry
Explanation
Correct Answer
C:For assessment and interpretation involving “Recognize administrative privilege escalation through” and the report “service identity that should never manage IAM”, unusual grants can create persistent human or machine access long after a key rotates. “Preserve IAM change records, caller identity and resulting policy versions” is an investigative cross-check.
Incorrect Answers
A:For assessment and interpretation, contrasting “Recognize excessive IAM privilege increasing” with “service identity that should never manage IAM”, a role able to administer unrelated services makes one workload compromise much more damaging. “service identity that should never manage IAM” gives a different evidentiary target: “escalation through a compromised workload identity”.
B:For assessment and interpretation, contrasting “Recognize an ephemeral evidence-readiness gap” with “service identity that should never manage IAM”, terminated instances can lose local state and associated short-retention logs. The incident detail “service identity that should never manage IAM” still calls for “administrative privilege escalation through a compromised workload”.
D:For assessment and interpretation, contrasting “Recognize the difference between management-plane” with “service identity that should never manage IAM”, administrative configuration logs may not cover every read of stored objects. Against “service identity that should never manage IAM”, this does not establish “privilege escalation through a compromised workload identity”.
Question 854
During a network incident, two SOAR systems issue conflicting firewall changes against the same destination. What is the most defensible interpretation of the observed situation?
- Require analyst approval for organization-wide destructive email actions
- Identify the lack of confidence and business-criticality checks
- Recognize competing playbook ownership and shared-state collisions
- Spot the gap between intake monitoring and accountable assignment
Explanation
Correct Answer
C:For assessment and interpretation involving “Recognize competing playbook ownership and” and the report “conflicting firewall changes against the same destination”, independent workflows can overwrite controls and obscure which change took effect. “Collect change identifiers, playbook histories and effective rule snapshots” is a source for testing the inference.
Incorrect Answers
A:For assessment and interpretation, contrasting “Require analyst approval for organization-wide” with “conflicting firewall changes against the same destination”, a human checkpoint is justified when automation could remove legitimate messages at scale. “competing playbook ownership and shared-state collisions” is the criterion not satisfied for “conflicting firewall changes against the same destination”.
B:For assessment and interpretation, contrasting “Identify the lack of confidence” with “conflicting firewall changes against the same destination”, automatic quarantine based on one weak indicator can cause disproportionate operational loss. For the “conflicting firewall changes against the same destination” observation, “playbook ownership and shared-state collisions” remains open.
D:For assessment and interpretation, contrasting “Spot the gap between intake” with “conflicting firewall changes against the same destination”, an alert cannot meet a response service level if no on-call individual accepts ownership. “competing playbook ownership and shared-state” remains unverified against the reported “conflicting firewall changes against the same destination”.
Question 855
A QR code in an email sends mobile users to a fraudulent authentication portal. What records would most clearly support validation of the reported activity?
- Preserve the email image and decoded URL with redirect chain
- Preserve challenge records, push denials and originating sign-in context
- Preserve URLs, landing-page captures, mail headers and identity sign-in logs
- Retain the original MIME attachment, hashes and execution telemetry
Explanation
Correct Answer
A:For evidence selection and preservation involving “Preserve the email image and” and the report “mobile users to a fraudulent authentication portal”, investigators need both the presented lure and actual destination. “Quarantine the campaign and alert mobile users not to follow the link” is the specific follow-up action.
Incorrect Answers
B:For evidence selection and preservation, contrasting “Preserve challenge records, push denials” with “mobile users to a fraudulent authentication portal”, authentication telemetry distinguishes malicious prompting from expected logins. Here, “image and decoded URL with redirect chain” must account for “mobile users to a fraudulent authentication portal”.
C:For evidence selection and preservation, contrasting “Preserve URLs, landing-page captures, mail” with “mobile users to a fraudulent authentication portal”, combining lure and authentication activity identifies victims and use of stolen credentials. “mobile users to a fraudulent authentication portal” needs a more direct result for “email image and decoded URL with redirect”.
D:For evidence selection and preservation, contrasting “Retain the original MIME attachment” with “mobile users to a fraudulent authentication portal”, unmodified evidence links the lure to any spawned process or network activity. The comparison turns on “mobile users to a fraudulent authentication portal” versus “the email image and decoded URL”.
Question 856
Security analysts can query infrastructure changes but cannot tell which object data an attacker may have read. Which information should be retained before the incident history is lost?
- Review role policies, assumed-role sessions and API event history
- Preserve IAM change records, caller identity and resulting policy versions
- Preserve instance metadata, boot logs and authorized volume snapshots
- Preserve secret-exposure timing, audit events and repository revision history
- Identify enabled data-access logs, object paths and relevant request identities
Explanation
Correct Answer
E:For evidence selection and preservation involving “Identify enabled data-access logs, object” and the report “object data an attacker may have read”, evidence sufficiency depends on logging scope and retention at incident time. “Restrict suspect storage access and preserve available access logs immediately” is the containment decision supported by those artifacts.
Incorrect Answers
A:For evidence selection and preservation, contrasting “Review role policies, assumed-role sessions” with “object data an attacker may have read”, the evidence shows what the role could do and what it actually did. “enabled data-access logs object” cannot be inferred from that “object data an attacker may have read” finding.
B:For evidence selection and preservation, contrasting “Preserve IAM change records, caller” with “object data an attacker may have read”, grant chronology reveals both attacker origin and unauthorized recipients. Only “logs object paths and relevant request” would test the “object data an attacker may have read” condition.
C:For evidence selection and preservation, contrasting “Preserve instance metadata, boot logs” with “object data an attacker may have read”, snapshot and metadata capture can retain artifacts beyond VM lifetime. The “object data an attacker may have read” report requires a finding about “object paths and relevant request”.
D:For evidence selection and preservation, contrasting “Preserve secret-exposure timing, audit events” with “object data an attacker may have read”, access logs and publication chronology bound the potential compromise period. In “object data an attacker may have read”, the necessary control concerns “object paths and relevant request identities”.
Question 857
A public API logs only generic 500 errors and analysts cannot determine which users triggered a recent access-control failure. What is the most defensible interpretation of the observed situation?
- Recognize virtual patching as a compensating control, not necessarily eradication
- Recognize unpatched third-party components in the runtime artifact
- Recognize insufficient security audit context in application logging
- Recognize partial recovery caused by inconsistent application state
Explanation
Correct Answer
C:For assessment and interpretation involving “Recognize insufficient security audit context” and the report “which users triggered a recent access-control failure”, without principal, endpoint and decision detail, investigations cannot reconstruct abuse. “Record request identifiers, actor identity, resource and authorization outcome” is a corroborating evidence path.
Incorrect Answers
A:For assessment and interpretation, contrasting “Recognize virtual patching as a” with “which users triggered a recent access-control failure”, attackers may bypass signature matching while vulnerable logic remains. “insufficient security audit context in application” addresses a gap left by the “which users triggered a recent access-control failure” observation.
B:For assessment and interpretation, contrasting “Recognize unpatched third-party components in” with “which users triggered a recent access-control failure”, source-code remediation does not update embedded libraries in shipped images. Against “which users triggered a recent access-control failure”, this does not establish “insufficient security audit context in application logging”.
D:For assessment and interpretation, contrasting “Recognize partial recovery caused by” with “which users triggered a recent access-control failure”, restoring compute without coherent dependent state can leave users unable to sign in. “which users triggered a recent access-control failure” is why proof of “insufficient security audit context” matters here.
Question 858
A Microsoft Entra application registration gains a high-privilege delegated consent outside the approved change window. What is the best immediate step for the on-call response team?
- Revoke the unauthorized grant and associated sessions or credentials
- Assign manual ownership and use a safe alternate notification channel
- Isolate the affected workload through approved network or endpoint response controls
- Revert network restrictions that were not part of the application-consent change
Explanation
Correct Answer
A:For immediate response and containment involving “Revoke the unauthorized grant and” and the report “delegated consent outside the approved change window”, containment cuts off app-based access while evaluating downstream activity. “Collect Entra audit and sign-in logs plus granted permission scopes” is the corroboration step, where safe.
Incorrect Answers
B:For immediate response and containment, contrasting “Assign manual ownership and use” with “delegated consent outside the approved change window”, operational continuity matters while playbook faults are corrected. “unauthorized grant and associated sessions or credentials” remains unverified against the reported “delegated consent outside the approved change window”.
C:For immediate response and containment, contrasting “Isolate the affected workload through” with “delegated consent outside the approved change window”, restriction reduces spread while preserving necessary investigation access. For “delegated consent outside the approved change window”, the missing check concerns “unauthorized grant and associated sessions or credentials”.
D:Network rule rollback does not remove a newly granted OAuth or Entra consent. The specific application permissions and usable tokens remain active until revoked or constrained.
Question 859
An IoT gateway accepts unsigned firmware packages from an update server that may have been compromised. What should be changed to prevent recurrence rather than only quiet alerts?
- Require cryptographic firmware signatures and protected update channels
- Fix event forwarding and require logging regression checks for firmware releases
- Enforce segmentation and approved maintenance pathways at the gateway
- Enforce unique credentials and disable unused administration services
Explanation
Correct Answer
A:For eradication and systemic correction involving “Require cryptographic firmware signatures and” and the report “update server that may have been compromised”, device-side verification prevents installation of untrusted images. “Suspend suspicious updates and isolate affected gateways where safe” is the interim response.
Incorrect Answers
B:For eradication and systemic correction, contrasting “Fix event forwarding and require” with “update server that may have been compromised”, reliable auditing must be part of update acceptance criteria. The comparison turns on “update server that may have been compromised” versus “and protected update channels”.
C:For eradication and systemic correction, contrasting “Enforce segmentation and approved maintenance” with “update server that may have been compromised”, network design must prevent edge devices from bridging trust zones. The case fact “update server that may have been compromised” makes “cryptographic firmware signatures and protected update channels” the better test.
D:For eradication and systemic correction, contrasting “Enforce unique credentials and disable” with “update server that may have been compromised”, fleet-level policy removes the repeatable initial access route. “firmware signatures and protected update channels” is the criterion not satisfied for “update server that may have been compromised”.
Question 860
A session token remains usable for hours after a user clicks sign out on a finance portal. Which TWO measures together limit the active risk and repair its underlying cause? Choose TWO.
- Revoke affected sessions and reduce exposure of reusable tokens
- Reject tokens with incorrect issuer or audience at the API boundary
- Disable dangerous update fields until server-side checks are deployed
- Invalidate exposed reset codes and protect affected accounts
- Implement reliable server-side revocation or short-lived tokens with rotation
- Make recovery tokens single-use, expiring and bound to an intended account
Explanation
Correct Answers
A:For immediate response and containment involving “Revoke affected sessions and reduce” and the report “clicks sign out on a finance portal”, immediate invalidation cuts off access from stolen or stale credentials. “Preserve issuance, logout and subsequent API usage records” is a separate forensic preservation step.
E:For immediate response and containment involving “Implement reliable server-side revocation or” and the report “clicks sign out on a finance portal”, session design must reflect intended termination semantics. “Preserve issuance, logout and subsequent API usage records” is a time-sensitive forensic step.
Incorrect Answers
B:For immediate response and containment, contrasting “Reject tokens with incorrect issuer” with “clicks sign out on a finance portal”, targeted validation blocks cross-service token replay. In “clicks sign out on a finance portal”, the necessary control concerns “server-side revocation or short-lived”.
C:For immediate response and containment, contrasting “Disable dangerous update fields until” with “clicks sign out on a finance portal”, narrow containment prevents further account manipulation. For this “clicks sign out on a finance portal” event, “affected sessions and reduce exposure” is still outstanding.
D:For immediate response and containment, contrasting “Invalidate exposed reset codes and” with “clicks sign out on a finance portal”, containment blocks replay while administrators assess unauthorized changes. “clicks sign out on a finance portal” is not evaluated through the “server-side revocation or short-lived tokens with rotation” requirement.
F:For immediate response and containment, contrasting “Make recovery tokens single-use, expiring” with “clicks sign out on a finance portal”, secure recovery must enforce token lifecycle server-side. “clicks sign out on a finance portal” needs a more direct result for “reliable server-side revocation or short-lived”.