SY0-701 domain - 28% of the exam

Security Operations

Security Operations is 28% of the SY0-701 exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

92
Practice questions
9
Objectives
9
Easy
50
Medium
33
Hard

Where people go wrong

  • Assigning an incident response activity to the wrong phase

    The wrong answers move an activity into a neighbouring phase. Isolating systems to bound an active incident is containment, and removing malware, backdoors and persistence is eradication, so swapping their descriptions or order fails. Restoring services from clean backups is recovery. Confirming an intrusion belongs to detection and analysis, while preparation is the standing readiness built before any incident. Root cause analysis asks why the weakness existed, and reimaging a host first destroys evidence and leaves stolen credentials in use.

    See it in a sample question
  • Choosing a data source that cannot hold the evidence

    Each investigative question needs a source that records the answer, and the wrong answers pick one that does not. Firewall flow records hold addresses, ports and byte counts but discard payload, so they cannot yield the TLS client hello. Message headers carry the Received hops and SPF and DKIM verdicts that the rendered body and attachment hashes lack. A vulnerability scan names the missing patch and CVE, which access logs cannot. Document and audit metadata records readers, timestamps and authors that packet captures never expose.

    See it in a sample question
  • Ranking remediation by CVSS base score alone

    The wrong answers treat the base score as the whole priority. The base metrics describe intrinsic, static characteristics of the flaw. They leave out exploit maturity, which the temporal group captures, and asset exposure and data sensitivity, which the environmental group captures. A publicly exploited flaw on an internet-facing portal holding identity documents needs immediate action, and an exposed host with sensitive data outranks an identical flaw on an isolated low-value system. Age does not lower urgency, and the scan method has no bearing on how urgent a finding is.

    See it in a sample question
  • Giving one monitoring tool another's role

    The wrong answers hand a tool the job of its neighbour. A SIEM centralises, normalises and correlates logs across sources, which an intrusion detection sensor, a vulnerability scanner or SNMP polling cannot do. A scanner finds where weaknesses live, while a SIEM shows what is happening now. SOAR orchestrates playbooks across existing tools and leaves the SIEM as the log store. Full packet capture belongs to a network forensics recorder and process quarantine to endpoint detection and response, and a SIEM only consumes their telemetry.

    See it in a sample question
  • Crediting MFA, SSO or RBAC with privileged access control

    The wrong answers offer a general identity control where the scenario needs privileged access management. Federated sign-on, multi-factor authentication and role-based group membership improve authentication or entitlement, yet each leaves standing administrator rights in place and records no session. PAM vaults credentials, issues just-in-time elevation, brokers and records sessions, and rotates service account secrets. It augments MFA rather than replacing it, and joiner, mover and leaver provisioning belongs to identity governance and administration.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleSecurity Operationsmedium

Which statement most accurately distinguishes the containment phase from the eradication phase of the incident response process?

  • AContainment removes the adversary's tools and persistence from affected systems, while eradication isolates those systems from the network to stop further damage.
  • BContainment and eradication are interchangeable terms for the same stage in which responders restore affected services back to normal business operation.
  • CContainment is performed only after eradication has finished, so that responders can verify the network is safe before they begin isolating any affected hosts.
  • DContainment limits the scope and impact of the incident while it is still active, whereas eradication removes the attacker's foothold, malware, and other artefacts from affected systems. Correct
Distinguish containment, which limits incident impact, from eradication, which removes the attacker's tools and persistence from affected systems. Standard incident response process descriptions, including those summarised in the SY0-701 Security Operations objective, treat containment as the phase that bounds active damage through isolation and access changes, and eradication as the subsequent phase that removes malware, backdoors, malicious accounts, and other persistence so the environment can be safely recovered.

Why A is wrong: This is tempting because both phases sound like cleanup work, but the descriptions are swapped: isolating systems to stop further damage is containment, and removing tools and persistence is eradication.

Why B is wrong: This option is tempting because the two terms are often discussed together, but they are distinct phases, and restoring services to normal operation is the recovery phase rather than either of them.

Why C is wrong: This reverses the documented order: incident response frameworks place containment before eradication so that an active threat is bounded before responders attempt to remove the attacker's tooling and persistence.

Why D is correct: Containment focuses on bounding the blast radius by isolating hosts, blocking accounts, or filtering traffic; eradication then removes malware, backdoors, malicious accounts, and other persistence so the environment is clean before recovery.

