Question 200
An attacker alters the body of a signed email after it leaves the sending service. How should the responder classify the central risk described?
- Recognize message-integrity failure detectable by DKIM validation
- Recognize an SPF evaluation configuration problem
- Recognize failed identifier alignment for an authorized external sender
- Recognize display-domain spoofing requiring authentication alignment checks
- Recognize forwarding-related SPF failure and evaluate any aligned DKIM pass
Explanation
Correct Answer
A:A changed signed body can invalidate the hash protected by the signature. “Inspect DKIM-Signature fields, body hash and verifier results” is a check against premature conclusions.
Incorrect Answers
B:For assessment and interpretation, contrasting “Recognize an SPF evaluation configuration” with “email after it leaves the sending service”, the SPF specification limits DNS-lookup mechanisms, and overcomplex policies can fail evaluation. In “email after it leaves the sending service”, the necessary control concerns “message-integrity failure detectable by DKIM”.
C:For assessment and interpretation, contrasting “Recognize failed identifier alignment for” with “email after it leaves the sending service”, mail may pass an underlying check yet fail DMARC if the authenticated domain differs from visible From. For this “email after it leaves the sending service” event, “message-integrity failure detectable by DKIM validation” is still outstanding.
D:For assessment and interpretation, contrasting “Recognize display-domain spoofing requiring authentication” with “email after it leaves the sending service”, a familiar header name does not establish authorization to send as the domain. “email after it leaves the sending service” is not evaluated through the “failure detectable by DKIM validation” requirement.
E:Forwarding changes sending IP context. Here, “message-integrity failure detectable” must account for “email after it leaves the sending service”.
Question 201
Two analysts independently open cases for the same malicious OAuth consent event in a shared tenant. Which verification best confirms that the original weakness is controlled?
- Validate that no privileged changes occurred during the suspicious interval
- Confirm impacted accounts and downstream sign-ins were individually reviewed
- Check that every original alert is represented in the final evidence timeline
- Demonstrate that unauthorized scans still trigger the detection
Explanation
Correct Answer
C:For recovery and closure validation involving “Check that every original alert” and the report “OAuth consent event in a shared tenant”, successful consolidation must not erase a unique detection or action history. “Implement incident correlation keyed on app consent and identity context” is a control change requiring validation.
Incorrect Answers
A:For recovery and closure validation, contrasting “Validate that no privileged changes” with “OAuth consent event in a shared tenant”, recovery confidence depends on checking sensitive backup control actions, not clearing an endpoint alert. For “is represented in the final evidence timeline”, the case record must resolve “OAuth consent event in a shared tenant”.
B:For recovery and closure validation, contrasting “Confirm impacted accounts and downstream” with “OAuth consent event in a shared tenant”, a common incident must not conceal an uninvestigated account takeover. “OAuth consent event in a shared tenant” is why proof of “alert is represented in the final evidence” matters here.
D:For recovery and closure validation, contrasting “Demonstrate that unauthorized scans still” with “OAuth consent event in a shared tenant”, a safe closure test proves the new rule did not blind the SOC to similar attacker behavior. “original alert is represented in the final” cannot be inferred from that “OAuth consent event in a shared tenant” finding.
Question 202
An IT engineer uses a shared administrator account, so investigators cannot tell who changed payroll permissions. Which measurement demonstrates that expected protections now hold?
- Verify sensitive changes map to identifiable users and approved sessions
- Verify no dormant emergency roles remain and authorized break-glass access works
- Test EDR telemetry across previously excluded endpoints after restoration
- Test that a developer cannot merge and release unreviewed security changes
Explanation
Correct Answer
A:A logging system is useful only if identities are personally attributable. “Implement individual privileged access with monitored elevation and credential vaulting” is the correction whose effectiveness is being retested.
Incorrect Answers
B:For recovery and closure validation, contrasting “Verify no dormant emergency roles” with “investigators cannot tell who changed payroll permissions”, the organization needs both least privilege and a tested emergency process. “investigators cannot tell who changed payroll permissions” gives a different evidentiary target: “sensitive changes map to identifiable users”.
C:For recovery and closure validation, contrasting “Test EDR telemetry across previously” with “investigators cannot tell who changed payroll permissions”, re-enabling a toggle does not prove events are reaching the SOC. The incident detail “investigators cannot tell who changed payroll permissions” still calls for “sensitive changes map to identifiable users”.
D:For recovery and closure validation, contrasting “Test that a developer cannot” with “investigators cannot tell who changed payroll permissions”, workflow design must be proven with negative permission tests. “map to identifiable users and approved sessions” addresses a gap left by the “investigators cannot tell who changed payroll permissions” observation.
Question 203
Multiple security alerts describe a payment API outage and possible exposure of customer records; business owners disagree about urgency. Which action best balances containment and preservation needs?
- Merge coordination under a single owner while retaining child evidence
- Escalate to privacy and incident leadership according to policy
- Escalate the shared incident to identity response and warn affected users
- Assign a single incident commander and escalate on the high-impact criteria
Explanation
Correct Answer
D:For immediate response and containment involving “Assign a single incident commander” and the report “customer records; business owners disagree about urgency”, central ownership prevents conflicting containment orders while the potential data exposure is assessed. “Record affected service, data categories, onset, and owner in one incident ticket” is a time-sensitive forensic step.
Incorrect Answers
A:Deduplication should remove duplicate effort rather than discard separate observations. The case fact “customer records; business owners disagree about urgency” makes “incident commander and escalate on the high-impact” the better test.
B:For immediate response and containment, contrasting “Escalate to privacy and incident” with “customer records; business owners disagree about urgency”, potential legal obligations require authorized evaluation without prematurely declaring a reportable breach. “Assign a single” is the criterion not satisfied for “customer records; business owners disagree about urgency”.
C:For immediate response and containment, contrasting “Escalate the shared incident to” with “customer records; business owners disagree about urgency”, a coordinated communication avoids inconsistent individual password-reset instructions. For the “customer records; business owners disagree about urgency” observation, “on the high-impact criteria” remains open.
Question 204
A suspected attacker changes network security group rules through Azure management APIs. Which THREE steps together preserve evidence, contain present exposure, and correct the root weakness? Choose THREE.
- Inspect incident automation history, playbook runs and identity permissions
- Revert unauthorized rules and disable or constrain the initiating principal
- Assign manual ownership and use a safe alternate notification channel
- Require controlled admin consent workflows and permission reviews
- Preserve Azure Activity Log records, caller identity and NSG rule history
- Enforce least-privilege Azure RBAC and policy-based change governance
Explanation
Correct Answers
B:For assessment and interpretation involving “Revert unauthorized rules and disable” and the report “security group rules through Azure management APIs”, network and identity containment stops further exposure. The linked case facts, including “network security group rules through Azure management APIs”, should be preserved for independent review.
E:For assessment and interpretation involving “Preserve Azure Activity Log records” and the report “security group rules through Azure management APIs”, resource management events provide the timeline and actor behind policy modification. For assessment and interpretation involving “Preserve Azure Activity Log records” and the report “security group rules through Azure management APIs”, the linked case facts, including “network security group rules through Azure management APIs”, should be preserved for independent review.
F:For assessment and interpretation involving “Enforce least-privilege Azure RBAC and” and the report “security group rules through Azure management APIs”, preventing unauthorized updates addresses the administrative boundary. For assessment and interpretation involving “Enforce least-privilege Azure RBAC and” and the report “security group rules through Azure management APIs”, the linked case facts, including “network security group rules through Azure management APIs”, should be preserved for independent review.
Incorrect Answers
A:For assessment and interpretation, contrasting “Inspect incident automation history, playbook” with “security group rules through Azure management APIs”, runtime and role data reveal whether trigger, authorization or connector failed. For this “security group rules through Azure management APIs” event, “Revert unauthorized rules and disable or” is still outstanding.
C:For assessment and interpretation, contrasting “Assign manual ownership and use” with “security group rules through Azure management APIs”, operational continuity matters while playbook faults are corrected. Here, “Revert unauthorized rules and disable” must account for “security group rules through Azure management APIs”.
D:For assessment and interpretation, contrasting “Require controlled admin consent workflows” with “security group rules through Azure management APIs”, governed application onboarding reduces future privilege abuse. “security group rules through Azure management APIs” needs a more direct result for “Revert unauthorized rules and disable”.
Question 205
A workstation EDR alert reports a signed office process spawning a command interpreter that downloads a script. Which inference would best shape the next investigative step?
- Recognize the weakness of detection without an accurate software baseline
- Recognize suspicious parent-child execution despite the signed parent
- Recognize incomplete endpoint isolation across active interfaces
- Recognize autostart persistence associated with a transient file location
Explanation
Correct Answer
B:For assessment and interpretation involving “Recognize suspicious parent-child execution despite” and the report “a command interpreter that downloads a script”, a legitimate application can be abused to launch unexpected secondary commands. “Preserve process command lines, parent ancestry, script hash and network destinations” is a separate source of incident context.
Incorrect Answers
A:For assessment and interpretation, contrasting “Recognize the weakness of detection” with “a command interpreter that downloads a script”, unknown executables are difficult to interpret when legitimate deployments are undocumented. The option does not link “a command interpreter that downloads a script” to “parent-child execution despite the signed parent”.
C:For assessment and interpretation, contrasting “Recognize incomplete endpoint isolation across” with “a command interpreter that downloads a script”, a control can appear successful while another network path remains usable. Only “parent-child execution despite the signed parent” would test the “a command interpreter that downloads a script” condition.
D:For assessment and interpretation, contrasting “Recognize autostart persistence associated with” with “a command interpreter that downloads a script”, repeated execution after boot suggests a scheduled or registry-based launcher. The “a command interpreter that downloads a script” report requires a finding about “parent-child execution despite the signed parent”.
Question 206
An insider investigation manager asks the SOC to search an employee's private communications without legal review. What recovery test specifically addresses the earlier failure mode?
- Verify effective permissions match the new job function
- Audit that only approved evidence was accessed and shared
- Test report handling and verify access is limited to authorized reviewers
- Verify all linked accounts, tokens and physical access were removed
Explanation
Correct Answer
B:A defensible investigation documents compliance with its scope. “Create a joint investigation protocol with defined access and retention limits” is the remediation record that supports sign-off.
Incorrect Answers
A:A revoked explicit grant may still be inherited through old groups. The incident detail “an employee's private communications without legal review” still calls for “only approved evidence was accessed and shared”.
C:A reporting hotline is meaningful only if confidentiality and action follow. Against “an employee's private communications without legal review”, this does not establish “that only approved evidence was accessed”.
D:A single VPN disablement may leave other identity paths active. For “that only approved evidence was accessed”, the case record must resolve “an employee's private communications without legal review”.
Question 207
A shared mailbox has an unknown delegate who can send messages as the finance department. Which information should be retained before the incident history is lost?
- Collect message trace, recipient inventory and session login records
- Preserve consent events, app permissions, forwarding settings and access logs
- Preserve delegation history, sent items and administrative audit events
- Preserve mailbox audit entries, rule definitions and login details
Explanation
Correct Answer
C:For evidence selection and preservation involving “Preserve delegation history, sent items” and the report “can send messages as the finance department”, permission provenance connects unauthorized mail to an enabling change. “Remove unauthorized delegation and suspend the suspected principal” is the containment decision supported by those artifacts.
Incorrect Answers
A:For evidence selection and preservation, contrasting “Collect message trace, recipient inventory” with “can send messages as the finance department”, tracing deliveries helps identify recipients, campaign content and compromise onset. For the “can send messages as the finance department” observation, “delegation history sent items and administrative” remains open.
B:For evidence selection and preservation, contrasting “Preserve consent events, app permissions” with “can send messages as the finance department”, the combined evidence identifies whether data left through app or routing controls. The “history sent items and administrative audit” requirement follows from “can send messages as the finance department”.
D:For evidence selection and preservation, contrasting “Preserve mailbox audit entries, rule” with “can send messages as the finance department”, rule creation time and actor context show how the mailbox was manipulated. For “can send messages as the finance department”, the missing check concerns “delegation history sent items and”.
Question 208
Multiple security alerts describe a payment API outage and possible exposure of customer records; business owners disagree about urgency. What interpretation should guide the incident handler's first analysis?
- Prioritize by functional impact, information impact, and recovery effort
- Detect the common app ID, user, and consent timestamp
- Reassess the incident using confidentiality and regulatory impact
- Correlate reports by time, application, and affected identity group
Explanation
Correct Answer
A:A mixed availability and confidentiality event requires combined business-impact assessment rather than counting alerts alone. “Record affected service, data categories, onset, and owner in one incident ticket” is a corroborating evidence path.
Incorrect Answers
B:An entity-based correlation reveals one incident represented by multiple alert sources. “customer records; business owners disagree about urgency” needs a more direct result for “functional impact information impact and recovery”.
C:Generic alert severity cannot override potentially substantial harm from sensitive information exposure. The comparison turns on “customer records; business owners disagree about urgency” versus “Prioritize by functional impact information”.
D:A clustered pattern can indicate a coordinated credential attack rather than five unrelated tickets. The case fact “customer records; business owners disagree about urgency” makes “impact information impact and recovery effort” the better test.
Question 209
A network appliance displays an unfamiliar administrator account recreated after every configuration rollback. What initial handling step should the incident commander coordinate?
- Restrict management access to a trusted recovery network and rotate secrets
- Disable the extension across managed profiles and revoke at-risk sessions
- Isolate the host while collecting volatile evidence under authorized procedures
- Disconnect the host and avoid unplanned firmware updates during evidence collection
- Network-isolate the laptop while acquiring its process and persistence state
Explanation
Correct Answer
A:For immediate response and containment involving “Restrict management access to a” and the report “administrator account recreated after every configuration rollback”, containment blocks continued unauthorized control of the device. “Export configuration history, account events and management access logs” is a separate forensic preservation step.
Incorrect Answers
B:For immediate response and containment, contrasting “Disable the extension across managed” with “administrator account recreated after every configuration rollback”, removal plus session containment limits ongoing credential or content access. The “administrator account recreated after every configuration rollback” report requires a finding about “management access to a trusted recovery”.
C:For immediate response and containment, contrasting “Isolate the host while collecting” with “administrator account recreated after every configuration rollback”, terminating the process too soon may destroy the best evidence. In “administrator account recreated after every configuration rollback”, the necessary control concerns “management access to a trusted recovery network”.
D:For immediate response and containment, contrasting “Disconnect the host and avoid” with “administrator account recreated after every configuration rollback”, containment and controlled preservation prevent obscuring the boot state. For this “administrator account recreated after every configuration rollback” event, “a trusted recovery network and rotate secrets” is still outstanding.
E:For immediate response and containment, contrasting “Network-isolate the laptop while acquiring” with “administrator account recreated after every configuration rollback”, containment prevents outbound control without erasing startup evidence. “administrator account recreated after every configuration rollback” is not evaluated through the “trusted recovery network and rotate secrets” requirement.
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”.