Which log shows which device had an IP address?
DHCP lease logs map an IP address to a device.

Exam objectiveGiven a scenario, use data sources to support an investigation
Objective 4.9 covers where investigators find evidence and which data source answers which question.
Log data. Firewall logs record connection decisions: addresses, ports, protocol, and whether the connection was allowed or denied. IDS/IPS logs record attack alerts: the signature or anomaly, the traffic involved, and the action taken. Application logs record what a program saw, such as errors and input that triggered failures, while OS-specific security logs, such as the Windows Security log, record logon successes and failures, privilege use, and account changes. Endpoint logs show what happened on a specific host: process launches, file activity, malware detections, and EDR telemetry. Network logs include DNS queries, proxy and web filter records, DHCP leases that map an IP address to a device, VPN sessions, and flow data. Metadata describes a file or message rather than its contents.
Other data sources. Vulnerability scan results show which known weaknesses were present. Automated reports give periodic summaries with consistent snapshots and trends, while dashboards give a live visual overview that shows spikes quickly but only what was built into them. A full packet capture can hold whole packets, including payload that is readable when the traffic is not encrypted, unlike NetFlow, which holds summary metadata.
Exam scenarios describe a question the investigator must answer and ask which data source answers it: connection decisions come from firewall logs, device-to-IP mapping from DHCP, payload from packet captures, and file timelines from metadata.
This page is the map. Knotch is where you drill it until it sticks.
Firewall logs record connection decisions. IDS/IPS logs record attack alerts: the signature or anomaly, the traffic involved, and the action taken.
A full capture holds whole packets, including payload. NetFlow holds summary metadata.
A dashboard is a live visual overview that shows spikes quickly but only what was built into it. An automated report is a periodic summary that gives consistent snapshots and trends but may hide detail.
An application log records events inside one program, such as its errors and the input it rejected. An OS log records system-level events, such as logons, privilege use, and service changes.
The full set of look-alike pairs for this objective is inside Knotch.
A web application shows signs of SQL injection attempts. The network firewall only shows allowed HTTPS connections to the server, which reveals nothing about what was submitted.
Which log source is MOST likely to reveal the submitted input and resulting errors?
Application logs record logins, errors, transactions, and input that triggered failures.
Application logs record what the software received and how it responded, so they reveal injection attempts and misuse. Firewall and other connection logs record who connected, not what was submitted; application-aware tools such as a WAF may add some request detail.
Why not B: DHCP logs map addresses to devices and do not describe application activity.
Why not C: Firewall logs record connection decisions and not the content of the web requests.
Why not D: VPN logs show who connected remotely and from where, not what an application recorded.
DHCP lease logs map an IP address to a device.
Basic firewall logs record connection decisions, not the content of web requests. Application logs from the web server and database reveal the submitted input and resulting errors.
Metadata is details about a file or message, such as creation time, modification time, and author. Content is what the file or message actually contains.