Free sampleSecurity Operationsmedium

An incident responder at a logistics company is reviewing a phishing email that was reported by three drivers shortly after delivery. The body and headers have already been preserved, and the analyst now wants to determine which intermediate mail servers handled the message, whether the sending domain's SPF and DKIM checks passed at the receiving gateway, and the exact UTC time the message was accepted by the corporate mail relay. Which element of the preserved evidence should the analyst examine to answer all three questions?

  • AThe rendered HTML body of the phishing message as it appeared in the driver's mail client.
  • BThe list of any URLs extracted from the body and submitted to the threat intelligence platform for reputation lookup.
  • CThe full message headers, including each Received line and the Authentication-Results header added by the receiving gateway. Correct
  • DThe attachment hashes calculated from any files carried by the message and compared against the antivirus signature database.
Recall that mail message metadata in the full headers, especially Received and Authentication-Results, is the primary data source for routing, authentication, and timing in a phishing investigation. Internet mail records its routing as a stack of Received headers prepended by each relay it traverses, and modern gateways add an Authentication-Results header that captures SPF, DKIM, and DMARC verdicts. Because all three pieces of information are written into the header block as the message travels, examining the full headers answers routing, authentication, and acceptance-time questions from a single preserved artefact.

Why A is wrong: The rendered body shows what the recipient saw but it does not contain routing hops, authentication verdicts, or acceptance timestamps, so it cannot answer any of the three questions the analyst is asking.

Why B is wrong: URL reputation data describes the destinations of links inside the message but it says nothing about the mail relays that handled the message or the SPF and DKIM verdicts at the receiving gateway.

Why C is correct: Each Received line records one intermediate hop with its timestamp, and the Authentication-Results header recorded by the gateway carries the SPF and DKIM verdicts, so the headers answer routing, authentication, and acceptance-time questions in one place.

Why D is wrong: Attachment hashes help classify payloads but they do not reveal routing hops, authentication results, or the time the message was accepted by the corporate relay, so they cannot answer the analyst's three specific questions.

Free sampleSecurity Operationsmedium

A regional council's security analyst is reviewing a fresh finding for a publicly reachable customer portal. The advisory reports CVSS base metrics of attack vector network, attack complexity low, privileges required none, user interaction none, scope unchanged, and high confidentiality, integrity and availability impact. A reliable public exploit script is already circulating online, and the affected portal stores residents' identity documents. Which interpretation of the CVSS score most accurately drives the team's prioritisation decision?

  • ABecause the base metrics already include exploit availability and the value of the affected data, the base score alone is sufficient to schedule the finding into the next standard monthly patch cycle.
  • BThe CVSS score should be downgraded internally because the portal sits behind a content delivery network, since any control in front of the asset removes the relevance of the network attack vector metric.
  • CThe base score reflects only the intrinsic characteristics of the flaw, and the team should additionally consider the public exploit and the sensitivity of the residents' data through the temporal and environmental dimensions before settling the priority. Correct
  • DThe finding should be deferred until the next quarterly assessment because CVSS scores are advisory only and have no role in driving operational remediation timelines under standard vulnerability management practice.
Use CVSS base, temporal and environmental dimensions together so that exploit availability and asset context shape the final remediation priority. CVSS base metrics describe the intrinsic properties of a vulnerability, while temporal metrics reflect changing factors such as exploit code maturity and environmental metrics reflect the specific deployment and data sensitivity, and combining all three produces a context-aware priority that the base score alone cannot.

Why A is wrong: It is tempting to assume the base score captures everything, but the base metrics deliberately exclude exploit maturity and the specific business context of the affected asset, so relying on the base number alone would underweight a publicly exploited issue on a portal holding identity documents.

Why B is wrong: It feels reasonable to credit perimeter controls, but a content delivery network does not change the underlying network reachability or the flaw itself, and downgrading the score for that reason masks a genuinely exposed vulnerability behind an arbitrary adjustment.

Why C is correct: Treating the base score as the intrinsic measure and then layering temporal context such as available exploit code and environmental context such as data sensitivity is precisely how CVSS is designed to be used, and it gives the analyst a defensible reason to prioritise this finding for immediate action.

Why D is wrong: Calling CVSS advisory only sounds cautious, but recognised guidance treats CVSS as a primary input to remediation timelines, and ignoring a high-impact, publicly exploited finding on an internet-facing portal would conflict with normal vulnerability management expectations.

