Alerting & monitoring for SY0-701

Exam objectiveExplain security alerting and monitoring concepts and tools

The short answer

What objective 4.4 asks you to know

Objective 4.4 covers security alerting and monitoring: what you monitor, what you do with the data, and the tools that provide it.

What and how you monitor. Monitoring collects data from systems, applications, and infrastructure, turns it into alerts people can act on, and keeps the records for later reporting and investigation. The listed activities are log aggregation, alerting, scanning, reporting, archiving, and alert response and remediation or validation, including quarantine and alert tuning. Aggregation gathers logs into a shared store, while correlation links events across sources to reveal a pattern. Quarantine isolates a suspect item quickly, and tuning refines a noisy rule instead of turning detection off.

Central tools. A security information and event management (SIEM) system centralizes, normalizes, and correlates security events and alerts on them. The Security Content Automation Protocol (SCAP) is the automation standard that lets tools exchange and evaluate data in standard formats, and benchmarks, such as CIS Benchmarks, state the recommended settings that SCAP-based checks evaluate.

Data sources. Agents report from installed software on hosts, while agentless collection gathers data remotely. SNMP traps let a device announce an event without waiting for a poll. NetFlow describes traffic as flow metadata rather than full packet content. Antivirus catches malware on endpoints, data loss prevention (DLP) watches for sensitive data leaving, and vulnerability scanners find weaknesses on a schedule.

Exam questions give a symptom and ask which tool or activity fits: correlation points to a SIEM, flow metadata to NetFlow, and standardized configuration checks to SCAP and benchmarks.

Written by Knotch · reviewed Nov 15, 2026 · 3 study articles behind this page

Practice the rest

This page is the map. Knotch is where you drill it until it sticks.

  • 3step-by-step lessons with predict-and-reveal and look-alike duels
  • 46exam-style questions with a rationale for every wrong answer
  • 1review queue that brings back what you missed
Start practicing freeFree to start. No card needed.
Tell them apart

Pairs people mix up

  • Aggregation vs. Correlation

    Aggregation decides where the records end up and in what form. Correlation links clues from several tools into one finding an analyst can act on.

  • SIEM vs. SOAR

    A SIEM gathers events and tells analysts what it found. A SOAR tool runs the response steps that follow across other tools, pausing only where a person must approve.

  • SNMP polling vs. SNMP trap

    With polling, the manager asks the device on a schedule. With a trap, the device sends an unsolicited message when something happens.

  • SCAP vs. Benchmark

    SCAP is the automation standard for exchanging and evaluating data. A benchmark, such as a CIS Benchmark or DISA STIG, is the configuration content that states the recommended settings.

The full set of look-alike pairs for this objective is inside Knotch.

Know these cold

Key terms

SIEM
Security information and event management: a system that centralizes, normalizes, and correlates security events from many sources and alerts analysts.
SCAP
The Security Content Automation Protocol, a standard that lets tools exchange and evaluate configuration and vulnerability data in standard formats such as XCCDF and OVAL.
SNMP trap
An unsolicited message a network device sends to the monitoring system when an event happens, instead of waiting to be polled.
NetFlow
A source of flow metadata that summarizes traffic between hosts, without the full packet content a packet capture holds.
Alert tuning
Refining a detection rule to cut false alarms, as opposed to disabling it, which removes the detection.
Log aggregation
Pulling scattered logs into a shared store in a shared layout so they can be searched and correlated.
Try one

Sample question

Question 4.4-015 · medium

A switch needs to tell the monitoring system immediately when an interface goes down, without waiting for the next scheduled poll.

Which mechanism does this describe?

  1. A. An SNMP poll
  2. B. A NetFlow record
  3. C. A scheduled vulnerability scan
  4. D. An SNMP trap
Show the answer and why
Answer: D, An SNMP trap

A trap is an unsolicited message a device sends when an event happens.

SNMP polling is the manager asking on a schedule, whereas a trap is the device announcing an event.

Why not A: Polling is the manager asking on a schedule, which is the opposite of the device announcing the event.

Why not B: A flow record summarizes traffic between hosts and does not announce interface failures.

Why not C: A scan runs on a timetable to find weaknesses and does not report device events.

Quick answers

Common questions on this objective

What is the difference between a SIEM and a log server?

A log server stores logs. A SIEM also normalizes, correlates, and alerts on them.

What is the difference between NetFlow and packet capture?

NetFlow records flow metadata about traffic between hosts. Packet capture records full packet content.

What is the difference between agent-based and agentless monitoring?

Agent-based monitoring uses software installed on the host, which collects locally and reports whenever it can reach its collector, even off the corporate network. Agentless monitoring collects data remotely, which suits devices that cannot run installed software.

Know it. Now spot it in a scenario.

Start practicing free