Question 310
A database node sends tens of gigabytes to an external address shortly after an unauthorized account login. What record is most useful for confirming this specific pattern?
- DNS query strings with NXDOMAIN outcomes by client
- Proxy timing series and endpoint initiating process
- TLS handshake metadata with JA3-like fingerprint and destination
- Flow-byte counts joined to database authentication history
Explanation
Correct Answer
D:For corroboration in Unusual outbound data volume, network volume and actor evidence are necessary to link transfer with the suspected account; this applies to the reported “A database node sends tens of gigabytes to an external address shortly after an unauthorized account login”.
Incorrect Answers
A:For corroboration in Unusual outbound data volume, Domain-generation algorithm surge is a different mechanism: high unique-domain count and lexical patterns reveal unsuccessful domain cycling; here, network volume and actor evidence are necessary to link transfer with the suspected account.
B:The choice is relevant to Regular command beacon intervals, where periodic flow alone is weak; the process and network identity provide useful corroboration; for corroboration in Unusual outbound data volume, network volume and actor evidence are necessary to link transfer with the suspected account.
C:For corroboration in Unusual outbound data volume, Anomalous TLS client fingerprint is a different mechanism: handshake characteristics offer context for encrypted connections but are not unique identities; here, network volume and actor evidence are necessary to link transfer with the suspected account.
Question 311
An Azure SOC needs to correlate suspicious Entra sign-ins with privileged resource changes in an analytics workspace. The analyst has not yet established malicious intent or downstream impact. What caution prevents an unsupported inference from these records?
- A GuardDuty finding is a lead, not a complete forensic record
- An Azure resource existing in a subscription does not guarantee its detailed logs are in Sentinel
- Security Hub is not a substitute for raw CloudTrail event history
- Microsoft Sentinel does not automatically ingest every Azure log category
- Not every service data operation is in a default management-event trail
Explanation
Correct Answer
D:For interpretation limit in Microsoft Sentinel analytic rule, connectors and diagnostic settings must supply the intended source events; this applies to the reported “An Azure SOC needs to correlate suspicious Entra sign-ins with privileged resource changes in an analytics workspace”.
Incorrect Answers
A:The choice is relevant to AWS GuardDuty threat finding, where investigation still requires original service logs and corroboration; for interpretation limit in Microsoft Sentinel analytic rule, connectors and diagnostic settings must supply the intended source events.
B:For interpretation limit in Microsoft Sentinel analytic rule, Azure Monitor diagnostic data routing is a different mechanism: source configuration and connector scope control availability; here, connectors and diagnostic settings must supply the intended source events.
C:The choice is relevant to AWS Security Hub finding consolidation, where findings summarize detections while detailed API reconstruction uses source logs; for interpretation limit in Microsoft Sentinel analytic rule, connectors and diagnostic settings must supply the intended source events.
E:The choice is relevant to AWS CloudTrail API activity, where data events often require explicit selection and incur separate considerations; for interpretation limit in Microsoft Sentinel analytic rule, connectors and diagnostic settings must supply the intended source events.
Question 312
An organization needs to prioritize exposed cloud assets and misconfigurations identified across Google Cloud projects. Which investigative step would most directly establish the relevant scope?
- Reconstruct the SSO assertion and resulting provider sessions
- Trace source parser, UDM field and detection match
- Compare misconfiguration findings with project ownership and exposure
- Correlate key creation with subsequent setIamPolicy operations
Explanation
Correct Answer
C:For scope analysis in Google Cloud Security Command Center posture, business criticality and actual access paths determine remediation priority; this applies to the reported “An organization needs to prioritize exposed cloud assets and misconfigurations identified across Google Cloud projects”.
Incorrect Answers
A:This option addresses Cross-cloud incident correlation because the attack timeline needs both identity and cloud service records; the Google Cloud Security Command Center posture scope analysis question instead turns on the fact that business criticality and actual access paths determine remediation priority.
B:That option fits Google Security Operations threat correlation since schema mapping and entity integrity are required for reliable correlation; it does not fit the Google Cloud Security Command Center posture scope analysis scenario, where business criticality and actual access paths determine remediation priority.
D:That option fits Google Cloud audit log principal investigation since a session sequence can reveal whether a new credential changed authorization; it does not fit the Google Cloud Security Command Center posture scope analysis scenario, where business criticality and actual access paths determine remediation priority.
Question 313
A server starts an unexpected job every ten minutes under an account that normally has no scheduled tasks. Which source would most directly corroborate the observation?
- Cron configuration files and scheduler execution records
- Journal suppression counters and daemon configuration
- auditd SYSCALL and EXECVE records with serial correlation
- sudo log entry including user, TTY and COMMAND fields
Explanation
Correct Answer
A:Task definitions and job-start entries identify what automation is recurring; this is the relevant corroboration mechanism for Linux cron persistence evidence given “A server starts an unexpected job every ten minutes under an account that normally has no scheduled tasks”.
Incorrect Answers
B:For corroboration in Linux cron persistence evidence, Linux dropped syslog messages is a different mechanism: dropped-message warnings explain why the apparent event volume suddenly fell; here, task definitions and job-start entries identify what automation is recurring.
C:The choice is relevant to Linux auditd execution records, where combining related records reconstructs the command and security context; for corroboration in Linux cron persistence evidence, task definitions and job-start entries identify what automation is recurring.
D:For corroboration in Linux cron persistence evidence, Linux sudo elevation audit is a different mechanism: these attributes expose who requested elevation and the command that was invoked; here, task definitions and job-start entries identify what automation is recurring.
Question 314
An exposed API receives many unauthorized requests with rotating tokens and a small set of sensitive resource endpoints. The analyst has not yet established malicious intent or downstream impact. Which caveat most directly affects assessment of the evidence?
- A 401 burst might follow a legitimate client key rotation
- A backend error does not guarantee successful data theft
- A large upload is not automatically confirmed data theft
- A new admin role is not proof the account exercised that privilege
Explanation
Correct Answer
A:Deployment history must be checked before labeling operational failures as attacks; this is the relevant interpretation limit mechanism for API bearer-token guessing given “An exposed API receives many unauthorized requests with rotating tokens and a small set of sensitive resource endpoints”.
Incorrect Answers
B:The choice is relevant to WAF bypass with origin success, where exploit attempts can fail after reaching vulnerable code without returning sensitive records; for interpretation limit in API bearer-token guessing, deployment history must be checked before labeling operational failures as attacks.
C:For interpretation limit in API bearer-token guessing, Massive object-storage upload through web app is a different mechanism: the classification depends on destination authorization and data sensitivity; here, deployment history must be checked before labeling operational failures as attacks.
D:The choice is relevant to Unexpected web administrative role assignment, where access grants and subsequent privileged operations are distinct facts; for interpretation limit in API bearer-token guessing, deployment history must be checked before labeling operational failures as attacks.
Question 315
An analyst examines an unknown Windows executable without executing it and observes suspicious imports and a malformed section table. What monitoring improvement would best help detect recurrence?
- Detect macro-enabled attachments with suspicious process-spawn APIs
- Create vetted signatures from stable extracted artifacts
- Record packer features and recovered behavioral signatures
- Develop detections for observed persistence and egress patterns
Explanation
Correct Answer
B:The Static PE import inspection evidence “An analyst examines an unknown Windows executable without executing it and observes suspicious imports and a malformed section table” is decisive for ongoing detection improvement because static indicators can support blocking but need false-positive validation.
Incorrect Answers
A:In Macro document content extraction, static content rules complement runtime behavioral monitoring; the reported Static PE import inspection case calls for a different ongoing detection improvement conclusion because static indicators can support blocking but need false-positive validation.
C:In Packed executable entropy analysis, behavioral indicators are less fragile than a packer name alone; the reported Static PE import inspection case calls for a different ongoing detection improvement conclusion because static indicators can support blocking but need false-positive validation.
D:For the alternative Sandbox process and network observation situation, behavioral findings can be translated into endpoint and SIEM analytics; by contrast, for Static PE import inspection ongoing detection improvement, static indicators can support blocking but need false-positive validation.
Question 316
A busy application host reports a rate-limit warning, then a monitoring dashboard shows suspiciously few subsequent events. Which technical explanation is most defensible from the evidence?
- Sudo privilege escalation audit trail
- macOS unified logging visibility
- OpenSSH authentication trail
- Local logging rate-limit loss
Explanation
Correct Answer
D:For classification in Linux dropped syslog messages, syslog or journald throttling can discard messages during bursts before a SIEM receives them; this applies to the reported “A busy application host reports a rate-limit warning, then a monitoring dashboard shows suspiciously few subsequent events”.
Incorrect Answers
A:This option addresses Linux sudo elevation audit because authorized sudo use is recorded with invoking account and command under typical logging configurations; the Linux dropped syslog messages classification question instead turns on the fact that syslog or journald throttling can discard messages during bursts before a SIEM receives them.
B:That option fits macOS unified log investigation since modern macOS uses a structured unified logging subsystem rather than only traditional plaintext logs; it does not fit the Linux dropped syslog messages classification scenario, where syslog or journald throttling can discard messages during bursts before a SIEM receives them.
C:This option addresses Linux SSH authentication messages because system authentication logs can reveal user, origin and result for remote SSH attempts; the Linux dropped syslog messages classification question instead turns on the fact that syslog or journald throttling can discard messages during bursts before a SIEM receives them.
Question 317
The SIEM shows a suspicious injection request allowed at the WAF and a matching database error at the origin. Which step would most precisely determine the affected entities?
- Check source records and approved integration destination list
- Reconstruct matched HTTP request from edge to application
- Group invalid-token requests by client fingerprint and resource
- Inspect the endpoint's source file and child command tree
Explanation
Correct Answer
B:The WAF bypass with origin success evidence “The SIEM shows a suspicious injection request allowed at the WAF and a matching database error at the origin” is decisive for scope analysis because following the trace identifies the vulnerable parameter and whether an operation completed.
Incorrect Answers
A:For scope analysis in WAF bypass with origin success, Massive object-storage upload through web app is a different mechanism: business-approved ETL jobs must be distinguished from an illicit export; here, following the trace identifies the vulnerable parameter and whether an operation completed.
C:For scope analysis in WAF bypass with origin success, API bearer-token guessing is a different mechanism: shared automation characteristics matter even when source IPs rotate; here, following the trace identifies the vulnerable parameter and whether an operation completed.
D:The choice is relevant to Web-shell request and process correlation, where file provenance and execution output establish the suspected web shell's capabilities; for scope analysis in WAF bypass with origin success, following the trace identifies the vulnerable parameter and whether an operation completed.
Question 318
The same weak password is tried once against hundreds of corporate users over a short window. How should the analyst classify the activity at this stage?
- Remote service-based lateral execution
- Wide low-frequency password spraying
- Document-driven script execution
- Conversation hijack for payment redirection
- Malicious delegated OAuth authorization
Explanation
Correct Answer
B:Given “The same weak password is tried once against hundreds of corporate users over a short window”, an attacker spreads guesses across accounts to avoid per-user lockout thresholds; that best addresses classification in Password spraying across employees.
Incorrect Answers
A:The choice is relevant to Lateral movement via remote service, where administrative access can copy or launch payloads through a remote service-control interface; for classification in Password spraying across employees, an attacker spreads guesses across accounts to avoid per-user lockout thresholds.
C:The choice is relevant to Malicious Office macro delivery, where a macro or embedded automation can launch child processes and pull a second-stage payload; for classification in Password spraying across employees, an attacker spreads guesses across accounts to avoid per-user lockout thresholds.
D:For classification in Password spraying across employees, Business email compromise payment diversion is a different mechanism: a compromised or impersonated conversation can exploit existing trust to change payment details; here, an attacker spreads guesses across accounts to avoid per-user lockout thresholds.
E:The choice is relevant to OAuth consent phishing, where a consent grant can let an app access data through tokens even without disclosing the user's password; for classification in Password spraying across employees, an attacker spreads guesses across accounts to avoid per-user lockout thresholds.
Question 319
Critical incidents appear within target on an overall dashboard but several have exceeded the escalation SLA. Which investigative step would most directly establish the relevant scope?
- Compare rates on a stable cohort of unchanged sensors
- Compare onboarded sources against required asset classes
- Calculate breach rates using each tier's defined deadline
- Rank rules by false-positive effort and true-positive yield
Explanation
Correct Answer
C:The SLA breach trend by incident tier evidence “Critical incidents appear within target on an overall dashboard but several have exceeded the escalation SLA” is decisive for scope analysis because aggregated elapsed time cannot be compared to mixed SLA thresholds.
Incorrect Answers
A:In Threat trend comparison without normalization, holding the monitored population constant avoids conflating telemetry growth with threat growth; the reported SLA breach trend by incident tier case calls for a different scope analysis conclusion because aggregated elapsed time cannot be compared to mixed SLA thresholds.
B:For the alternative SOC data-source coverage dashboard situation, inventory reconciliation reveals absent servers, networks and cloud accounts; by contrast, for SLA breach trend by incident tier scope analysis, aggregated elapsed time cannot be compared to mixed SLA thresholds.
D:For the alternative Noisy use-case Pareto dashboard situation, a Pareto view highlights changes with the largest operational benefit; by contrast, for SLA breach trend by incident tier scope analysis, aggregated elapsed time cannot be compared to mixed SLA thresholds.
Question 320
A user workstation requests many Kerberos service tickets for unusually privileged service principals. What security condition most directly explains the pattern?
- Potential insider data collection
- Malicious delegated OAuth authorization
- Offline cracking of service-account tickets
- Document-driven script execution
- Conversation hijack for payment redirection
Explanation
Correct Answer
C:Given “A user workstation requests many Kerberos service tickets for unusually privileged service principals”, service ticket material can be collected and attacked offline when accounts use weak secrets; that best addresses classification in Kerberoasting service-ticket harvesting.
Incorrect Answers
A:For the alternative Insider bulk source-code copying situation, unusual repository access by a soon-departing user can indicate unauthorized gathering of sensitive material; by contrast, for Kerberoasting service-ticket harvesting classification, service ticket material can be collected and attacked offline when accounts use weak secrets.
B:In OAuth consent phishing, a consent grant can let an app access data through tokens even without disclosing the user's password; the reported Kerberoasting service-ticket harvesting case calls for a different classification conclusion because service ticket material can be collected and attacked offline when accounts use weak secrets.
D:In Malicious Office macro delivery, a macro or embedded automation can launch child processes and pull a second-stage payload; the reported Kerberoasting service-ticket harvesting case calls for a different classification conclusion because service ticket material can be collected and attacked offline when accounts use weak secrets.
E:For the alternative Business email compromise payment diversion situation, a compromised or impersonated conversation can exploit existing trust to change payment details; by contrast, for Kerberoasting service-ticket harvesting classification, service ticket material can be collected and attacked offline when accounts use weak secrets.