ITForMe Beta Sign in
SEC+ SY0-701 V7 Security operations Runs in your browser · no setup Original practice · Review pending

Drive a vulnerability remediation sprint

Prioritize risk with business context, choose defensible treatments, and prove remediation worked.

Estimated15 min
DifficultyAdvanced
Points12
Scenario brief

Northwind Print Cooperative has one four-hour maintenance window and cannot complete every open finding. Use the technical records, reachable attack paths, operational constraints, and vendor evidence to create a defensible plan.

Content record

Original practice · Review pending

Mapped to CompTIA SY0-701 objectives · Internal validation 2026-09-15 · Original ITForMe practice mapped to published objectives; not an official exam question. A named independent subject-matter expert has not yet verified the question and answer key.

Community review →
4.3Explain various activities associated with vulnerability management.
Show review record and official sources

Method: Mapped to SY0-701 vulnerability-management objective 4.3; raw scanner, exposure, threat, and vendor evidence plus prioritization, exception, and validation logic were rechecked after difficulty-calibration feedback.

Current-profile check: 2026-08-12 · Next review due 2026-11-16

01

Inspect the evidence

Use only the information provided to complete the tasks.

Scanner export with asset and threat telemetry

table
AssetScanner resultReachability / telemetryVendor and operations record
VPN-01CVE-2026-4811; CVSS 9.8; appliance build 12.4.6Public TCP 443; WAF logs show exploit-pattern requests from 14 sources; no matching IPS rule deployedBuild 12.4.9 fixes CVE-2026-4811; update is supported and VPN-02 can carry sessions during restart
PRINT-04CVE-2025-7710; CVSS 9.8; firmware 4.2.1Printer VLAN accepts management only from PRINT-MGR; no exploit indicators in retained logsVendor firmware 4.3 scheduled next quarter; vendor has no supported interim package
CAD-17CVE-2026-1902; CVSS 8.4; local privilege escalation in OS componentRestricted engineering subnet; assigned operator uses a standard account; EDR has no matching process behaviorSupported OS update passed the engineering pilot and needs one reboot
ARCHIVE-02CVE-2024-6120 matched upstream library version 1.4.2Internal archival service; no vulnerable endpoint exposed outside the service tierInstalled package 1.4.2-18.nw4; distribution advisory NW-2024-88 states the fix was backported in 1.4.2-15.nw4

If columns are offscreen, scroll sideways or focus the table and use arrow keys.

Change and governance record

list
  • ›VPN-01 has a configuration export restored successfully to a lab appliance two weeks ago.
  • ›Security engineering can rescan changed assets and review WAF, EDR, and service logs during the window.
  • ›The exception form cannot be approved without a named risk owner, review-by date, planned treatment, and current compensating-control evidence.
  • ›Unsupported firmware and untested packages are prohibited on production print devices.
02

Complete the response

Partial credit is available for matching, ordering, and multi-select tasks.

Changes will save automatically.
01
single choice

Which asset should receive the first change-window slot?

3 pts
Need a hint?

Restate the exact outcome or failure the prompt asks about before comparing choices.

Show another hint

Eliminate choices that solve a nearby problem, change more than requested, or do not fit the evidence.

02
matching

Match each finding to the most defensible immediate treatment.

4 pts
Need a hint?

Start with the row and choice that have the most distinctive purpose, then use that pair to narrow the rest.

Show another hint

For each remaining pair, explain the relationship in one sentence before selecting it.

03
ordering

Order the VPN-01 remediation workflow.

5 pts

Drag the rows or use the arrow buttons to reorder.

  1. 1 Confirm the finding, affected version, exposure, and vendor fix
  2. 2 Approve the change, backup, failover, test, and rollback plan
  3. 3 Fail over traffic and install the supported security update
  4. 4 Test remote access, confirm the running build, rescan, and review logs
  5. 5 Attach evidence, document residual risk, and close or reassign the finding
Need a hint?

Identify the prerequisite that must happen first and the verification or documentation that belongs last.

Show another hint

For the middle steps, ask what must already be true before each action can safely happen.

Ready to check your work?Unanswered tasks and matches earn no points. A partial submission is scored and saved in your history.
Persistent progress

Attempt history

Every submission is retained. Starting another attempt never replaces or unlocks the previous one.

No attempts yet

Your first submitted score and detailed answer review will appear here.

Community quality control

Question or answer look wrong?

Proposals and votes help staff prioritize review. They never change the scoring key automatically.

Full review queue →
No community corrections yet

Be the first to flag unclear wording, an answer-key issue, or a source that needs another look.

Propose a correction