Question 40
A new ransomware playbook has never been tested with service owners or backup administrators. The team takes this action: Run a cross-team tabletop and fix documented decision or access failures. Which check most directly verifies the intended outcome?
- Participants demonstrate escalation and recovery decisions in a repeat exercise
- Evidence is timestamped, hashed where appropriate and linked to a chain-of-custody record
- Subsequent updates reconcile new evidence with earlier statements transparently
- The approved alternative limits attacker access without disrupting safety operations
Explanation
Correct Answer
A:Measurable corrections matter more than attendance statistics. That verification specifically tests whether the intervention to run a cross-team tabletop and fix documented decision or access failures corrected the issue rather than merely hiding an alert.
Incorrect Answers
B:A copied file without provenance has reduced investigative value; prioritizing that evidence preservation order mechanism would leave this response readiness exercise decision unresolved because participants demonstrate escalation and recovery decisions in a repeat exercise is the direct fit.
C:Credible communication includes corrections and documented decisions; applied to this response readiness exercise case, it addresses evidence-based stakeholder updates instead of the required step: participants demonstrate escalation and recovery decisions in a repeat exercise.
D:This relates to playbook exception handling: evidence must cover both threat reduction and process continuity; the response readiness exercise question instead requires demonstrating that the remediation or control took effect, specifically participants demonstrate escalation and recovery decisions in a repeat exercise.
Question 41
A standard user receives HTTP 200 for administrator-only API resources after changing an object ID. Supporting evidence includes: API access logs joined to role entitlements and object ownership. Which next step most directly reduces the described risk?
- Escalate potential code execution and protect the endpoint while investigating
- Create a SIEM correlation from WAF input to database anomalies
- Detect cross-tenant or unauthorized-object access and escalate for code remediation
- Correlate unusual script execution reports with submitted content changes
Explanation
Correct Answer
C:A WAF path rule cannot replace server-side authorization checks. For safe case progression, preserve the evidence and later verify replayed unauthorized requests receive denial while permitted requests still work.
Incorrect Answers
A:Suppressing crash logs would hide an important exploit signal; prioritizing that application crash exploitation mechanism would leave this broken access control decision unresolved because detect cross-tenant or unauthorized-object access and escalate for code remediation is the direct fit.
B:A generic 500-status spike lacks the payload specificity for SQL injection; that is suited to investigating SQL injection detection, whereas the broken access control case requires detect cross-tenant or unauthorized-object access and escalate for code remediation for choosing the immediate operational response.
D:Blocking all JavaScript can break the application without fixing output encoding; this evidence or action is associated with cross-site scripting telemetry, whereas the case concerns broken access control and calls for detect cross-tenant or unauthorized-object access and escalate for code remediation.
Question 42
A dashboard shows an unusual failed-login spike but offers no way to investigate affected users. Select the most discriminating sign for the SOC assessment.
- Acknowledgment compliance hides a missed containment service objective
- A collection-scope increase explains part of the apparent incident increase
- A control requires traceable privileged changes and accountable identities
- Technical alert counts alone do not communicate risk and response outcomes
- Aggregate counts lack entity and event-level investigation context
Explanation
Correct Answer
E:A useful dashboard should let analysts move from trend to underlying evidence. Confirmation should then examine source events with identity, origin and failure reason fields; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
A:The alternative concerns SOC SLA breach: different SLA stages measure different responsibilities and risk exposures; however, the described SOC dashboard drilldown situation calls for aggregate counts lack entity and event-level investigation context.
B:Changes in sensor coverage can affect counts without changing attack frequency; applied to this SOC dashboard drilldown case, it addresses incident trend analysis instead of the required step: aggregate counts lack entity and event-level investigation context.
C:Compliance detection should map to a specific control objective and evidence; that is suited to investigating compliance use case, whereas the SOC dashboard drilldown case requires aggregate counts lack entity and event-level investigation context for recognizing the distinguishing signal.
D:This relates to executive SOC report: leadership needs trends, incident impact, coverage gaps and action ownership; the SOC dashboard drilldown question instead requires recognizing the distinguishing signal, specifically aggregate counts lack entity and event-level investigation context.
Question 43
To verify remediation of log retention tiers, the team reports taking this action: Apply policy-driven hot retention plus protected long-term storage. Which outcome should the analyst demand?
- A burst test is delivered without gaps through simulated link impairment
- Attempts to alter archived logs fail or produce verifiable audit traces
- Backlog clears and generated test events reach the index within the SLA
- A historical test event remains retrievable and its integrity is demonstrable
Explanation
Correct Answer
D:Retention success includes recovery of useful evidence, not just object existence. That verification specifically tests whether the intervention to apply policy-driven hot retention plus protected long-term storage corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:Normal low-volume success does not validate reliable peak delivery, which would be relevant to Syslog transport reliability, but not the log retention tiers scenario that requires a historical test event remains retrievable and its integrity is demonstrable.
B:The alternative concerns log integrity: a normal query result does not by itself establish tamper resistance; however, the described log retention tiers situation calls for a historical test event remains retrievable and its integrity is demonstrable.
C:A functioning collector process alone does not prove current ingestion health; this evidence or action is associated with collector backlog monitoring, whereas the case concerns log retention tiers and calls for a historical test event remains retrievable and its integrity is demonstrable.
Question 44
A cloud SOC needs to alert on suspicious sign-ins already ingested into a Log Analytics workspace. Supporting evidence includes: Sentinel workspace data tables, connector status and analytic rule query. Which next step most directly reduces the described risk?
- Correct least-privilege access and monitor use of service identities
- Stream relevant Activity Log events to monitored storage or workspace
- Investigate the activation and enforce appropriate privileged access policy
- Create and test a Sentinel analytic rule with entity mapping and incident settings
Explanation
Correct Answer
D:Enabling the service without analytic content will not detect the behavior. The response must subsequently be checked by confirming a known suspicious sign-in produces an incident with correct user and IP entities; otherwise the original exposure may persist.
Incorrect Answers
A:Demanding host hypervisor logs from the provider would not fix tenant grants; applied to this Microsoft Sentinel analytic case, it addresses cloud shared responsibility instead of the required step: create and test a Sentinel analytic rule with entity mapping and incident settings.
B:Collecting only VM Security events misses resource-management changes; applied to this Microsoft Sentinel analytic case, it addresses Azure activity log visibility instead of the required step: create and test a Sentinel analytic rule with entity mapping and incident settings.
C:The alternative concerns Azure privileged identity: rotating a storage account key would not constrain directory role activation; however, the described Microsoft Sentinel analytic situation calls for create and test a Sentinel analytic rule with entity mapping and incident settings.
Question 45
Several endpoints start launching the same malicious payload across reachable network shares. Which finding best distinguishes this activity from a routine operational change?
- Self-propagating executions occur over accessible hosts and shares
- Unexpected sustained compute and known mining-protocol communication
- Extension permissions and background requests exceed approved browsing behavior
- Installer ancestry leads to unauthorized persistence and outbound control traffic
Explanation
Correct Answer
A:A worm moves via a repeatable exploitation or authentication path. Investigators should still corroborate it with cross-host process telemetry, SMB sessions and first-seen timeline before assigning definitive scope or attribution.
Incorrect Answers
B:The alternative concerns cryptomining compromise: malicious mining may be a symptom of a broader server intrusion; however, the described worm propagation situation calls for self-propagating executions occur over accessible hosts and shares.
C:Extensions can access page content and create network traffic independent of user clicks; this evidence or action is associated with malicious browser extension, whereas the case concerns worm propagation and calls for self-propagating executions occur over accessible hosts and shares.
D:This relates to trojanized installer: signed or seemingly functional software can carry an additional malicious payload; the worm propagation question instead requires recognizing the distinguishing signal, specifically self-propagating executions occur over accessible hosts and shares.
Question 46
Responders addressed low-and-slow beacon using this measure: Correlate periodic network activity with uncommon binary and domain context. What should the SOC test before considering closure?
- Benign typo traffic stays below threshold and test DGA sequences are flagged
- Legitimate request success recovers and abusive rate tests are throttled
- Authorized integrations remain usable while the tested unauthorized path is denied
- Suspicious simulated callbacks alert while approved telemetry agents are excluded narrowly
Explanation
Correct Answer
D:The suppression must identify vetted software rather than arbitrary destinations. That verification specifically tests whether the intervention to correlate periodic network activity with uncommon binary and domain context corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:For DNS algorithmic names, a good rule controls false positives from software probes; here the narrower objective is demonstrating that the remediation or control took effect in low-and-slow beacon, best addressed by suspicious simulated callbacks alert while approved telemetry agents are excluded narrowly.
B:This relates to HTTP request flood: blocking all traffic would not meet availability goals; the low-and-slow beacon question instead requires demonstrating that the remediation or control took effect, specifically suspicious simulated callbacks alert while approved telemetry agents are excluded narrowly.
C:Verification needs both security and application health evidence, which would be relevant to unexpected outbound port, but not the low-and-slow beacon scenario that requires suspicious simulated callbacks alert while approved telemetry agents are excluded narrowly.
Question 47
Responders addressed cloud logging gap using this measure: Automate audit onboarding and open coverage gaps as operational incidents. What should the SOC test before considering closure?
- Known unauthorized data reads stop and authorized service throughput remains intact
- Synthetic administrative activity from every new account reaches the SIEM
- Exposure is closed and a repeated unauthorized update triggers an alert
- Unapproved grant is removed and app API calls stop while approved apps work
Explanation
Correct Answer
B:A healthy connector in only one existing account is insufficient. That verification specifically tests whether the intervention to automate audit onboarding and open coverage gaps as operational incidents corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:This relates to cloud data download: review permissions and access events after the change; the cloud logging gap question instead requires demonstrating that the remediation or control took effect, specifically synthetic administrative activity from every new account reaches the SIEM.
C:Rule state and future detection both matter, which would be relevant to cloud control-plane edit, but not the cloud logging gap scenario that requires synthetic administrative activity from every new account reaches the SIEM.
D:For oAuth consent anomaly, portal logout alone is not a reliable revocation test; here the narrower objective is demonstrating that the remediation or control took effect in cloud logging gap, best addressed by synthetic administrative activity from every new account reaches the SIEM.
Question 48
Analysts confirm the following observation: Known token identity appears from an unapproved client origin and action set. Supporting material includes: API gateway token ID, client IP, scope and request traces. Which operational action addresses the issue most directly?
- Create a SIEM correlation from WAF input to database anomalies
- Escalate potential code execution and protect the endpoint while investigating
- Detect cross-tenant or unauthorized-object access and escalate for code remediation
- Correlate unusual script execution reports with submitted content changes
- Correlate token identity with client allowlists and revoke confirmed stolen secrets
Explanation
Correct Answer
E:Rotating an unrelated user's password would not invalidate this token. Operational success is not assumed until old token use fails and the replacement follows expected source restrictions, the relevant outcome for this response.
Incorrect Answers
A:A generic 500-status spike lacks the payload specificity for SQL injection; that is suited to investigating SQL injection detection, whereas the API token misuse case requires correlate token identity with client allowlists and revoke confirmed stolen secrets for choosing the immediate operational response.
B:Suppressing crash logs would hide an important exploit signal; prioritizing that application crash exploitation mechanism would leave this API token misuse decision unresolved because correlate token identity with client allowlists and revoke confirmed stolen secrets is the direct fit.
C:For broken access control, a WAF path rule cannot replace server-side authorization checks; here the narrower objective is choosing the immediate operational response in API token misuse, best addressed by correlate token identity with client allowlists and revoke confirmed stolen secrets.
D:Blocking all JavaScript can break the application without fixing output encoding; this evidence or action is associated with cross-site scripting telemetry, whereas the case concerns API token misuse and calls for correlate token identity with client allowlists and revoke confirmed stolen secrets.
Question 49
An alert suggests low-and-slow beacon. The recorded clue is: Repeated intervals with low timing variance suggest automated callbacks. What evidence would best test this hypothesis?
- Proxy flows, connection timestamps and owning endpoint process
- Resolver answer codes, query entropy and endpoint context
- TLS handshake metadata, SNI and approved certificate rotation records
- WAF request logs, endpoint latency and origin application metrics
Explanation
Correct Answer
A:Timing statistics coupled with destination reputation distinguish routine polling. This is particularly useful after the initial sign of repeated intervals with low timing variance suggest automated callbacks; the two forms of evidence test different parts of the case.
Incorrect Answers
B:This relates to DNS algorithmic names: the combined pattern is more robust than domain length alone; the low-and-slow beacon question instead requires independently corroborating the suspected behavior, specifically proxy flows, connection timestamps and owning endpoint process.
C:The alternative concerns TLS certificate anomaly: certificate validity alone does not explain whether a change is authorized; however, the described low-and-slow beacon situation calls for proxy flows, connection timestamps and owning endpoint process.
D:Client patterns and resource saturation distinguish attack from successful promotion; that is suited to investigating HTTP request flood, whereas the low-and-slow beacon case requires proxy flows, connection timestamps and owning endpoint process for independently corroborating the suspected behavior.
Question 50
The team has responded to hunt data gap using this measure: Record the coverage limitation and onboard necessary audit sources. Which post-action evidence would justify declaring the measure effective?
- The hunt records evidence for or against the hypothesis and creates detection improvements
- Test outliers are detected without flagging expected high-volume service traffic
- A test API call becomes observable before the hunt is repeated
- Future matching tasks create actionable alerts with assigned responders
Explanation
Correct Answer
C:Measurable telemetry readiness precedes defensible negative conclusions. It documents the result of this response step—Record the coverage limitation and onboard necessary audit sources—and helps determine whether the protective state persists.
Incorrect Answers
A:A zero-findings hunt can still be useful if coverage was verified; prioritizing that hypothesis-driven hunt mechanism would leave this hunt data gap decision unresolved because a test API call becomes observable before the hunt is repeated is the direct fit.
B:The alternative concerns hunt peer baselines: good hunt quality depends on discriminating abnormal from merely uncommon; however, the described hunt data gap situation calls for a test API call becomes observable before the hunt is repeated.
D:Operationalization turns a one-off hunt into sustained coverage; applied to this hunt data gap case, it addresses hunt handoff instead of the required step: a test API call becomes observable before the hunt is repeated.