Free sampleSecurity Operationsmedium

Which statement most accurately describes the defining role of a security information and event management platform within a security operations programme?

  • AIt replaces endpoint detection agents by inspecting host memory directly and quarantining suspicious processes without forwarding telemetry to any central collector.
  • BIt is a packet capture appliance that stores full network traffic for months and reconstructs application sessions on demand for forensic analysts.
  • CIt centralises log and event data from many sources, normalises and correlates that data, and produces alerts and dashboards that analysts can investigate and report on. Correct
  • DIt is a vulnerability scanner that authenticates to hosts, enumerates missing patches, and produces remediation tickets for the patch management team.
Recognise that a SIEM aggregates, normalises, and correlates log data from many sources to produce alerts, dashboards, and reports. A security information and event management platform sits downstream of producers such as firewalls, endpoints, identity providers, and applications. It parses each source into a common schema, applies correlation rules across events, retains data for search and reporting, and raises alerts when patterns match. That aggregation and correlation is what distinguishes it from point tools such as EDR, packet capture, or vulnerability scanners.

Why A is wrong: This conflates a SIEM with endpoint detection and response. A SIEM does not run on endpoints and does not perform in-memory inspection or quarantining; it consumes telemetry produced by other tools rather than acting on hosts itself.

Why B is wrong: Full packet capture is the job of a network forensics or full-flow recorder, not a SIEM. A SIEM ingests metadata and log records rather than storing raw packets for session reconstruction.

Why C is correct: This captures the SIEM's defining role: aggregation, normalisation, correlation, alerting, and reporting across heterogeneous sources, which is how it supports detection and investigation in a SOC.

Why D is wrong: Vulnerability scanning is a separate tool category. A SIEM may ingest scanner output as one source, but its purpose is event correlation and alerting, not credentialed enumeration of missing patches.

Free sampleSecurity Operationshard

A platform engineering team is rolling out privileged access management for around two hundred Linux servers that host customer workloads. The security manager has set three outcomes for the rollout: standing administrator credentials must be eliminated, every interactive root session must be tied to a named human and recorded, and shared service accounts that scripts use for backups must rotate their secrets automatically without humans handling them. Which design most directly delivers all three outcomes for these servers?

  • ALocal root passwords that are stored in an encrypted spreadsheet shared with the on-call team, with quarterly password rotation and an honour-system rule that admins record what they did in a wiki page after each session.
  • BDisable interactive root logins entirely and require every administrator to elevate using sudo after logging in with their normal account, with sudo configured to log to syslog locally on each host.
  • CSingle sign-on for the Linux fleet through the corporate identity provider, with administrators kept in a permanent admin group and service accounts using static secrets distributed by configuration management.
  • DA PAM solution that brokers SSH sessions through a jump host, issues short-lived just-in-time credentials per request after multi-factor authentication, records the session, and stores service account secrets in a vault that rotates and injects them into automated jobs. Correct
Identify a brokered PAM design with just-in-time elevation, session recording, and vault-rotated service secrets as the control set that removes standing privilege. Modern privileged access management combines a brokered access path that authenticates the human, issues a short-lived credential or certificate after policy and MFA checks, records the resulting session for forensic and audit purposes, and stores non-interactive secrets such as service account passwords in a vault that rotates them and injects them into pipelines on demand. Together these eliminate standing administrator credentials and the unattributed shared accounts that drive most privileged access incidents.

Why A is wrong: Shared passwords in a spreadsheet keep standing credentials in human hands, break attribution because anyone in the on-call group could be the user, and rely on self-reporting rather than recorded sessions, so all three required outcomes fail.

Why B is wrong: Sudo with personal accounts is a sensible baseline and improves attribution, but it leaves persistent administrative entitlements in place, does not record full session content, and does nothing for shared service account credentials used by automated backups.

Why C is wrong: Federated SSO improves authentication but a permanent admin group preserves standing privilege, and static secrets pushed by configuration management do not rotate themselves, so neither elimination of standing credentials nor automatic rotation is achieved.

Why D is correct: This design removes standing credentials by issuing them just in time, ties each interactive session to the requesting human through the broker, records the session for accountability, and uses vault-managed secrets so backup jobs receive freshly rotated credentials without any human seeing them.

Other domains in this exam

See also the SY0-701 cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by CompTIA. Original, blueprint-aligned practice material only.