Question 450
Audit teams need evidence that unauthorized privileged configuration changes are recorded. Which additional finding would most directly support the suspected security interpretation?
- Acknowledgment compliance hides a missed containment service objective
- Technical alert counts alone do not communicate risk and response outcomes
- Known token identity appears from an unapproved client origin and action set
- A control requires traceable privileged changes and accountable identities
- A collection-scope increase explains part of the apparent incident increase
Explanation
Correct Answer
D:Compliance detection should map to a specific control objective and evidence. Investigators should still corroborate it with audit event coverage, change tickets and immutable retention settings before assigning definitive scope or attribution.
Incorrect Answers
A:Different SLA stages measure different responsibilities and risk exposures; applied to this compliance use case case, it addresses SOC SLA breach instead of the required step: a control requires traceable privileged changes and accountable identities.
B:Leadership needs trends, incident impact, coverage gaps and action ownership; prioritizing that executive SOC report mechanism would leave this compliance use case decision unresolved because a control requires traceable privileged changes and accountable identities is the direct fit.
C:Bearer token misuse may bypass password-alert patterns; applied to this compliance use case case, it addresses API token misuse instead of the required step: a control requires traceable privileged changes and accountable identities.
E:This relates to incident trend analysis: changes in sensor coverage can affect counts without changing attack frequency; the compliance use case question instead requires recognizing the distinguishing signal, specifically a control requires traceable privileged changes and accountable identities.
Question 451
Analysts confirm the following observation: New third-party consent grants unusually broad delegated permissions. Supporting material includes: Identity audit of application consent, publisher and granted scopes. Which operational action addresses the issue most directly?
- Automate audit onboarding and open coverage gaps as operational incidents
- Correlate risky configuration updates with approvals and restore safe rules
- Detect unusual bulk reads and narrow or revoke the exposed principal rights
- Alert on risky app consent and revoke malicious grants and tokens
Explanation
Correct Answer
D:A password reset may not remove an application's delegated access. Operational success is not assumed until unapproved grant is removed and app API calls stop while approved apps work, the relevant outcome for this response.
Incorrect Answers
A:Manual dashboards do not provide consistent future account visibility; applied to this oAuth consent anomaly case, it addresses cloud logging gap instead of the required step: alert on risky app consent and revoke malicious grants and tokens.
B:Traffic monitoring alone detects usage, not the policy change that enabled it, which would be relevant to cloud control-plane edit, but not the oAuth consent anomaly scenario that requires alert on risky app consent and revoke malicious grants and tokens.
C:This relates to cloud data download: applying web firewall rules does not stop internal API access with valid credentials; the oAuth consent anomaly question instead requires choosing the immediate operational response, specifically alert on risky app consent and revoke malicious grants and tokens.
Question 452
A developer runs a downloaded installer that spawns a backdoor while appearing to succeed. Select the most discriminating sign for the SOC assessment.
- Installer ancestry leads to unauthorized persistence and outbound control traffic
- Extension permissions and background requests exceed approved browsing behavior
- Self-propagating executions occur over accessible hosts and shares
- Browser process spawns a payload after visiting a compromised page
Explanation
Correct Answer
A:Signed or seemingly functional software can carry an additional malicious payload. The follow-up evidence is EDR process tree, installer provenance, autoruns and network connections, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
B:This relates to malicious browser extension: extensions can access page content and create network traffic independent of user clicks; the trojanized installer question instead requires recognizing the distinguishing signal, specifically installer ancestry leads to unauthorized persistence and outbound control traffic.
C:A worm moves via a repeatable exploitation or authentication path; prioritizing that worm propagation mechanism would leave this trojanized installer decision unresolved because installer ancestry leads to unauthorized persistence and outbound control traffic is the direct fit.
D:For drive-by download, a drive-by chain can occur with little explicit user interaction; here the narrower objective is recognizing the distinguishing signal in trojanized installer, best addressed by installer ancestry leads to unauthorized persistence and outbound control traffic.
Question 453
A SOC analyst is investigating Windows account created and records this observation: Security event 4720 records user-account creation where audited. Which source or comparison would most directly corroborate it?
- Account management audit entries and identity-directory change details
- Domain-controller lockout records joined to service authentication failures
- Group-change audit events showing actor, member and group identifiers
- Service registration event and SCM service image path plus EDR process data
Explanation
Correct Answer
A:Joining creator, target account and later logons shows how the new identity was used. The result can be compared with security event 4720 records user-account creation where audited to verify that the suspected mechanism is actually present.
Incorrect Answers
B:The account and caller-host trail separates misconfigured service retries from an attack; applied to this Windows account created case, it addresses Windows account lockouts instead of the required step: account management audit entries and identity-directory change details.
C:This relates to Windows group membership: effective privilege depends on which security group was modified; the Windows account created question instead requires independently corroborating the suspected behavior, specifically account management audit entries and identity-directory change details.
D:The binary path and creating identity matter more than the service name alone; that is suited to investigating Windows service installation, whereas the Windows account created case requires account management audit entries and identity-directory change details for independently corroborating the suspected behavior.
Question 454
An alert suggests executive SOC report. The recorded clue is: Technical alert counts alone do not communicate risk and response outcomes. What evidence would best test this hypothesis?
- Audit event coverage, change tickets and immutable retention settings
- Incident severity trends, containment intervals and control-gap records
- Ticket timestamps for detection, acknowledgment, escalation and enforcement
- Sensor onboarding dates, comparable asset population and severity trends
Explanation
Correct Answer
B:Outcome measures connect operational activity to risk management. This is particularly useful after the initial sign of technical alert counts alone do not communicate risk and response outcomes; the two forms of evidence test different parts of the case.
Incorrect Answers
A:Demonstrating control performance requires preserved events and authorized baselines; that is suited to investigating compliance use case, whereas the executive SOC report case requires incident severity trends, containment intervals and control-gap records for independently corroborating the suspected behavior.
C:The alternative concerns SOC SLA breach: the timeline must separate workflow touches from effective mitigation; however, the described executive SOC report situation calls for incident severity trends, containment intervals and control-gap records.
D:Normalizing by coverage makes before-and-after comparisons fairer; applied to this executive SOC report case, it addresses incident trend analysis instead of the required step: incident severity trends, containment intervals and control-gap records.
Question 455
The team has responded to distributed denial of service using this measure: Engage upstream DDoS mitigation and activate rate or challenge controls. Which post-action evidence would justify declaring the measure effective?
- Host network activity and resolver records show no continued encoded lookups
- The sweep stops and the source is confirmed unauthorized or approved
- Legitimate user success rates and backend capacity return to baseline
- Unapproved connection attempts cease and network telemetry confirms containment
Explanation
Correct Answer
C:Traffic reduction is insufficient if real users still cannot complete transactions. The measure should be evaluated against the actual action, engage upstream DDoS mitigation and activate rate or challenge controls, rather than against ticket status.
Incorrect Answers
A:This relates to DNS tunneling: confirm both endpoint remediation and disappearance of the suspicious DNS traffic; the distributed denial of service question instead requires demonstrating that the remediation or control took effect, specifically legitimate user success rates and backend capacity return to baseline.
B:For horizontal port scan, a drop in alerts without source attribution could hide continuing reconnaissance; here the narrower objective is demonstrating that the remediation or control took effect in distributed denial of service, best addressed by legitimate user success rates and backend capacity return to baseline.
D:A dashboard alert count alone cannot validate that all probes stopped, which would be relevant to vertical port scan, but not the distributed denial of service scenario that requires legitimate user success rates and backend capacity return to baseline.
Question 456
The first-line team is investigating TAXII feed transport. Its preliminary finding is: A recurring exchange needs an API transport rather than manual document copies. What corroborating material is most decisive?
- TIP indicator history, source mappings, expiration and enrichment records
- TAXII collection metadata, authentication and poll cursor behavior
- Shared objects' types, relationships and version identifiers
- Malware sample bytes, encoded strings and rule condition test corpus
- Report markings, intended audience and partner distribution agreement
Explanation
Correct Answer
B:Collection scope and checkpoints ensure reliable controlled ingestion. The result can be compared with a recurring exchange needs an API transport rather than manual document copies to verify that the suspected mechanism is actually present.
Incorrect Answers
A:A coherent indicator lifecycle supports reliable downstream decisions; prioritizing that threat intelligence platform mechanism would leave this TAXII feed transport decision unresolved because TAXII collection metadata, authentication and poll cursor behavior is the direct fit.
C:For STIX structured sharing, schema consistency is necessary for downstream systems to interpret evidence; here the narrower objective is independently corroborating the suspected behavior in TAXII feed transport, best addressed by TAXII collection metadata, authentication and poll cursor behavior.
D:For YARA file matching, benign and malicious corpora help estimate signature precision; here the narrower objective is independently corroborating the suspected behavior in TAXII feed transport, best addressed by TAXII collection metadata, authentication and poll cursor behavior.
E:This relates to TLP handling: release decisions must reflect both markings and contractual restrictions; the TAXII feed transport question instead requires independently corroborating the suspected behavior, specifically TAXII collection metadata, authentication and poll cursor behavior.
Question 457
An alert has high attack-confidence but affects only a disposable test endpoint. Select the most discriminating sign for the SOC assessment.
- Detection confidence and business impact are different assessment dimensions
- Telemetry or analytic logic failed to cover known simulated behavior
- Missing asset and ownership context prevents severity assessment
- Multiple alerts share the same actor, destination, time and causal activity
Explanation
Correct Answer
A:A likely malicious event is not automatically the most damaging case. The follow-up evidence is evidence strength, asset criticality and attack scope fields, which helps separate the observed pattern from merely similar activity.
Incorrect Answers
B:The alternative concerns false negative detection: a clean dashboard after an attack test indicates a detection-control gap; however, the described severity versus confidence situation calls for detection confidence and business impact are different assessment dimensions.
C:Impact depends on the protected system and its business role; this evidence or action is associated with entity enrichment, whereas the case concerns severity versus confidence and calls for detection confidence and business impact are different assessment dimensions.
D:Duplicate notifications can inflate workload without reflecting separate incidents; that is suited to investigating alert deduplication, whereas the severity versus confidence case requires detection confidence and business impact are different assessment dimensions for recognizing the distinguishing signal.
Question 458
Two successful logins appear minutes apart in distant countries for the same cloud identity. Which observation most directly identifies the concern that needs investigation?
- Geographic separation is inconsistent with plausible physical movement
- Distinct attacked users grow rapidly while per-user failures stay low
- A long-inactive account initiates a privileged successful session
- High-frequency push denials immediately precede an accepted prompt
Explanation
Correct Answer
A:IP geolocation is a risk signal but can be distorted by VPNs and proxies. Confirmation should then examine session device IDs, IP ownership, VPN egress and MFA context; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
B:For password-spray rule, a spray is characterized by breadth across accounts, not one account's failure count; here the narrower objective is recognizing the distinguishing signal in impossible travel triage, best addressed by geographic separation is inconsistent with plausible physical movement.
C:Inactivity history changes the baseline risk of otherwise normal logons; prioritizing that dormant-account access mechanism would leave this impossible travel triage decision unresolved because geographic separation is inconsistent with plausible physical movement is the direct fit.
D:This relates to MFA fatigue attempts: repeated approval requests may indicate a prompt-bombing attempt or user coercion; the impossible travel triage question instead requires recognizing the distinguishing signal, specifically geographic separation is inconsistent with plausible physical movement.
Question 459
A SOC analyst is investigating persistence via scheduled task and records this observation: New scheduled task registration referencing suspicious startup command. Which source or comparison would most directly corroborate it?
- EDR process-access telemetry, memory access rights and parent ancestry
- Domain-controller ticket requests and the requesting host's process history
- Task Scheduler Operational events and task XML with creation identity
- Authentication failures grouped by source, user cardinality and time
Explanation
Correct Answer
C:The executable path, trigger and account expose the persistence mechanism. Linking these records back to new scheduled task registration referencing suspicious startup command reduces reliance on an isolated indicator.
Incorrect Answers
A:For credential dumping, the process relationship and security context distinguish abuse from authorized diagnostics; here the narrower objective is independently corroborating the suspected behavior in persistence via scheduled task, best addressed by task Scheduler Operational events and task XML with creation identity.
B:Correlating 4769 events with endpoint execution improves context and attribution; this evidence or action is associated with kerberoasting, whereas the case concerns persistence via scheduled task and calls for task Scheduler Operational events and task XML with creation identity.
D:Username diversity and timing separate spraying from a single forgotten password; that is suited to investigating password spraying, whereas the persistence via scheduled task case requires task Scheduler Operational events and task XML with creation identity for independently corroborating the suspected behavior.
Question 460
Analysts confirm the following observation: An unauthorized web-accessible file executes operating-system commands. Supporting material includes: Web server file metadata, process ancestry, access logs and upload path. Which operational action addresses the issue most directly?
- Disable the vulnerable route or restrict access while fixing server-side authorization
- Apply adaptive throttling and strengthen account abuse detections
- Remove malicious content and fix context-specific output encoding
- Restrict the server, preserve shell artifacts and remove the upload or execution flaw
Explanation
Correct Answer
D:Deleting the web shell without fixing upload controls risks recurrence. Operational success is not assumed until no unapproved executable files remain and upload controls reject the exploit pattern, the relevant outcome for this response.
Incorrect Answers
A:A login reset does not correct missing object-level checks; applied to this web shell discovery case, it addresses broken object authorization instead of the required step: restrict the server, preserve shell artifacts and remove the upload or execution flaw.
B:The alternative concerns API rate-limit incident: blocking all users would create self-inflicted availability loss; however, the described web shell discovery situation calls for restrict the server, preserve shell artifacts and remove the upload or execution flaw.
C:Blocking the poster's IP alone leaves malicious content stored; prioritizing that stored XSS incident mechanism would leave this web shell discovery decision unresolved because restrict the server, preserve shell artifacts and remove the upload or execution flaw is the direct fit.