Question 270
A device makes hundreds of failed DNS lookups for random-looking domains at short intervals. What monitoring improvement would best help detect recurrence?
- Alert on internal port fan-out exceeding peer baseline
- Alert on lexical rarity combined with NXDOMAIN fan-out
- Alert on rare client profiles from normally closed server roles
- Detect periodic rare destinations with uncommon parent processes
- Alert on sensitive-host egress exceeding approved destination baselines
Explanation
Correct Answer
B:The Domain-generation algorithm surge evidence “A device makes hundreds of failed DNS lookups for random-looking domains at short intervals” is decisive for ongoing detection improvement because multiple discriminators improve on a rule matching any random-looking hostname.
Incorrect Answers
A:For the alternative East-west port scan detection situation, segment-specific baselines reduce benign scans and management chatter; by contrast, for Domain-generation algorithm surge ongoing detection improvement, multiple discriminators improve on a rule matching any random-looking hostname.
C:For the alternative Anomalous TLS client fingerprint situation, asset-specific rarity is more discriminating than global fingerprint novelty; by contrast, for Domain-generation algorithm surge ongoing detection improvement, multiple discriminators improve on a rule matching any random-looking hostname.
D:In Regular command beacon intervals, combining cadence and provenance helps distinguish malware from agent telemetry; the reported Domain-generation algorithm surge case calls for a different ongoing detection improvement conclusion because multiple discriminators improve on a rule matching any random-looking hostname.
E:For the alternative Unusual outbound data volume situation, data movement must be evaluated against workload schedules and expected peers; by contrast, for Domain-generation algorithm surge ongoing detection improvement, multiple discriminators improve on a rule matching any random-looking hostname.
Question 271
A web application firewall reports a blocked injection payload while the origin access log shows no corresponding request. What record is most useful for confirming this specific pattern?
- WAF rule ID, matched component and disposition
- IIS status, substatus, time-taken and URI fields
- Apache access log URI, client, status and user agent
- API gateway identity result, route and token validation reason
Explanation
Correct Answer
A:The WAF blocked request telemetry evidence “A web application firewall reports a blocked injection payload while the origin access log shows no corresponding request” is decisive for corroboration because these fields establish what rule fired and whether the request was blocked or monitored.
Incorrect Answers
B:For corroboration in WAF blocked request telemetry, IIS request diagnostics is a different mechanism: substatus and affected paths narrow the failure mode beyond a top-level 500 count; here, these fields establish what rule fired and whether the request was blocked or monitored.
C:The choice is relevant to Apache path enumeration logs, where those fields show which paths were tried and which requests succeeded; for corroboration in WAF blocked request telemetry, these fields establish what rule fired and whether the request was blocked or monitored.
D:For corroboration in WAF blocked request telemetry, API gateway authentication logs is a different mechanism: auth failure codes help distinguish expired tokens from missing authorization scope; here, these fields establish what rule fired and whether the request was blocked or monitored.
Question 272
An organization needs to prioritize exposed cloud assets and misconfigurations identified across Google Cloud projects. Which interpretive boundary is most relevant to this situation?
- Some data-access audit streams have different enablement or access requirements
- A posture finding does not necessarily mean an adversary exploited the issue
- Serverless abstraction does not mean outbound traffic is automatically safe
- Different cloud usernames may represent one underlying principal
Explanation
Correct Answer
B:For interpretation limit in Google Cloud Security Command Center posture, exposure and confirmed activity are separate evidence classes; this applies to the reported “An organization needs to prioritize exposed cloud assets and misconfigurations identified across Google Cloud projects”.
Incorrect Answers
A:For interpretation limit in Google Cloud Security Command Center posture, Google Cloud audit log principal investigation is a different mechanism: do not assume every operation appears in an identical default log category; here, exposure and confirmed activity are separate evidence classes.
C:For interpretation limit in Google Cloud Security Command Center posture, Cloud function unusual outbound connections is a different mechanism: application code still determines what data can be sent externally; here, exposure and confirmed activity are separate evidence classes.
D:The choice is relevant to Cross-cloud incident correlation, where identity mapping requires stable claims rather than simple display-name matching; for interpretation limit in Google Cloud Security Command Center posture, exposure and confirmed activity are separate evidence classes.
Question 273
A malicious flow is logged from a private address that was reassigned to another device earlier the same day. Which engineering change provides the most relevant ongoing visibility?
- Include resolver client identity in centralized telemetry
- Retain DHCP mappings for at least the investigation horizon
- Alert on unusual VPN origin plus sensitive internal access
- Enrich IDS alerts with firewall action and asset exposure
Explanation
Correct Answer
B:For ongoing detection improvement in DHCP lease attribution, IP-only telemetry is less useful when old leases have expired; this applies to the reported “A malicious flow is logged from a private address that was reassigned to another device earlier the same day”.
Incorrect Answers
A:In Recursive DNS resolver attribution, upstream firewall source addresses cannot reveal the actual requesting endpoint; the reported DHCP lease attribution case calls for a different ongoing detection improvement conclusion because IP-only telemetry is less useful when old leases have expired.
C:In VPN session authentication audit, combining context avoids flagging every traveler or mobile provider route; the reported DHCP lease attribution case calls for a different ongoing detection improvement conclusion because IP-only telemetry is less useful when old leases have expired.
D:For the alternative IDS signature alert context situation, paired context reduces false statements about impact; by contrast, for DHCP lease attribution ongoing detection improvement, IP-only telemetry is less useful when old leases have expired.
Question 274
A trusted application receives a sudden increase in valid tokens for an account with no corresponding interactive logins. Which technical explanation is most defensible from the evidence?
- Unexpected reactivation of a stale identity
- Geographically implausible account activity
- Potential noninteractive token abuse
- MFA push bombardment with possible approval
Explanation
Correct Answer
C:For classification in Unusual federation token issuance, stolen refresh tokens or service tokens may support access without repeated password prompts; this applies to the reported “A trusted application receives a sudden increase in valid tokens for an account with no corresponding interactive logins”.
Incorrect Answers
A:This option addresses Dormant account revival because dormant accounts are attractive targets when disablement and periodic entitlement review are weak; the Unusual federation token issuance classification question instead turns on the fact that stolen refresh tokens or service tokens may support access without repeated password prompts.
B:That option fits Impossible travel sign-in correlation since travel speed between accepted sign-ins can indicate shared credentials when identity and network context support the inference; it does not fit the Unusual federation token issuance classification scenario, where stolen refresh tokens or service tokens may support access without repeated password prompts.
D:That option fits MFA fatigue notification storm since repeated unsolicited prompts can pressure a user into accepting an attacker-initiated sign-in; it does not fit the Unusual federation token issuance classification scenario, where stolen refresh tokens or service tokens may support access without repeated password prompts.
Question 275
A high-reputation feed flags a cloud IP used by several legitimate customers six months after the original malicious observation. Which source would most directly corroborate the observation?
- First-seen, last-seen, provider confidence and hosting context
- Normalized hash with source references and timestamps
- STIX bundle objects with IDs and relationship references
- TAXII API collection metadata and authentication settings
Explanation
Correct Answer
A:Given “A high-reputation feed flags a cloud IP used by several legitimate customers six months after the original malicious observation”, source metadata shows whether the observation still describes today's owner; that best addresses corroboration in Threat feed confidence decay.
Incorrect Answers
B:That option fits Threat intelligence platform deduplication since a single observable can link to several different sightings and assessments; it does not fit the Threat feed confidence decay corroboration scenario, where source metadata shows whether the observation still describes today's owner.
C:This option addresses STIX structured intelligence exchange because object types and links preserve context beyond a plain text indicator list; the Threat feed confidence decay corroboration question instead turns on the fact that source metadata shows whether the observation still describes today's owner.
D:That option fits TAXII intelligence distribution since collection discovery and credentials define what intelligence can be retrieved; it does not fit the Threat feed confidence decay corroboration scenario, where source metadata shows whether the observation still describes today's owner.
Question 276
Employees scanned QR images in office notices and reached an external login replica absent from email URL scanners. Which engineering change provides the most relevant ongoing visibility?
- Restrict risky consent workflows and monitor new grants
- Block related URLs and detect similar inbound subjects cautiously
- Improve attachment sandboxing and document-child-process rules
- Extend anti-phishing inspection and awareness to QR links
- Require dual control for payment changes and unusual instructions
Explanation
Correct Answer
D:Decoded destinations need the same trust analysis as ordinary URLs; this is the relevant ongoing detection improvement mechanism for QR-code phishing landing page given “Employees scanned QR images in office notices and reached an external login replica absent from email URL scanners”.
Incorrect Answers
A:For the alternative Malicious OAuth app consent response situation, app governance reduces recurrence without disabling legitimate integrations; by contrast, for QR-code phishing landing page ongoing detection improvement, decoded destinations need the same trust analysis as ordinary URLs.
B:In Targeted phishing mail delivery, campaign signatures support rapid suppression while impersonators vary wording; the reported QR-code phishing landing page case calls for a different ongoing detection improvement conclusion because decoded destinations need the same trust analysis as ordinary URLs.
C:For the alternative Malicious email attachment execution situation, delivery and runtime controls provide defense in depth; by contrast, for QR-code phishing landing page ongoing detection improvement, decoded destinations need the same trust analysis as ordinary URLs.
E:For the alternative Business email compromise wire request situation, process safeguards reduce losses even when attackers impersonate trusted staff; by contrast, for QR-code phishing landing page ongoing detection improvement, decoded destinations need the same trust analysis as ordinary URLs.
Question 277
A new SOAR workflow automatically disables senior executives' accounts after a single uncorroborated anomaly score. Which working hypothesis is best supported by these facts?
- Unsafe automation on weak evidence
- Ungrounded AI-generated query content
- Untrusted feed text attempting AI instruction hijack
- Detection-model distribution drift
- Uncontrolled sensitive-log disclosure to AI service
Explanation
Correct Answer
A:The Automated response approval boundary evidence “A new SOAR workflow automatically disables senior executives' accounts after a single uncorroborated anomaly score” is decisive for classification because high-impact identity actions require confidence thresholds, safeguards and often explicit approval.
Incorrect Answers
B:This option addresses AI-generated SIEM rule hallucination because a fluent rule can be invalid or semantically empty when generated without source-schema validation; the Automated response approval boundary classification question instead turns on the fact that high-impact identity actions require confidence thresholds, safeguards and often explicit approval.
C:That option fits Prompt injection in threat enrichment since threat-intelligence content is data, not authority to control downstream SOC workflows; it does not fit the Automated response approval boundary classification scenario, where high-impact identity actions require confidence thresholds, safeguards and often explicit approval.
D:This option addresses AI alert score drift because changes in source features can make prior model thresholds unreliable without a system error; the Automated response approval boundary classification question instead turns on the fact that high-impact identity actions require confidence thresholds, safeguards and often explicit approval.
E:That option fits Sensitive data entered into AI copilot since incident artifacts can contain regulated information and secrets beyond the analyst's intended question; it does not fit the Automated response approval boundary classification scenario, where high-impact identity actions require confidence thresholds, safeguards and often explicit approval.
Question 278
A finance clerk receives an apparently internal urgent wire request after an executive mailbox shows anomalous sign-ins. What caution prevents an unsupported inference from these records?
- The presence of an executive display name does not authenticate a request
- A simple password change may not remove delegated application access
- A QR code is a carrier, not proof its destination is malicious
- A clicked link does not establish credential submission
- Removing the email after execution does not remove the malware
Explanation
Correct Answer
A:In the Business email compromise wire request case, a hijacked mailbox can produce familiar threads and correct sender details; the observation “A finance clerk receives an apparently internal urgent wire request after an executive mailbox shows anomalous sign-ins” makes this interpretation limit choice the fitting one.
Incorrect Answers
B:The choice is relevant to Malicious OAuth app consent response, where permission grants and cached tokens follow separate lifecycles; for interpretation limit in Business email compromise wire request, a hijacked mailbox can produce familiar threads and correct sender details.
C:For interpretation limit in Business email compromise wire request, QR-code phishing landing page is a different mechanism: legitimate login and enrollment processes also use scannable links; here, a hijacked mailbox can produce familiar threads and correct sender details.
D:The choice is relevant to Targeted phishing mail delivery, where form interaction or follow-on authentication evidence is needed to infer disclosure; for interpretation limit in Business email compromise wire request, a hijacked mailbox can produce familiar threads and correct sender details.
E:For interpretation limit in Business email compromise wire request, Malicious email attachment execution is a different mechanism: host persistence or stolen secrets may remain despite mailbox cleanup; here, a hijacked mailbox can produce familiar threads and correct sender details.
Question 279
A web application firewall reports a blocked injection payload while the origin access log shows no corresponding request. The finding has been corroborated and the response team has authorization to act. Which operational remedy is best aligned to the verified issue?
- Review the WAF decision and tune false positives conservatively
- Keep the malicious sample quarantined and hunt related recipients
- Suspend confirmed unauthorized grants and preserve audit trails
- Roll back a confirmed faulty deployment under change control
Explanation
Correct Answer
A:The WAF blocked request telemetry evidence “A web application firewall reports a blocked injection payload while the origin access log shows no corresponding request” is decisive for response decision because disabling a protective rule requires evidence that legitimate traffic is affected.
Incorrect Answers
B:For response decision in WAF blocked request telemetry, Email message trace analysis is a different mechanism: preserving evidence supports detection without restoring unsafe content to users; here, disabling a protective rule requires evidence that legitimate traffic is affected.
C:The choice is relevant to Database privileged query audit, where least-disruptive response should protect data and retain investigative evidence; for response decision in WAF blocked request telemetry, disabling a protective rule requires evidence that legitimate traffic is affected.
D:For response decision in WAF blocked request telemetry, IIS request diagnostics is a different mechanism: a functional regression needs repair rather than blind IP blocking; here, disabling a protective rule requires evidence that legitimate traffic is affected.
Question 280
An IIS-hosted application returns repeated HTTP 500 errors after deployment while client requests vary normally. What follow-up analysis most effectively distinguishes this case?
- Correlate application error logs with deployment change time
- Compare WAF time and action with origin server traffic
- Compare sensitive-table reads with job schedules and destinations
- Compare failure onset with key rotation and client versions
Explanation
Correct Answer
A:The IIS request diagnostics evidence “An IIS-hosted application returns repeated HTTP 500 errors after deployment while client requests vary normally” is decisive for scope analysis because an error spike after a rollout suggests a regression before an attack hypothesis.
Incorrect Answers
B:In WAF blocked request telemetry, a missing origin event can corroborate successful edge blocking; the reported IIS request diagnostics case calls for a different scope analysis conclusion because an error spike after a rollout suggests a regression before an attack hypothesis.
C:For the alternative Database privileged query audit situation, linking queries to approved application work exposes out-of-pattern data access; by contrast, for IIS request diagnostics scope analysis, an error spike after a rollout suggests a regression before an attack hypothesis.
D:In API gateway authentication logs, timing and deployed client behavior test the likely operational cause; the reported IIS request diagnostics case calls for a different scope analysis conclusion because an error spike after a rollout suggests a regression before an attack hypothesis.