Question 290
A suspected tenant-wide identity compromise leaves investigators unsure whether their normal corporate chat is trustworthy. What record is most useful for confirming this specific pattern?
- Approved incident roles, escalation policy and service ownership
- Linked event timeline and incident severity criteria
- Preapproved external bridge details and responder contact list
- Active retainer agreement, scope and escalation contact verification
Explanation
Correct Answer
C:The Out-of-band crisis communications evidence “A suspected tenant-wide identity compromise leaves investigators unsure whether their normal corporate chat is trustworthy” is decisive for corroboration because a separate trusted channel remains reachable during identity system isolation.
Incorrect Answers
A:That option fits Incident response authority chart since the policy establishes who can authorize high-impact containment; it does not fit the Out-of-band crisis communications corroboration scenario, where a separate trusted channel remains reachable during identity system isolation.
B:This option addresses Incident declaration threshold because the aggregated evidence should be evaluated against defined declaration triggers; the Out-of-band crisis communications corroboration question instead turns on the fact that a separate trusted channel remains reachable during identity system isolation.
D:This option addresses Third-party incident retainer activation because contract terms define assistance level, notification requirements and access limits; the Out-of-band crisis communications corroboration question instead turns on the fact that a separate trusted channel remains reachable during identity system isolation.
Question 291
Three feeds provide the same malware hash with different labels and observation times, inflating the analyst's case list. The finding has been corroborated and the response team has authorization to act. Which response is the most appropriate at this point?
- Build behavior rules alongside hash-based detections
- Merge duplicate observables without discarding source histories
- Expire outdated block rules unless renewed by evidence
- Normalize the shared objects into the intelligence platform
Explanation
Correct Answer
B:The Threat intelligence platform deduplication evidence “Three feeds provide the same malware hash with different labels and observation times, inflating the analyst's case list” is decisive for response decision because preserving attribution supports later re-evaluation and false-positive handling.
Incorrect Answers
A:The choice is relevant to Malware hash IoC specificity, where layered detection catches payload variants without relying on one checksum; for response decision in Threat intelligence platform deduplication, preserving attribution supports later re-evaluation and false-positive handling.
C:The choice is relevant to Threat feed confidence decay, where time-limited enforcement avoids penalizing newly legitimate tenants; for response decision in Threat intelligence platform deduplication, preserving attribution supports later re-evaluation and false-positive handling.
D:For response decision in Threat intelligence platform deduplication, STIX structured intelligence exchange is a different mechanism: structured import preserves entities for enrichment and correlation; here, preserving attribution supports later re-evaluation and false-positive handling.
Question 292
A user reports unexpected password-reset emails while valid sessions originate from a newly observed unmanaged device. What record is most useful for confirming this specific pattern?
- Directory group-change event and initiating account sign-ins
- Helpdesk reset ticket and authenticator registration audit
- IdP audit of device, factors and post-login resource access
- Repository exposure history and cloud credential use audit
Explanation
Correct Answer
C:Authentication and application logs reveal which sessions may be attacker-controlled; this is the relevant corroboration mechanism for Employee account takeover given “A user reports unexpected password-reset emails while valid sessions originate from a newly observed unmanaged device”.
Incorrect Answers
A:For corroboration in Employee account takeover, Privilege escalation via group membership is a different mechanism: actor, target and timestamps identify the delegation path; here, authentication and application logs reveal which sessions may be attacker-controlled.
B:The choice is relevant to Unauthorized MFA factor registration, where the requester, new factor and approval record support the legitimacy check; for corroboration in Employee account takeover, authentication and application logs reveal which sessions may be attacker-controlled.
D:The choice is relevant to Exposed cloud API credential, where source records reveal exposure interval and actual API activity; for corroboration in Employee account takeover, authentication and application logs reveal which sessions may be attacker-controlled.
Question 293
Investigators must discover rare internal-to-external connections while full packet payload capture is unavailable. Which investigative step would most directly establish the relevant scope?
- Test converted queries against each product's event schema
- Join startup path, signer and host prevalence from query output
- Test candidate YARA conditions on clean and malicious samples
- Join rare destination flows with DNS and TLS events
Explanation
Correct Answer
D:Cross-protocol correlation reveals suspicious network behavior beyond port counts; this is the relevant scope analysis mechanism for Threat hunt with Zeek connection logs given “Investigators must discover rare internal-to-external connections while full packet payload capture is unavailable”.
Incorrect Answers
A:For scope analysis in Threat hunt with Zeek connection logs, Sigma analytic rule portability is a different mechanism: portability of syntax does not guarantee equivalent behavior across sources; here, cross-protocol correlation reveals suspicious network behavior beyond port counts.
B:The choice is relevant to OSQuery endpoint state hunt, where the investigation can distinguish unique suspicious entries from approved software; for scope analysis in Threat hunt with Zeek connection logs, cross-protocol correlation reveals suspicious network behavior beyond port counts.
C:For scope analysis in Threat hunt with Zeek connection logs, YARA rule string matching is a different mechanism: false-positive evaluation is essential before broad deployment; here, cross-protocol correlation reveals suspicious network behavior beyond port counts.
Question 294
A feed still marks an IP address malicious one year after the original report. Which TWO limitations should a SOC analyst include when deciding whether to block it today? Choose TWO.
- The address may have changed owner, hosting role or legitimate users since the report.
- An old feed entry always remains valid when the original incident was real.
- A single provider's age and confidence label do not independently verify present-day activity.
- Age proves the address is now safe and should be excluded from every hunt.
- All cloud-provider addresses should be permanently blocked once reported once.
Explanation
Correct Answers
A:An IP is a reassigned infrastructure identifier rather than a stable actor identity. Current service use and independent recent sightings must inform the blocking decision.
C:Confidence is the provider's assessment under its own method. Recent telemetry or separate sources are needed to evaluate whether the old claim remains operationally relevant.
Incorrect Answers
B:A historically accurate report does not imply the indicator is currently malicious. Reassignment, sinkholing and shared hosting can make unqualified enforcement harmful.
D:An old indicator can still be useful to historical investigations. Age weakens unqualified enforcement but does not establish innocence or make retrospective review pointless.
E:Shared infrastructure changes tenants and legitimate workloads. Permanent broad blocks can disrupt unrelated business traffic and must not be inferred from one historical observation.
Question 295
A report claims attacks doubled after new branch-office sensors were added to the SIEM last month. Which engineering change provides the most relevant ongoing visibility?
- Show coverage percentage and stale-source counts by tier
- Track percentile detection delay and long-tail incidents
- Display precision and investigation hours per detection
- Chart tail SLA breaches by severity and shift
- Report alert rates per monitored asset and source class
Explanation
Correct Answer
E:Given “A report claims attacks doubled after new branch-office sensors were added to the SIEM last month”, normalized measures reduce misleading raw-count comparisons; that best addresses ongoing detection improvement in Threat trend comparison without normalization.
Incorrect Answers
A:For ongoing detection improvement in Threat trend comparison without normalization, SOC data-source coverage dashboard is a different mechanism: missing-data indicators make dashboard health meaningful; here, normalized measures reduce misleading raw-count comparisons.
B:The choice is relevant to Incident detection latency dashboard, where tail performance matters because a few missed intrusions can dominate damage; for ongoing detection improvement in Threat trend comparison without normalization, normalized measures reduce misleading raw-count comparisons.
C:For ongoing detection improvement in Threat trend comparison without normalization, Noisy use-case Pareto dashboard is a different mechanism: efficiency reporting should combine workload with detection value; here, normalized measures reduce misleading raw-count comparisons.
D:The choice is relevant to SLA breach trend by incident tier, where breakdowns reveal time-of-day failures hidden by totals; for ongoing detection improvement in Threat trend comparison without normalization, normalized measures reduce misleading raw-count comparisons.
Question 296
A critical host's process audit shows execve activity with unusual effective user IDs but syslog lacks command detail. What follow-up analysis most effectively distinguishes this case?
- Join executable path, auid and effective uid for each event
- Correlate launch agent plist provenance with process events
- Compare sudo calls with the host's approved change record
- Match success to source IP, session and shell history
Explanation
Correct Answer
A:In the Linux auditd execution records case, audit user identity helps trace privilege transitions not visible from process name alone; the observation “A critical host's process audit shows execve activity with unusual effective user IDs but syslog lacks command detail” makes this scope analysis choice the fitting one.
Incorrect Answers
B:For scope analysis in Linux auditd execution records, macOS unified log investigation is a different mechanism: file and execution context can connect a scheduled launch with the observed program; here, audit user identity helps trace privilege transitions not visible from process name alone.
C:The choice is relevant to Linux sudo elevation audit, where a privileged command can be legitimate when it matches a maintenance task; for scope analysis in Linux auditd execution records, audit user identity helps trace privilege transitions not visible from process name alone.
D:For scope analysis in Linux auditd execution records, Linux SSH authentication messages is a different mechanism: the overlap distinguishes a real foothold from unrelated logins; here, audit user identity helps trace privilege transitions not visible from process name alone.
Question 297
A malicious flow is logged from a private address that was reassigned to another device earlier the same day. The finding has been corroborated and the response team has authorization to act. Which response is the most appropriate at this point?
- Triage as an attempt and examine target evidence before escalation
- Validate the change request before altering the firewall rule
- Block validated malicious domains and identify requesting endpoints
- Block confirmed malicious destinations at the proxy
- Preserve lease records and correct incident asset attribution
- Review the session and revoke suspicious VPN access after validation
Explanation
Correct Answer
E:The DHCP lease attribution evidence “A malicious flow is logged from a private address that was reassigned to another device earlier the same day” is decisive for response decision because fixing identity mapping prevents unnecessary containment of an innocent endpoint.
Incorrect Answers
A:The choice is relevant to IDS signature alert context, where investigators should not claim host compromise solely from a perimeter match; for response decision in DHCP lease attribution, fixing identity mapping prevents unnecessary containment of an innocent endpoint.
B:For response decision in DHCP lease attribution, Firewall deny rule evidence is a different mechanism: opening access without review could remove the segment boundary protecting the database; here, fixing identity mapping prevents unnecessary containment of an innocent endpoint.
C:The choice is relevant to Recursive DNS resolver attribution, where sinkholing or policy denial helps only after the infected clients are located; for response decision in DHCP lease attribution, fixing identity mapping prevents unnecessary containment of an innocent endpoint.
D:For response decision in DHCP lease attribution, Web proxy URL telemetry is a different mechanism: the control acts at the layer where URL and user context are available; here, fixing identity mapping prevents unnecessary containment of an innocent endpoint.
F:For response decision in DHCP lease attribution, VPN session authentication audit is a different mechanism: risk-based response focuses on actual access and identity assurance; here, fixing identity mapping prevents unnecessary containment of an innocent endpoint.
Question 298
An application audit shows an ordinary customer granted administrator access shortly after a suspicious support session. What lasting monitoring control should be added after the case?
- Alert on privileged grants outside authorized workflows
- Alert on web-worker processes spawning shells
- Detect allowed high-risk payloads with backend effect
- Alert on export destinations not in the approved allowlist
Explanation
Correct Answer
A:The Unexpected web administrative role assignment evidence “An application audit shows an ordinary customer granted administrator access shortly after a suspicious support session” is decisive for ongoing detection improvement because role-sensitive detections should include actor entitlement and change context.
Incorrect Answers
B:For ongoing detection improvement in Unexpected web administrative role assignment, Web-shell request and process correlation is a different mechanism: parent-child linkage has more value than scanning page names alone; here, role-sensitive detections should include actor entitlement and change context.
C:The choice is relevant to WAF bypass with origin success, where joint edge-origin rules are stronger than WAF signature counts alone; for ongoing detection improvement in Unexpected web administrative role assignment, role-sensitive detections should include actor entitlement and change context.
D:For ongoing detection improvement in Unexpected web administrative role assignment, Massive object-storage upload through web app is a different mechanism: contextual detection is better than flagging every large upload; here, role-sensitive detections should include actor entitlement and change context.
Question 299
A pod that should only read a namespace config map uses its service account to modify workloads in another namespace. Which interpretation best fits the observed evidence?
- Cloud object access-control misconfiguration
- Azure nonhuman identity abuse
- Compromised Google Cloud machine credential
- Kubernetes workload identity overprivilege
Explanation
Correct Answer
D:In the Kubernetes compromised workload token case, a mounted service-account token can be abused when RBAC grants exceed the workload's purpose; the observation “A pod that should only read a namespace config map uses its service account to modify workloads in another namespace” makes this classification choice the fitting one.
Incorrect Answers
A:In Cloud storage anonymous exposure, public read permission can disclose sensitive files without requiring any identity compromise; the reported Kubernetes compromised workload token case calls for a different classification conclusion because a mounted service-account token can be abused when RBAC grants exceed the workload's purpose.
B:For the alternative Azure automation identity misuse situation, application identities can access resources through assigned roles without a user's interactive sign-in; by contrast, for Kubernetes compromised workload token classification, a mounted service-account token can be abused when RBAC grants exceed the workload's purpose.
C:In GCP service account key exposed, long-lived service-account keys can be copied and used without a human login; the reported Kubernetes compromised workload token case calls for a different classification conclusion because a mounted service-account token can be abused when RBAC grants exceed the workload's purpose.
Question 300
A newly created customer account retrieves tens of thousands of profiles through a paginated API overnight. Which caveat most directly affects assessment of the evidence?
- A clean vulnerability scan does not prove the host is no longer compromised
- Filtering obvious SQL keywords alone is an incomplete fix
- An HTTPS connection does not prove a webhook came from its vendor
- Removing the public file alone does not make the old password safe
- Rate limiting alone cannot correct broken object-level authorization
Explanation
Correct Answer
E:The Automated scraping of protected records evidence “A newly created customer account retrieves tens of thousands of profiles through a paginated API overnight” is decisive for interpretation limit because a slow attacker may still access records belonging to other users.
Incorrect Answers
A:That option fits Web-shell persistence after patching since patch status and attacker artifact removal are separate requirements; it does not fit the Automated scraping of protected records interpretation limit scenario, where a slow attacker may still access records belonging to other users.
B:This option addresses Confirmed SQL injection data exposure because input can be encoded or reformulated, while prepared statements preserve query structure; the Automated scraping of protected records interpretation limit question instead turns on the fact that a slow attacker may still access records belonging to other users.
C:That option fits Compromised webhook endpoint since TLS protects the channel but does not inherently validate application-level payload authorization; it does not fit the Automated scraping of protected records interpretation limit scenario, where a slow attacker may still access records belonging to other users.
D:This option addresses Leaked application database password because anyone who copied the string can still attempt authentication until rotation; the Automated scraping of protected records interpretation limit question instead turns on the fact that a slow attacker may still access records belonging to other users.