Question 480
The SOC has completed this action: Alert on novel prohibited egress and confirm business allowlist before blocking. Which result provides the strongest assurance that the specific problem was addressed?
- Approved certificate rotation works and a simulated interceptor remains blocked
- Authorized integrations remain usable while the tested unauthorized path is denied
- Benign typo traffic stays below threshold and test DGA sequences are flagged
- Legitimate request success recovers and abusive rate tests are throttled
- Suspicious simulated callbacks alert while approved telemetry agents are excluded narrowly
Explanation
Correct Answer
B:Verification needs both security and application health evidence. It documents the result of this response step—Alert on novel prohibited egress and confirm business allowlist before blocking—and helps determine whether the protective state persists.
Incorrect Answers
A:Testing only successful TLS establishment ignores trust requirements; that is suited to investigating TLS certificate anomaly, whereas the unexpected outbound port case requires authorized integrations remain usable while the tested unauthorized path is denied for demonstrating that the remediation or control took effect.
C:A good rule controls false positives from software probes; applied to this unexpected outbound port case, it addresses DNS algorithmic names instead of the required step: authorized integrations remain usable while the tested unauthorized path is denied.
D:Blocking all traffic would not meet availability goals; this evidence or action is associated with HTTP request flood, whereas the case concerns unexpected outbound port and calls for authorized integrations remain usable while the tested unauthorized path is denied.
E:This relates to low-and-slow beacon: the suppression must identify vetted software rather than arbitrary destinations; the unexpected outbound port question instead requires demonstrating that the remediation or control took effect, specifically authorized integrations remain usable while the tested unauthorized path is denied.
Question 481
A global administrator logs in from an unmanaged device with weak authentication assurance. Supporting evidence includes: Sign-in logs with authentication method, device state and policy result. Which next step most directly reduces the described risk?
- Detect unusual bulk reads and narrow or revoke the exposed principal rights
- Automate audit onboarding and open coverage gaps as operational incidents
- Prioritize the successful high-privilege session and enforce access policy
- Correlate risky configuration updates with approvals and restore safe rules
- Summarize material incidents, response performance and recommended decisions
- Alert on risky app consent and revoke malicious grants and tokens
Explanation
Correct Answer
C:A low-severity failure count rule misses a potentially valid compromised session. The response must subsequently be checked by confirming the same unmanaged access is denied and compliant admin logins still succeed; otherwise the original exposure may persist.
Incorrect Answers
A:This relates to cloud data download: applying web firewall rules does not stop internal API access with valid credentials; the privileged SaaS sign-in question instead requires choosing the immediate operational response, specifically prioritize the successful high-privilege session and enforce access policy.
B:Manual dashboards do not provide consistent future account visibility; applied to this privileged SaaS sign-in case, it addresses cloud logging gap instead of the required step: prioritize the successful high-privilege session and enforce access policy.
D:Traffic monitoring alone detects usage, not the policy change that enabled it, which would be relevant to cloud control-plane edit, but not the privileged SaaS sign-in scenario that requires prioritize the successful high-privilege session and enforce access policy.
E:Raw IOC tables are useful to analysts but not enough for executives; applied to this privileged SaaS sign-in case, it addresses executive SOC report instead of the required step: prioritize the successful high-privilege session and enforce access policy.
F:For oAuth consent anomaly, a password reset may not remove an application's delegated access; here the narrower objective is choosing the immediate operational response in privileged SaaS sign-in, best addressed by prioritize the successful high-privilege session and enforce access policy.
Question 482
To verify remediation of ransomware recovery staging, the team reports taking this action: Restore into isolated validated infrastructure after containment and secret rotation. Which outcome should the analyst demand?
- The data impact assessment is documented independently of restore status
- Restored services pass integrity checks and remain free of attacker access under monitoring
- No new encrypted files are created and share activity remains controlled
- An isolated restore test succeeds and attacker credentials no longer manage backups
Explanation
Correct Answer
B:Boot success alone is not safe recovery. That verification specifically tests whether the intervention to restore into isolated validated infrastructure after containment and secret rotation corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:Recovery completion does not mean exfiltration findings are closed; applied to this ransomware recovery staging case, it addresses double extortion instead of the required step: restored services pass integrity checks and remain free of attacker access under monitoring.
C:Stopping the first process does not rule out other encryptors; prioritizing that ransomware early containment mechanism would leave this ransomware recovery staging decision unresolved because restored services pass integrity checks and remain free of attacker access under monitoring is the direct fit.
D:This relates to compromised backup repository: backup job success alone does not prove restorability; the ransomware recovery staging question instead requires demonstrating that the remediation or control took effect, specifically restored services pass integrity checks and remain free of attacker access under monitoring.
Question 483
To verify remediation of ARP cache poisoning, the team reports taking this action: Quarantine the offending switch port and correct trusted gateway bindings. Which outcome should the analyst demand?
- Legitimate user success rates and backend capacity return to baseline
- Clients resolve the real gateway MAC and no further spoofed ARP appears
- The sweep stops and the source is confirmed unauthorized or approved
- Test payloads no longer alter query behavior and logs show no successful exploitation
Explanation
Correct Answer
B:A successful web refresh without ARP validation does not prove that interception ended. It documents the result of this response step—Quarantine the offending switch port and correct trusted gateway bindings—and helps determine whether the protective state persists.
Incorrect Answers
A:Traffic reduction is insufficient if real users still cannot complete transactions; that is suited to investigating distributed denial of service, whereas the ARP cache poisoning case requires clients resolve the real gateway MAC and no further spoofed ARP appears for demonstrating that the remediation or control took effect.
C:A drop in alerts without source attribution could hide continuing reconnaissance; prioritizing that horizontal port scan mechanism would leave this ARP cache poisoning decision unresolved because clients resolve the real gateway MAC and no further spoofed ARP appears is the direct fit.
D:Simply suppressing database error messages could hide an unfixed injection flaw; applied to this ARP cache poisoning case, it addresses SQL injection instead of the required step: clients resolve the real gateway MAC and no further spoofed ARP appears.
Question 484
The team has responded to Microsoft Sentinel analytic using this measure: Create and test a Sentinel analytic rule with entity mapping and incident settings. Which post-action evidence would justify declaring the measure effective?
- A test resource change appears centrally with the correct actor and scope
- A known suspicious sign-in produces an incident with correct user and IP entities
- Unapproved activation attempts are denied or reviewed while approved activation remains functional
- A controlled misconfiguration yields a traceable finding with resource ownership
Explanation
Correct Answer
B:Testing ingestion alone does not validate incident generation. The measure should be evaluated against the actual action, create and test a Sentinel analytic rule with entity mapping and incident settings, rather than against ticket status.
Incorrect Answers
A:A working VM agent is not enough to establish Azure audit coverage; applied to this Microsoft Sentinel analytic case, it addresses Azure activity log visibility instead of the required step: a known suspicious sign-in produces an incident with correct user and IP entities.
C:The alternative concerns Azure privileged identity: validate actual policy enforcement on the privileged role; however, the described Microsoft Sentinel analytic situation calls for a known suspicious sign-in produces an incident with correct user and IP entities.
D:Finding visibility should be tested at intended organization scope, which would be relevant to GCP Security Command Center, but not the Microsoft Sentinel analytic scenario that requires a known suspicious sign-in produces an incident with correct user and IP entities.
Question 485
A production security group is opened to all sources by an unfamiliar automation principal. Select the most discriminating sign for the SOC assessment.
- Account enrollment is missing an audit connector or organization trail scope
- Abnormal object-read volume and unfamiliar client identity suggest extraction
- Privileged session satisfies password authentication but lacks required posture
- Unexpected allow-all rule modification expands exposed network access
Explanation
Correct Answer
D:Cloud audit events capture configuration changes that ordinary flow logs cannot. Confirmation should then examine cloud audit principal, API operation, old and new rule values; the signal is a triage lead, not a complete incident narrative.
Incorrect Answers
A:Cloud growth can create blind spots unless sources are onboarded automatically; this evidence or action is associated with cloud logging gap, whereas the case concerns cloud control-plane edit and calls for unexpected allow-all rule modification expands exposed network access.
B:Object access telemetry reveals data-plane movement missed by sign-in logs; that is suited to investigating cloud data download, whereas the cloud control-plane edit case requires unexpected allow-all rule modification expands exposed network access for recognizing the distinguishing signal.
C:The alternative concerns privileged SaaS sign-in: the risk is conditional-access noncompliance, not simple geolocation; however, the described cloud control-plane edit situation calls for unexpected allow-all rule modification expands exposed network access.
Question 486
An attacker has obtained a cloud user's active refresh token. The user has already changed their password, but API calls continue. Which TWO response steps are most appropriate? Choose TWO.
- Assume the password change automatically invalidated every token in every application
- Clear local browser history and then close the investigation
- Block one unrelated IP address without reviewing the active token's permissions
- Revoke affected sessions or token grants using the identity provider's controls
- Review API audit events to scope resource access by the suspect token
Explanation
Correct Answers
D:A previously issued token may remain usable after a secret change. Explicit session invalidation closes that bearer access path.
E:The continued requests reveal which data and operations might have been exposed. Scope and impact cannot be inferred from password state alone.
Incorrect Answers
A:Token lifetimes and revocation behavior vary, so this assumption is unsafe. Observed continued access already disproves it in the case.
B:Browser history deletion does not revoke tokens held by an attacker. It also may remove useful investigative information.
C:An attacker may reuse a token from multiple origins. Privilege and session controls address the exposed credential directly.
Question 487
A developer account unexpectedly runs a privileged shell through sudo on a production host. Which finding best distinguishes this activity from a routine operational change?
- Unified Logging predicates identify process and event records on macOS
- Security event 4697 may record service installation when audited
- sudo authorization and command records reveal privilege elevation
- An ephemeral journal configuration loses records across restarts
Explanation
Correct Answer
C:Privilege use can be permitted but becomes suspicious when context differs from approval. Investigators should still corroborate it with sudo and PAM logs linked to the user's session and executed command before assigning definitive scope or attribution.
Incorrect Answers
A:This relates to macOS unified logging: the platform uses its own structured logging mechanism and privacy controls; the Linux sudo activity question instead requires recognizing the distinguishing signal, specifically sudo authorization and command records reveal privilege elevation.
B:Service creation can establish persistence or remote execution depending on context; that is suited to investigating Windows service installation, whereas the Linux sudo activity case requires sudo authorization and command records reveal privilege elevation for recognizing the distinguishing signal.
D:Volatile journal storage can be unsuitable when historical host events are required; prioritizing that systemd journal persistence mechanism would leave this Linux sudo activity decision unresolved because sudo authorization and command records reveal privilege elevation is the direct fit.
Question 488
A SOC analyst is investigating hybrid SOC coordination and records this observation: Alerts span infrastructure telemetry and enterprise identity activity. Which source or comparison would most directly corroborate it?
- The current case timeline, pending actions, and shift-transfer acknowledgement
- Contracted runbooks, RACI matrix, and delegated access inventory
- A shared escalation matrix mapping cloud and application control planes
- Identity-provider sign-in details joined to endpoint activity
Explanation
Correct Answer
C:Clear boundaries determine which telemetry and remediation rights belong to each party. Linking these records back to alerts span infrastructure telemetry and enterprise identity activity reduces reliance on an isolated indicator.
Incorrect Answers
A:A complete handover includes hypotheses, collected evidence, decisions and deadlines; prioritizing that follow-the-sun transfer mechanism would leave this hybrid SOC coordination decision unresolved because a shared escalation matrix mapping cloud and application control planes is the direct fit.
B:The operating agreement defines which decisions and tools the supplier can actually use, which would be relevant to managed SOC boundary, but not the hybrid SOC coordination scenario that requires a shared escalation matrix mapping cloud and application control planes.
D:Correlating user, device, and subsequent behavior is stronger than treating failure counts alone as an incident; this evidence or action is associated with triage versus investigation, whereas the case concerns hybrid SOC coordination and calls for a shared escalation matrix mapping cloud and application control planes.
Question 489
An attacker with temporary admin access adds an unfamiliar local or domain user. Supporting evidence includes: Account management audit entries and identity-directory change details. Which next step most directly reduces the described risk?
- Alert on unexpected account creation and review role assignments
- Restore the approved audit baseline and investigate who altered it
- Find the repeatedly failing service or malicious origin before unlocking
- Correlate privileged group additions with approvals and subsequent activity
Explanation
Correct Answer
A:The follow-up must consider whether the account gained privileges or persisted. Operational success is not assumed until an approved provisioning test is logged and unauthorized new accounts are investigated, the relevant outcome for this response.
Incorrect Answers
B:Re-enabling logging alone does not establish why security visibility was disabled, which would be relevant to Windows policy change, but not the Windows account created scenario that requires alert on unexpected account creation and review role assignments.
C:For Windows account lockouts, blind account unlocks without repairing the cause may trigger immediate relock; here the narrower objective is choosing the immediate operational response in Windows account created, best addressed by alert on unexpected account creation and review role assignments.
D:Unexpected memberships should trigger review before broad privilege spread; this evidence or action is associated with Windows group membership, whereas the case concerns Windows account created and calls for alert on unexpected account creation and review role assignments.
Question 490
Two samples share a hash prefix but exhibit different persistence and network behavior. Select the most discriminating sign for the SOC assessment.
- Embedded strings and import tables can expose capabilities without running code
- Flow metadata cannot show all application-layer request details
- Display sender and visible hyperlink text differ from technical message origins
- Partial hash resemblance does not establish common malware family
Explanation
Correct Answer
D:Cryptographic hashes are exact identifiers; family inference requires features and behavior. Investigators should still corroborate it with code similarity, YARA features, protocol patterns and tooling overlaps before assigning definitive scope or attribution.
Incorrect Answers
A:Static analysis can identify likely functions while obfuscation limits conclusions, which would be relevant to static malware strings, but not the malware family attribution scenario that requires partial hash resemblance does not establish common malware family.
B:For network packet evidence, packet captures may reveal protocol features and transmitted payload when available; here the narrower objective is recognizing the distinguishing signal in malware family attribution, best addressed by partial hash resemblance does not establish common malware family.
C:Header and URL analysis can reveal spoofing and hidden destinations; applied to this malware family attribution case, it addresses email artifact examination instead of the required step: partial hash resemblance does not establish common malware family.