Question 140
An administrator appears to have disabled logging in a cloud account before deleting resources. Select the approach that most closely fits the investigative objective.
- Preserve transaction-related records and correlate them with application request identifiers
- Request scoped SaaS audit and retention evidence through authorized administrative access
- Preserve control-plane audit records independently from the affected instance
- Compare on-device evidence with authorized cloud-synchronized copies
Explanation
Correct Answer
C:For Cloud control-plane activity, management API events show which principal requested configuration changes; control-plane history can reveal changes invisible in a deleted guest filesystem. When selecting the procedure for Cloud control-plane activity, the crucial limit is that an API principal may be assumed by automation or another actor.
Incorrect Answers
A:Compared with Cloud control-plane activity, database transaction evidence concerns a different indicator: committed operations and transaction timestamps may reconstruct changed rows and statements; the current task is selecting the procedure. For the Cloud control-plane activity decision about selecting the procedure, the separate database transaction evidence inference is transactional evidence links application events to persistent data changes; it does not establish the requested result.
B:Although SaaS audit-log availability may matter in another case because object activity and sharing events may be recorded independently of endpoint caches, this question asks about selecting the procedure for Cloud control-plane activity. The separate SaaS audit-log availability consideration is that Cloud application auditing may preserve evidence that endpoints no longer contain; it cannot substitute for selecting the procedure in the Cloud control-plane activity analysis.
D:Compared with Cloud control-plane activity, mobile synchronization artifact concerns a different indicator: different device and account timestamps reveal synchronization and deletion state; the current task is selecting the procedure. For the Cloud control-plane activity decision about selecting the procedure, the separate mobile synchronization artifact inference is cross-device synchronization affects which endpoint can be attributed a message; it does not establish the requested result.
Question 141
A small text file occupies a cluster larger than the bytes reported by its logical length. Select the approach that most closely fits the investigative objective.
- Reconstruct RAID order, stripe size, and parity layout before filesystem parsing
- Inspect the MBR partition records and active boot indicator
- Inspect bytes between end-of-file and the allocated cluster boundary
- Carve unallocated sectors using file signatures and structural validation
Explanation
Correct Answer
C:For file slack analysis, residual cluster bytes can persist beyond the active file's logical content; slack bytes require cautious provenance interpretation independent of the visible file. When selecting the procedure for file slack analysis, the crucial limit is that slack content may belong to earlier allocations and not to the current file owner.
Incorrect Answers
A:The RAID reconstruction alternative points to a different lead: a valid assembled logical image exposes consistent volume structures across drives; it does not settle selecting the procedure for file slack analysis. The RAID reconstruction interpretation, array geometry determines how physical member bytes form logical evidence, cannot replace file slack analysis evidence for selecting the procedure.
B:The MBR partition table alternative points to a different lead: legacy sector-zero entries describe starting sectors, lengths, and partition types; it does not settle selecting the procedure for file slack analysis. The MBR partition table interpretation, an MBR map describes a legacy partition layout rather than the files inside it, cannot replace file slack analysis evidence for selecting the procedure.
D:The unallocated-space carving alternative points to a different lead: recognizable headers and trailers permit recovery of some orphaned content; it does not settle selecting the procedure for file slack analysis. The unallocated-space carving interpretation, carved content can establish data presence without proving the original pathname, cannot replace file slack analysis evidence for selecting the procedure.
Question 142
A case lead requests a targeted response. The examiner has offline Windows registry hives and needs artifact-focused extraction. Which approach is most relevant?
- Use RegRipper plugins appropriate to the hive and Windows version
- Use Plaso or log2timeline to parse supported artifacts into structured events
- Use KAPE targets for scoped collection and modules for post-collection processing
- Use osquery to query supported endpoint state tables with documented permissions
Explanation
Correct Answer
A:For RegRipper registry parsing, parsed keys may expose user activity, system configuration, and persistence locations; registry-focused parsers accelerate extraction but need source-aware interpretation. When selecting the procedure for RegRipper registry parsing, the crucial limit is that a plugin's output depends on hive compatibility and available transaction state.
Incorrect Answers
B:Compared with RegRipper registry parsing, Plaso timeline generation concerns a different indicator: parsed event records can be normalized, filtered, and exported for temporal correlation; the current task is selecting the procedure. For the RegRipper registry parsing decision about selecting the procedure, the separate Plaso timeline generation inference is a timeline engine aggregates evidence but does not prove causation by itself; it does not establish the requested result.
C:The KAPE artifact triage alternative points to a different lead: target definitions help capture relevant hives, logs, and user artifacts consistently; it does not settle selecting the procedure for RegRipper registry parsing. The KAPE artifact triage interpretation, KAPE supports repeatable triage acquisition and processing workflows, cannot replace RegRipper registry parsing evidence for selecting the procedure.
D:Compared with RegRipper registry parsing, osquery live endpoint state concerns a different indicator: SQL-like results expose current system state for live triage; the current task is selecting the procedure. For the RegRipper registry parsing decision about selecting the procedure, the separate osquery live endpoint state inference is osquery is useful for live state inspection rather than historical disk reconstruction; it does not establish the requested result.
Question 143
Which action would an examiner select for this evidence-handling challenge? A workstation uses Tor and an investigator attempts to identify the final visited site from its entry-node IP.
- Distinguish observable Tor entry connections from destination identification
- Request scoped SaaS audit and retention evidence through authorized administrative access
- Capture runtime metadata and ephemeral state before orchestrator replacement
- Normalize device events using gateway and controller timestamps
- Preserve transaction-related records and correlate them with application request identifiers
Explanation
Correct Answer
A:For Tor traffic limitations, a guard-node connection shows Tor network use rather than the final onion or website target; entry-node metadata cannot by itself identify the user's destination. When selecting the procedure for Tor traffic limitations, the crucial limit is that tor's relay design prevents inferring the destination from the first-hop address alone.
Incorrect Answers
B:Compared with Tor traffic limitations, SaaS audit-log availability concerns a different indicator: object activity and sharing events may be recorded independently of endpoint caches; the current task is selecting the procedure. For the Tor traffic limitations decision about selecting the procedure, the separate SaaS audit-log availability inference is Cloud application auditing may preserve evidence that endpoints no longer contain; it does not establish the requested result.
C:In an inquiry concerning ephemeral container evidence, short-lived container IDs, logs, and mounted-volume references survive only if collected; that supports a different purpose than selecting the procedure for Tor traffic limitations. This ephemeral container evidence material may suggest that ephemeral workload forensics depends on timely preservation outside the container, but it does not establish the Tor traffic limitations finding needed for selecting the procedure.
D:Compared with Tor traffic limitations, smart-home IoT timeline concerns a different indicator: gateway receipts establish a second chronology for the sensor's reported activity; the current task is selecting the procedure. For the Tor traffic limitations decision about selecting the procedure, the separate smart-home IoT timeline inference is IoT event timing must account for clock drift and store-and-forward delay; it does not establish the requested result.
E:In an inquiry concerning database transaction evidence, committed operations and transaction timestamps may reconstruct changed rows and statements; that supports a different purpose than selecting the procedure for Tor traffic limitations. This database transaction evidence material may suggest that transactional evidence links application events to persistent data changes, but it does not establish the Tor traffic limitations finding needed for selecting the procedure.
Question 144
A case lead requests a targeted response. A downloaded document called invoice.pdf.exe appeared in a folder with hidden known extensions. Which approach is most relevant?
- Inspect the full filename, file type signature, and execution history
- Assess wiping-tool behavior against storage-controller and allocation evidence
- Inspect scheduled tasks, scripts, WMI subscriptions, and memory process context
- Analyze packing indicators in a controlled setting before interpreting static strings
Explanation
Correct Answer
A:For filename spoofing, the actual extension and PE header reveal an executable masquerading as a document; extension tricks can conceal executable content from casual visual inspection. When selecting the procedure for filename spoofing, the crucial limit is that a deceptive name is an indicator of intent, not proof that the file ran.
Incorrect Answers
B:In an inquiry concerning secure wiping inference, deliberate overwrite patterns or tool execution traces can support data destruction activity; that supports a different purpose than selecting the procedure for filename spoofing. This secure wiping inference material may suggest that unrecoverable data alone does not establish use of a wiping utility, but it does not establish the filename spoofing finding needed for selecting the procedure.
C:Compared with filename spoofing, fileless persistence concerns a different indicator: execution may be triggered by script hosts or event subscriptions rather than a conventional file; the current task is selecting the procedure. For the filename spoofing decision about selecting the procedure, the separate fileless persistence inference is persistence can operate through platform facilities despite a missing standalone binary; it does not establish the requested result.
D:Compared with filename spoofing, packed-binary triage concerns a different indicator: entropy and section layout suggest compressed or encrypted executable content; the current task is selecting the procedure. For the filename spoofing decision about selecting the procedure, the separate packed-binary triage inference is packing complicates static inspection but does not independently establish malware; it does not establish the requested result.
Question 145
An investigation presents the following condition: A Mac has an APFS snapshot taken before a suspected file deletion. What is the soundest next step?
- Account for copy-on-write clone behavior when interpreting physical extents
- Compare the current APFS volume with an authorized preserved snapshot
- Correlate SSH authentication records with session identifiers and sudo activity
- Examine shell-history context alongside account sessions and command execution records
Explanation
Correct Answer
B:For macOS APFS snapshot, snapshot metadata and prior file states may reveal material absent from the live namespace; APFS snapshots provide point-in-time filesystem perspectives when available. When selecting the procedure for macOS APFS snapshot, the crucial limit is that snapshot presence and retention vary and do not imply complete application-history capture.
Incorrect Answers
A:Although APFS clone-file interpretation may matter in another case because logical files may share underlying blocks until modifications create new extents, this question asks about selecting the procedure for macOS APFS snapshot. The separate APFS clone-file interpretation consideration is that physical block sharing and independent logical file histories can coexist; it cannot substitute for selecting the procedure in the macOS APFS snapshot analysis.
C:Although Linux auth-log correlation may matter in another case because authentication lines and privilege-use records outline a candidate access sequence, this question asks about selecting the procedure for macOS APFS snapshot. The separate Linux auth-log correlation consideration is that SSH and privilege logs together clarify access and post-login actions; it cannot substitute for selecting the procedure in the macOS APFS snapshot analysis.
D:The Linux shell-history attribution alternative points to a different lead: a saved command list suggests commands entered in a shell profile; it does not settle selecting the procedure for macOS APFS snapshot. The Linux shell-history attribution interpretation, a shell history line is a lead, not independent proof of execution by a named person, cannot replace macOS APFS snapshot evidence for selecting the procedure.
Question 146
An investigation presents the following condition: A workstation initiates outbound traffic through a corporate proxy but direct packet capture lacks final web URLs. What is the soundest next step?
- Correlate XML parser input with network egress and local file-access records
- Inspect cookie validation and server-side authorization records for the request
- Correlate observed BSSID and channel data with approved access-point inventory
- Correlate proxy request identifiers with firewall flow records
- Correlate SMB session activity with remote service creation and host logons
Explanation
Correct Answer
D:For firewall and proxy log correlation, proxy URL and user context can supplement network-layer addresses and ports; layered network logs reveal different parts of the same connection path. When selecting the procedure for firewall and proxy log correlation, the crucial limit is that a firewall destination address alone may represent a shared proxy rather than the final site.
Incorrect Answers
A:Compared with firewall and proxy log correlation, XML external entity investigation concerns a different indicator: entity-resolution activity can produce server-side reads or requests outside intended input data; the current task is selecting the procedure. For the firewall and proxy log correlation decision about selecting the procedure, the separate XML external entity investigation inference is XXE impact requires proof that the parser resolved attacker-influenced resources; it does not establish the requested result.
B:Compared with firewall and proxy log correlation, cookie tampering assessment concerns a different indicator: a modified token accepted without proper integrity checks can permit session manipulation; the current task is selecting the procedure. For the firewall and proxy log correlation decision about selecting the procedure, the separate cookie tampering assessment inference is cookie tampering becomes an exploit when server-side trust decisions accept it; it does not establish the requested result.
C:Although wireless rogue AP triage may matter in another case because a previously unknown radio advertising the corporate SSID merits investigation, this question asks about selecting the procedure for firewall and proxy log correlation. The separate wireless rogue AP triage consideration is that BSSID and infrastructure evidence distinguish an impostor from a legitimate access point; it cannot substitute for selecting the procedure in the firewall and proxy log correlation analysis.
E:In an inquiry concerning SMB lateral-movement traces, administrative-share connections followed by remote execution suggest movement between hosts; that supports a different purpose than selecting the procedure for firewall and proxy log correlation. This SMB lateral-movement traces material may suggest that SMB access becomes more probative when linked to execution on target hosts, but it does not establish the firewall and proxy log correlation finding needed for selecting the procedure.
Question 147
An investigation presents the following condition: The logs cover only the final two days of a month-long alleged campaign. What is the soundest next step?
- Describe acquisition limitations before asserting the messages never existed
- Explicitly define the observed data window and any collection gaps
- Provide a reproducible exhibit trail from source offset through parsing and rendering
- Express a time range and uncertainty consistent with clock calibration evidence
- Correct the calculation and preserve the review finding and revision history
Explanation
Correct Answer
B:For time-bounded findings, readers can see which dates and hosts support the reported timeline; findings should not extend beyond the temporal coverage of the evidence. When selecting the procedure for time-bounded findings, the crucial limit is that no events in a short retention window cannot exonerate earlier activity.
Incorrect Answers
A:Compared with time-bounded findings, negative finding caveat concerns a different indicator: the missing result is interpreted relative to accessible partitions and extracted app data; the current task is selecting the procedure. For the time-bounded findings decision about selecting the procedure, the separate negative finding caveat inference is absence from a limited acquisition is weaker than proof of absence; it does not establish the requested result.
C:Compared with time-bounded findings, exhibit reproducibility concerns a different indicator: hash values, offsets, and tool parameters permit another examiner to reproduce the view; the current task is selecting the procedure. For the time-bounded findings decision about selecting the procedure, the separate exhibit reproducibility inference is traceable derivation makes complex exhibits independently verifiable; it does not establish the requested result.
D:The measurement precision alternative points to a different lead: time uncertainty bounds can prevent false precision in reconstructed sequences; it does not settle selecting the procedure for time-bounded findings. The measurement precision interpretation, forensic precision should reflect measurement quality, not just timestamp formatting, cannot replace time-bounded findings evidence for selecting the procedure.
E:The peer-review disposition alternative points to a different lead: the final report reflects a revised chronology with the original error accounted for; it does not settle selecting the procedure for time-bounded findings. The peer-review disposition interpretation, documented correction is part of defensible analytic quality assurance, cannot replace time-bounded findings evidence for selecting the procedure.
Question 148
A web server log shows a strange URI but the response status is not visible in a dashboard summary. What should the examiner prioritize to address the stated evidentiary need?
- Inspect EVTX record structure, retention settings, and export completeness
- Preserve and analyze the database with its write-ahead log and shared-memory context
- Read the underlying IIS W3C field definitions and complete request records
- Preserve the rollback journal and database together for transactional-state analysis
Explanation
Correct Answer
C:For IIS request-log fields, URI stem, query, client address, time, method, and status can be mapped by headers; parsing the actual field schema is essential to sound HTTP forensic interpretation. When selecting the procedure for IIS request-log fields, the crucial limit is that field order is configurable and guessing positions can misinterpret status codes.
Incorrect Answers
A:Compared with IIS request-log fields, Windows EVTX record integrity concerns a different indicator: record ranges and channel metadata reveal possible gaps or wraparound; the current task is selecting the procedure. For the IIS request-log fields decision about selecting the procedure, the separate Windows EVTX record integrity inference is event-log gaps demand integrity assessment before an accusation of clearing; it does not establish the requested result.
B:Compared with IIS request-log fields, SQLite write-ahead log concerns a different indicator: recent committed page changes may reside in WAL frames pending checkpointing; the current task is selecting the procedure. For the IIS request-log fields decision about selecting the procedure, the separate SQLite write-ahead log inference is database sidecar files can alter the apparent completeness of acquired evidence; it does not establish the requested result.
D:Compared with IIS request-log fields, SQLite rollback journal concerns a different indicator: rollback pages may contain pretransaction versions needed to restore consistency; the current task is selecting the procedure. For the IIS request-log fields decision about selecting the procedure, the separate SQLite rollback journal inference is transactional sidecars may hold evidence absent from ordinary table queries; it does not establish the requested result.
Question 149
An investigation presents the following condition: An investigator expects ext4 journaling to contain a complete copy of a deleted user document. What is the soundest next step?
- Review ext4 journal mode and metadata transactions rather than assuming full file data
- Decode the property-list structure without treating it as plain text
- Correlate SSH authentication records with session identifiers and sudo activity
- Analyze Spotlight metadata as a search-index lead, not sole proof of opening
- Examine shell-history context alongside account sessions and command execution records
Explanation
Correct Answer
A:For ext4 journal limits, journal records generally emphasize filesystem consistency and recent metadata operations; a filesystem journal is not a comprehensive historical content archive. When selecting the procedure for ext4 journal limits, the crucial limit is that the journal is circular and its mode does not guarantee recovery of user file contents.
Incorrect Answers
B:The macOS property lists alternative points to a different lead: structured keys and values reveal application configuration and stored state; it does not settle selecting the procedure for ext4 journal limits. The macOS property lists interpretation, plist interpretation benefits from schema-aware parsing and contextual checks, cannot replace ext4 journal limits evidence for selecting the procedure.
C:Although Linux auth-log correlation may matter in another case because authentication lines and privilege-use records outline a candidate access sequence, this question asks about selecting the procedure for ext4 journal limits. The separate Linux auth-log correlation consideration is that SSH and privilege logs together clarify access and post-login actions; it cannot substitute for selecting the procedure in the ext4 journal limits analysis.
D:The macOS Spotlight metadata alternative points to a different lead: indexed names and attributes can persist independently of a visible Finder directory; it does not settle selecting the procedure for ext4 journal limits. The macOS Spotlight metadata interpretation, search-index evidence supports file presence hypotheses with limited behavioral attribution, cannot replace ext4 journal limits evidence for selecting the procedure.
E:Although Linux shell-history attribution may matter in another case because a saved command list suggests commands entered in a shell profile, this question asks about selecting the procedure for ext4 journal limits. The separate Linux shell-history attribution consideration is that a shell history line is a lead, not independent proof of execution by a named person; it cannot substitute for selecting the procedure in the ext4 journal limits analysis.
Question 150
A case lead requests a targeted response. An Azure VM's resource settings were modified shortly before compromise was detected. Which approach is most relevant?
- Inspect subscription-level Azure Activity Log operations and caller context
- Assess authorized JTAG access using safe hardware procedures and device-specific documentation
- Review available Cloud Audit Logs and their enabled categories
- Create and verify an encrypted backup while preserving its password and manifest
Explanation
Correct Answer
A:For Azure Activity Log review, management events record resource control-plane changes and reported outcomes; Azure control-plane audit events complement VM disk and OS evidence. When selecting the procedure for Azure Activity Log review, the crucial limit is that the Activity Log does not replace guest OS security-event collection.
Incorrect Answers
B:Although JTAG hardware access may matter in another case because debug signals can expose some memory or processor state when access is not locked, this question asks about selecting the procedure for Azure Activity Log review. The separate JTAG hardware access consideration is that hardware debugging is device dependent and risks damaging fragile evidence; it cannot substitute for selecting the procedure in the Azure Activity Log review analysis.
C:In an inquiry concerning google Cloud Audit Logs, audit entries can show principal identities, services, resource names, and methods; that supports a different purpose than selecting the procedure for Azure Activity Log review. This google Cloud Audit Logs material may suggest that GCP audit streams support attribution of cloud API activity with configuration limits, but it does not establish the Azure Activity Log review finding needed for selecting the procedure.
D:The iOS encrypted backup evidence alternative points to a different lead: an encrypted backup can include categories of protected data excluded from some unencrypted backups; it does not settle selecting the procedure for Azure Activity Log review. The iOS encrypted backup evidence interpretation, logical backup acquisition has valuable coverage but is not complete flash capture, cannot replace Azure Activity Log review evidence for selecting the procedure.