Question 70
During an investigation of hypothesis-driven hunt, the SOC validates this finding: A hunt hypothesis predicts observable activity despite no existing detection. What should the response owner do next?
- Open an incident for confirmed findings and transfer an analytic to rule owners
- Record the coverage limitation and onboard necessary audit sources
- Form an ATT&CK-aligned hypothesis and query cross-host telemetry
- Build role-specific baselines and investigate deviations within the proper group
Explanation
Correct Answer
C:Searching random suspicious strings without a question rarely produces repeatable insight. For safe case progression, preserve the evidence and later verify the hunt records evidence for or against the hypothesis and creates detection improvements.
Incorrect Answers
A:Simply keeping a private notebook prevents ongoing monitoring; this evidence or action is associated with hunt handoff, whereas the case concerns hypothesis-driven hunt and calls for form an ATT&CK-aligned hypothesis and query cross-host telemetry.
B:Closing the hypothesis as false would misstate investigative confidence; that is suited to investigating hunt data gap, whereas the hypothesis-driven hunt case requires form an ATT&CK-aligned hypothesis and query cross-host telemetry for choosing the immediate operational response.
D:For hunt peer baselines, a one-size-fits-all global rate misses context and drives false positives; here the narrower objective is choosing the immediate operational response in hypothesis-driven hunt, best addressed by form an ATT&CK-aligned hypothesis and query cross-host telemetry.
Question 71
The first-line team is investigating insider database extraction. Its preliminary finding is: High-volume sensitive reads may breach the user's documented business need. What corroborating material is most decisive?
- Privileged sign-in logs, emergency ticket and post-use audit trail
- Repository audit logs, branch access, device posture and project approval
- Endpoint device-control logs, file read audit and approved exception records
- Database audit, approved job duties, export destinations and HR-approved case context
Explanation
Correct Answer
D:Insider investigation must be evidence based and protect privacy. Linking these records back to high-volume sensitive reads may breach the user's documented business need reduces reliance on an isolated indicator.
Incorrect Answers
A:The emergency purpose and actual actions determine whether access was justified; this evidence or action is associated with misuse of break-glass account, whereas the case concerns insider database extraction and calls for database audit, approved job duties, export destinations and HR-approved case context.
B:For suspicious source-code export, cloning can be legitimate; context distinguishes policy violations; here the narrower objective is independently corroborating the suspected behavior in insider database extraction, best addressed by database audit, approved job duties, export destinations and HR-approved case context.
C:Correlating transfer and purpose avoids treating every USB insertion as theft; that is suited to investigating unauthorized removable media, whereas the insider database extraction case requires database audit, approved job duties, export destinations and HR-approved case context for independently corroborating the suspected behavior.
Question 72
The SOC has completed this action: Correlate sudo execution against the least-privilege access baseline. Which result provides the strongest assurance that the specific problem was addressed?
- Approved sudo commands and unapproved deviations are separately visible
- A known test event is retrieved with matching process and timestamp
- Pre-reboot test events remain accessible after restart or at the collector
- A test write yields traceable identity, path and operation in the central store
- A controlled rejected SSH login appears centrally with the originating address
Explanation
Correct Answer
A:Tests should demonstrate meaningful audit fields rather than raw message ingestion. It documents the result of this response step—Correlate sudo execution against the least-privilege access baseline—and helps determine whether the protective state persists.
Incorrect Answers
B:Successful forwarding requires interpretable content, not only a collector heartbeat; applied to this Linux sudo activity case, it addresses macOS unified logging instead of the required step: approved sudo commands and unapproved deviations are separately visible.
C:This relates to systemd journal persistence: testing only new events after boot would miss the historical-loss defect; the Linux sudo activity question instead requires demonstrating that the remediation or control took effect, specifically approved sudo commands and unapproved deviations are separately visible.
D:A record of file existence is not equivalent to a modification audit; prioritizing that Linux auditd file access mechanism would leave this Linux sudo activity decision unresolved because approved sudo commands and unapproved deviations are separately visible is the direct fit.
E:For Linux SSH failures, validating source IP and timestamp prevents misleading aggregation; here the narrower objective is demonstrating that the remediation or control took effect in Linux sudo activity, best addressed by approved sudo commands and unapproved deviations are separately visible.
Question 73
A single endpoint makes small outbound connections every few minutes to a rare external host. Supporting evidence includes: Proxy flows, connection timestamps and owning endpoint process. Which next step most directly reduces the described risk?
- Alert on novel prohibited egress and confirm business allowlist before blocking
- Correlate periodic network activity with uncommon binary and domain context
- Detect anomalous NXDOMAIN bursts with client-specific baselines
- Investigate destination identity and update pins only after verifying ownership
Explanation
Correct Answer
B:An exact fixed-interval rule alone is easy to evade and may catch software updates. The response must subsequently be checked by confirming suspicious simulated callbacks alert while approved telemetry agents are excluded narrowly; otherwise the original exposure may persist.
Incorrect Answers
A:A blanket internet block could interrupt documented external dependencies; applied to this low-and-slow beacon case, it addresses unexpected outbound port instead of the required step: correlate periodic network activity with uncommon binary and domain context.
C:This relates to DNS algorithmic names: a blocklist of already known malicious domains misses newly generated names; the low-and-slow beacon question instead requires choosing the immediate operational response, specifically correlate periodic network activity with uncommon binary and domain context.
D:The alternative concerns TLS certificate anomaly: blindly trusting a new certificate defeats the intended authenticity check; however, the described low-and-slow beacon situation calls for correlate periodic network activity with uncommon binary and domain context.
Question 74
Responders suspect multi-cloud log residency based on this observation: Raw logs must obey geographic and contractual retention boundaries. Which artifact should be examined first?
- Principal grants, database audit events and provider service boundary documentation
- Entra role activation logs, approval context and sign-in details
- GuardDuty finding details plus VPC and workload activity context
- Google SecOps ingestion mappings, normalized fields and detection result context
- Per-cloud log destinations, data classifications and cross-border access controls
- CloudTrail eventName, userIdentity, sourceIPAddress and requestParameters
Explanation
Correct Answer
E:Collection architecture must reflect which data may leave each region. Linking these records back to raw logs must obey geographic and contractual retention boundaries reduces reliance on an isolated indicator.
Incorrect Answers
A:The root cause depends on customer-controlled authorization, not physical hosting; prioritizing that cloud shared responsibility mechanism would leave this multi-cloud log residency decision unresolved because per-cloud log destinations, data classifications and cross-border access controls is the direct fit.
B:This relates to Azure privileged identity: role assignment and activation are different from ordinary resource API calls; the multi-cloud log residency question instead requires independently corroborating the suspected behavior, specifically per-cloud log destinations, data classifications and cross-border access controls.
C:The alternative concerns GuardDuty compromise finding: an enriched finding must still be validated against actual affected assets; however, the described multi-cloud log residency situation calls for per-cloud log destinations, data classifications and cross-border access controls.
D:For Google SecOps investigation, consistent identities and timestamps are essential across feeds; here the narrower objective is independently corroborating the suspected behavior in multi-cloud log residency, best addressed by per-cloud log destinations, data classifications and cross-border access controls.
F:These fields identify which actor requested the privilege change; applied to this multi-cloud log residency case, it addresses CloudTrail administrative audit instead of the required step: per-cloud log destinations, data classifications and cross-border access controls.
Question 75
Analysts confirm the following observation: A state-changing request carries an existing session without verified user intent. Supporting material includes: CSRF token checks, Origin/Referer data and session-bound request traces. Which operational action addresses the issue most directly?
- Escalate under insider-threat procedures and preserve access evidence
- Enforce anti-CSRF tokens and suitable cookie SameSite settings
- Quarantine the campaign, invalidate exposed sessions and warn affected users
- Sanitize output contextually and remove the malicious stored content
Explanation
Correct Answer
B:Request origin defenses must protect state-changing operations while respecting normal workflows. For safe case progression, preserve the evidence and later verify untrusted-origin submissions fail while legitimate authenticated changes still succeed.
Incorrect Answers
A:Controlled review protects privacy and avoids an unsupported accusation from volume alone; prioritizing that insider bulk export mechanism would leave this cross-site request forgery decision unresolved because enforce anti-CSRF tokens and suitable cookie SameSite settings is the direct fit.
C:Removing mail limits further clicks but does not revoke already compromised tokens, which would be relevant to phishing attachment, but not the cross-site request forgery scenario that requires enforce anti-CSRF tokens and suitable cookie SameSite settings.
D:Safe output encoding is primary; deleting one comment alone does not fix future inputs; this evidence or action is associated with stored cross-site scripting, whereas the case concerns cross-site request forgery and calls for enforce anti-CSRF tokens and suitable cookie SameSite settings.
Question 76
An alert suggests dormant-account access. The recorded clue is: A long-inactive account initiates a privileged successful session. What evidence would best test this hypothesis?
- Account last-use history, current access rights and session event data
- Authentication event time, username normalization and five-minute grouping
- MFA challenge history, device binding and subsequent sign-in activity
- Session device IDs, IP ownership, VPN egress and MFA context
Explanation
Correct Answer
A:Risk assessment requires both dormancy and the actual privileged action. This is particularly useful after the initial sign of a long-inactive account initiates a privileged successful session; the two forms of evidence test different parts of the case.
Incorrect Answers
B:Correct grouping keys and event-time windows are required to count attempts accurately; prioritizing that authentication failure window mechanism would leave this dormant-account access decision unresolved because account last-use history, current access rights and session event data is the direct fit.
C:The sequence is more revealing than a single accepted push notification; that is suited to investigating MFA fatigue attempts, whereas the dormant-account access case requires account last-use history, current access rights and session event data for independently corroborating the suspected behavior.
D:Device and network metadata help separate account takeover from egress relocation; applied to this dormant-account access case, it addresses impossible travel triage instead of the required step: account last-use history, current access rights and session event data.
Question 77
An alert suggests privileged SaaS sign-in. The recorded clue is: Privileged session satisfies password authentication but lacks required posture. What evidence would best test this hypothesis?
- Cloud audit principal, API operation, old and new rule values
- Account inventory compared with trail, connector and ingestion status
- Sign-in logs with authentication method, device state and policy result
- Object access events, service principal permissions and egress indicators
Explanation
Correct Answer
C:These fields distinguish blocked attempts from actual risky access. The result can be compared with privileged session satisfies password authentication but lacks required posture to verify that the suspected mechanism is actually present.
Incorrect Answers
A:The alternative concerns cloud control-plane edit: control-plane context identifies who changed the rule and with what effect; however, the described privileged SaaS sign-in situation calls for sign-in logs with authentication method, device state and policy result.
B:For cloud logging gap, asset discovery must be compared to actual event coverage; here the narrower objective is independently corroborating the suspected behavior in privileged SaaS sign-in, best addressed by sign-in logs with authentication method, device state and policy result.
D:A principal's login does not demonstrate which data was retrieved; this evidence or action is associated with cloud data download, whereas the case concerns privileged SaaS sign-in and calls for sign-in logs with authentication method, device state and policy result.
Question 78
The first-line team is investigating broken access control. Its preliminary finding is: A low-privilege identity successfully accesses a forbidden object. What corroborating material is most decisive?
- HTTP parameter and database query or error correlation
- API gateway token ID, client IP, scope and request traces
- CSP report source files, document URL and stored user content
- Application exception traces, request IDs and endpoint process telemetry
- API access logs joined to role entitlements and object ownership
Explanation
Correct Answer
E:Effective access expectations are necessary to identify an IDOR condition. This is particularly useful after the initial sign of a low-privilege identity successfully accesses a forbidden object; the two forms of evidence test different parts of the case.
Incorrect Answers
A:This relates to SQL injection detection: backend effects distinguish blocked probes from exploitable injection; the broken access control question instead requires independently corroborating the suspected behavior, specifically API access logs joined to role entitlements and object ownership.
B:The token's privileges and actual use define exposure; that is suited to investigating API token misuse, whereas the broken access control case requires API access logs joined to role entitlements and object ownership for independently corroborating the suspected behavior.
C:A report needs application context before declaring persistent XSS; applied to this broken access control case, it addresses cross-site scripting telemetry instead of the required step: API access logs joined to role entitlements and object ownership.
D:Error patterns and payload correlation distinguish instability from an exploit chain; this evidence or action is associated with application crash exploitation, whereas the case concerns broken access control and calls for API access logs joined to role entitlements and object ownership.
Question 79
Responders suspect SOC SLA breach based on this observation: Acknowledgment compliance hides a missed containment service objective. Which artifact should be examined first?
- Audit event coverage, change tickets and immutable retention settings
- Ticket timestamps for detection, acknowledgment, escalation and enforcement
- Source events with identity, origin and failure reason fields
- Incident severity trends, containment intervals and control-gap records
Explanation
Correct Answer
B:The timeline must separate workflow touches from effective mitigation. Linking these records back to acknowledgment compliance hides a missed containment service objective reduces reliance on an isolated indicator.
Incorrect Answers
A:Demonstrating control performance requires preserved events and authorized baselines, which would be relevant to compliance use case, but not the SOC SLA breach scenario that requires ticket timestamps for detection, acknowledgment, escalation and enforcement.
C:Those attributes support root-cause and targeted triage; prioritizing that SOC dashboard drilldown mechanism would leave this SOC SLA breach decision unresolved because ticket timestamps for detection, acknowledgment, escalation and enforcement is the direct fit.
D:Outcome measures connect operational activity to risk management; that is suited to investigating executive SOC report, whereas the SOC SLA breach case requires ticket timestamps for detection, acknowledgment, escalation and enforcement for independently corroborating the suspected behavior.
Question 80
To verify remediation of tier-one escalation, the team reports taking this action: Open a priority incident and notify the on-call incident commander. Which outcome should the analyst demand?
- An acknowledged handoff with a named owner and response deadline
- Production precision and volume stay within agreed operating thresholds
- Disposition labels backed by recorded evidence and follow-up ownership
- One active incident record with clear owners for each dependent action
Explanation
Correct Answer
A:A ticket alone is not proof that the receiving team accepted time-sensitive responsibility. That verification specifically tests whether the intervention to open a priority incident and notify the on-call incident commander corrected the issue rather than merely hiding an alert.
Incorrect Answers
B:Successful deployment requires evidence of usable alerts, not just an enabled rule, which would be relevant to rule-change governance, but not the tier-one escalation scenario that requires an acknowledged handoff with a named owner and response deadline.
C:A closed alert without its reasoning and escalation record cannot be reliably reviewed; prioritizing that triage versus investigation mechanism would leave this tier-one escalation decision unresolved because an acknowledged handoff with a named owner and response deadline is the direct fit.
D:This relates to incident ownership: closure requires checking task responsibility, not simply reducing duplicate ticket counts; the tier-one escalation question instead requires demonstrating that the remediation or control took effect, specifically an acknowledged handoff with a named owner and response deadline.