Question 330
A signed Windows utility loads a DLL from a user's temporary download directory and contacts a novel host. How should the analyst classify the activity at this stage?
- Potential credential dumping chain
- Living-off-the-land DLL proxy execution
- Registry-based user persistence
- Coordinated defense-evasion configuration change
Explanation
Correct Answer
B:In the Rundll32 unusual DLL loading case, a trusted loader can execute attacker-supplied library code from an untrusted path; the observation “A signed Windows utility loads a DLL from a user's temporary download directory and contacts a novel host” makes this classification choice the fitting one.
Incorrect Answers
A:The choice is relevant to Credential store memory access, where sensitive-process access can precede extraction of authentication material when the caller is unauthorized; for classification in Rundll32 unusual DLL loading, a trusted loader can execute attacker-supplied library code from an untrusted path.
C:The choice is relevant to Persistence through registry Run key, where an autostart entry launches code when the affected account signs in; for classification in Rundll32 unusual DLL loading, a trusted loader can execute attacker-supplied library code from an untrusted path.
D:For classification in Rundll32 unusual DLL loading, Defender telemetry suppression attempt is a different mechanism: telemetry disappearing after administrative modifications may signal attackers disabling security controls; here, a trusted loader can execute attacker-supplied library code from an untrusted path.
Question 331
A departing engineer downloads hundreds of repository archives immediately before offboarding after months of limited activity. What monitoring improvement would best help detect recurrence?
- Detect unique-account counts in sliding source-IP windows
- Alert on rare bulk exports from sensitive repositories
- Detect suspicious forwarding rules plus external financial requests
- Detect newly consented high-risk third-party applications
Explanation
Correct Answer
B:In the Insider bulk source-code copying case, user baselines and asset labels improve specificity over raw download volume; the observation “A departing engineer downloads hundreds of repository archives immediately before offboarding after months of limited activity” makes this ongoing detection improvement choice the fitting one.
Incorrect Answers
A:For ongoing detection improvement in Insider bulk source-code copying, Password spraying across employees is a different mechanism: fan-out detection catches attacks that never exceed individual-user failure thresholds; here, user baselines and asset labels improve specificity over raw download volume.
C:For ongoing detection improvement in Insider bulk source-code copying, Business email compromise payment diversion is a different mechanism: mail and account telemetry together strengthen business email compromise detection; here, user baselines and asset labels improve specificity over raw download volume.
D:The choice is relevant to OAuth consent phishing, where permission risk and publisher reputation can prioritize OAuth abuse alerts; for ongoing detection improvement in Insider bulk source-code copying, user baselines and asset labels improve specificity over raw download volume.
Question 332
An employee reports a suspicious attachment but the inbox no longer holds the message after an automated quarantine. Which working hypothesis is best supported by these facts?
- IIS server-error logging
- Mail transport message tracing
- Database activity audit deviation
- Web application firewall enforcement record
Explanation
Correct Answer
B:For classification in Email message trace analysis, transport logs retain sender, recipient and delivery actions independently of mailbox visibility; this applies to the reported “An employee reports a suspicious attachment but the inbox no longer holds the message after an automated quarantine”.
Incorrect Answers
A:For the alternative IIS request diagnostics situation, windows web server logs capture status and substatus that help distinguish application failures from access denials; by contrast, for Email message trace analysis classification, transport logs retain sender, recipient and delivery actions independently of mailbox visibility.
C:For the alternative Database privileged query audit situation, database audit records may show sensitive queries executed under a principal and session; by contrast, for Email message trace analysis classification, transport logs retain sender, recipient and delivery actions independently of mailbox visibility.
D:In WAF blocked request telemetry, a WAF can reject an HTTP request before it reaches the protected application; the reported Email message trace analysis case calls for a different classification conclusion because transport logs retain sender, recipient and delivery actions independently of mailbox visibility.
Question 333
Event 1102 records a Windows Security log being cleared during an administrator's remote session. Which THREE cautions are appropriate when documenting the event? Choose THREE.
- The clearing event does not reconstruct the records that were removed.
- Event 1102 always proves an intruder—not an administrator—performed the action.
- Authorized maintenance can also produce a log-clear event, so the change context matters.
- The event reliably identifies every earlier command run by the clearing account.
- The event itself proves no forwarding or central log copies exist.
- Collector coverage and chronology determine how much pre-clear activity can still be recovered.
Explanation
Correct Answers
A:Event 1102 can demonstrate an audit-log-clear operation, but it does not contain the prior log entries. Central forwarding, backups or other telemetry are needed to rebuild missing activity.
C:The action is unusual and sensitive but not categorically malicious. Validated maintenance windows and administrator actions help interpret it without dismissing potential abuse.
F:A forwarder might have shipped relevant events before the clear, or it might have been disabled. The retained sequence and ingest health set limits on any reconstructed timeline.
Incorrect Answers
B:The event indicates the log was cleared, not the operator's malicious intent. Authorized maintenance and administrative activity must be checked against identity and change records.
D:The log-clear record is not a command history. Process records and retained upstream logs are separate evidence sources needed for earlier behavior.
E:A local log-clear operation does not establish the state of remote retention. The analyst should query collectors and immutable archives rather than assume evidence was lost everywhere.
Question 334
An AWS investigator needs to identify which IAM principal disabled object logging in a production account. What record is most useful for confirming this specific pattern?
- Resource diagnostic settings and workspace ingestion tables
- Security Hub finding records with provider and resource associations
- GuardDuty finding type, resource and supporting event context
- CloudTrail eventName, userIdentity and sourceIPAddress
Explanation
Correct Answer
D:These fields identify the action and the principal AWS recorded as making the call; this is the relevant corroboration mechanism for AWS CloudTrail API activity given “An AWS investigator needs to identify which IAM principal disabled object logging in a production account”.
Incorrect Answers
A:For corroboration in AWS CloudTrail API activity, Azure Monitor diagnostic data routing is a different mechanism: collection configuration establishes which categories are actually forwarded; here, these fields identify the action and the principal AWS recorded as making the call.
B:The choice is relevant to AWS Security Hub finding consolidation, where provider metadata preserves the origin of normalized finding information; for corroboration in AWS CloudTrail API activity, these fields identify the action and the principal AWS recorded as making the call.
C:For corroboration in AWS CloudTrail API activity, AWS GuardDuty threat finding is a different mechanism: the finding identifies the affected principal or resource and suspected behavior; here, these fields identify the action and the principal AWS recorded as making the call.
Question 335
A hash blocklist stops one malicious sample but a recompilation evades matching despite unchanged attacker behavior. The analyst has not yet established malicious intent or downstream impact. What qualification is most important before drawing a firm conclusion?
- TAXII does not itself validate the truth of indicators
- STIX is a data model rather than the feed transport protocol
- A digest is an exact artifact identifier, not a family-level guarantee
- Multiple copies of one IoC are not independent confirmations
Explanation
Correct Answer
C:Given “A hash blocklist stops one malicious sample but a recompilation evades matching despite unchanged attacker behavior”, repacking or small binary changes produce a different value; that best addresses interpretation limit in Malware hash IoC specificity.
Incorrect Answers
A:The choice is relevant to TAXII intelligence distribution, where transporting structured content cannot replace source-confidence assessment; for interpretation limit in Malware hash IoC specificity, repacking or small binary changes produce a different value.
B:For interpretation limit in Malware hash IoC specificity, STIX structured intelligence exchange is a different mechanism: a sharing interface still needs a method for exchanging the content; here, repacking or small binary changes produce a different value.
D:For interpretation limit in Malware hash IoC specificity, Threat intelligence platform deduplication is a different mechanism: feed syndication may repeat one original claim through several intermediaries; here, repacking or small binary changes produce a different value.
Question 336
An object-storage bucket containing internal invoices is accidentally configured for public reading during a deployment. The finding has been corroborated and the response team has authorization to act. Which targeted action should the authorized response team prioritize?
- Remove public access and rotate any secrets stored inside
- Revoke compromised access paths and correct overly broad trust
- Disable the malicious credential and remove unauthorized role assignments
- Disable exposed key material and migrate to safer workload identity
Explanation
Correct Answer
A:Containment closes access paths while handling contents that may already be leaked; this is the relevant response decision mechanism for Cloud storage anonymous exposure given “An object-storage bucket containing internal invoices is accidentally configured for public reading during a deployment”.
Incorrect Answers
B:The choice is relevant to AWS unauthorized role assumption, where containing the principal and role policy stops repeated assumptions; for response decision in Cloud storage anonymous exposure, containment closes access paths while handling contents that may already be leaked.
C:For response decision in Cloud storage anonymous exposure, Azure automation identity misuse is a different mechanism: both secret access and existing authorization paths must be addressed; here, containment closes access paths while handling contents that may already be leaked.
D:The choice is relevant to GCP service account key exposed, where key removal stops new use while preserving authorized applications; for response decision in Cloud storage anonymous exposure, containment closes access paths while handling contents that may already be leaked.
Question 337
A file appears innocuous statically but creates a persistence entry and contacts an unknown server when detonated. Which source would most directly corroborate the observation?
- Sandbox process tree, registry diffs and network trace
- Process memory map and injected-region forensic dump
- VBA source, document relationships and embedded objects
- Section entropy, unpacking stub and execution traces
Explanation
Correct Answer
A:In the Sandbox process and network observation case, combined activity shows what the sample changed and where it communicated; the observation “A file appears innocuous statically but creates a persistence entry and contacts an unknown server when detonated” makes this corroboration choice the fitting one.
Incorrect Answers
B:For corroboration in Sandbox process and network observation, Memory-only payload identification is a different mechanism: executable anonymous regions and thread starts can reveal code loaded outside normal modules; here, combined activity shows what the sample changed and where it communicated.
C:The choice is relevant to Macro document content extraction, where these artifacts expose script commands and payload dependencies; for corroboration in Sandbox process and network observation, combined activity shows what the sample changed and where it communicated.
D:For corroboration in Sandbox process and network observation, Packed executable entropy analysis is a different mechanism: packaging clues can explain why static inspection reveals little content; here, combined activity shows what the sample changed and where it communicated.
Question 338
A low-confidence endpoint detection fires on a server containing sensitive identity keys and remains unassigned. What follow-up analysis most effectively distinguishes this case?
- Compare the flagged sequence with verified maintenance artifacts
- Validate whether the observed action touched sensitive assets
- Trace network path and confirm target process or application state
- Verify key timestamps, confidence and attempted triage actions
Explanation
Correct Answer
B:In the Low-confidence alert with crown-jewel impact case, impact scoping can raise priority before final attack attribution; the observation “A low-confidence endpoint detection fires on a server containing sensitive identity keys and remains unassigned” makes this scope analysis choice the fitting one.
Incorrect Answers
A:The choice is relevant to Benign admin activity resembling attack, where the analyst must test the explanation instead of closing every matching alert; for scope analysis in Low-confidence alert with crown-jewel impact, impact scoping can raise priority before final attack attribution.
C:The choice is relevant to Conflicting alert severity from two sources, where a perimeter signature does not imply on-host compromise; for scope analysis in Low-confidence alert with crown-jewel impact, impact scoping can raise priority before final attack attribution.
D:For scope analysis in Low-confidence alert with crown-jewel impact, Alert escalation missing supporting evidence is a different mechanism: handoff quality depends on communicating known facts and unresolved questions; here, impact scoping can raise priority before final attack attribution.
Question 339
An external monitoring provider forwards high-severity notices but cannot explain who is permitted to isolate a customer workstation. Which scoping query or comparison best tests the working hypothesis?
- Follow one linked identity-network alert from intake to closure
- Trace a sample escalation through provider and customer roles
- Audit outstanding cases at regional shift boundaries
- Compare equivalent incidents across unit-specific queues
Explanation
Correct Answer
B:Reconstructing an actual handoff identifies the decision owner and missing authorization point; this is the relevant scope analysis mechanism for Managed SOC provider accountability given “An external monitoring provider forwards high-severity notices but cannot explain who is permitted to isolate a customer workstation”.
Incorrect Answers
A:That option fits Co-managed SOC handoff since a complete timeline exposes which team failed to preserve evidence or assign a decision maker; it does not fit the Managed SOC provider accountability scope analysis scenario, where reconstructing an actual handoff identifies the decision owner and missing authorization point.
C:That option fits Follow-the-sun SOC transfer since comparing end-of-shift and start-of-shift records identifies lost context during transfer; it does not fit the Managed SOC provider accountability scope analysis scenario, where reconstructing an actual handoff identifies the decision owner and missing authorization point.
D:This option addresses Virtual SOC tool integration because mapping status, severity and response ownership tests whether the operating process is consistent; the Managed SOC provider accountability scope analysis question instead turns on the fact that reconstructing an actual handoff identifies the decision owner and missing authorization point.
Question 340
Executives track average alert handling time but cannot see how long confirmed intrusions ran before discovery. The analyst has not yet established malicious intent or downstream impact. Which caveat most directly affects assessment of the evidence?
- A low alert count does not automatically identify the best rule
- A successful query over received logs is not proof of complete visibility
- Incident start time may be estimated rather than observed
- An average below the target does not mean every case met its SLA
Explanation
Correct Answer
C:Given “Executives track average alert handling time but cannot see how long confirmed intrusions ran before discovery”, MTTD reporting should acknowledge uncertainty in the earliest known malicious action; that best addresses interpretation limit in Incident detection latency dashboard.
Incorrect Answers
A:In Noisy use-case Pareto dashboard, a rarely triggered high-impact rule can be extremely valuable; the reported Incident detection latency dashboard case calls for a different interpretation limit conclusion because MTTD reporting should acknowledge uncertainty in the earliest known malicious action.
B:For the alternative SOC data-source coverage dashboard situation, uncollected events are invisible to every search and rule; by contrast, for Incident detection latency dashboard interpretation limit, MTTD reporting should acknowledge uncertainty in the earliest known malicious action.
D:For the alternative SLA breach trend by incident tier situation, a few severe outliers still require explicit reporting; by contrast, for Incident detection latency dashboard interpretation limit, MTTD reporting should acknowledge uncertainty in the earliest known malicious action.