Balancing AI Automation in Vulnerability Management Flow
Short answer
A Use AI to triage discovered issues and create tickets while a software engineer merges the software fixes.
Question
Key Takeaways
It tests where AI automation should stop in a vulnerability management workflow, with the trap being that faster is not always more balanced when the merge step changes production code.
This CY0-001 scenario asks how a large social media company can reduce mean time to fix with AI, and the balanced answer is option A: AI handles triage and ticket creation while a software engineer merges the fixes.
Common mistake: Option D is tempting because end-to-end automation looks fastest, but letting AI merge software fixes removes human accountability for shipped code and is not the balanced strategy.
Expert Analysis
The governing principle
The decision rests on CompTIA's guidance for AI-assisted security operations (domain AI-assisted Security): AI should take over high-volume, pattern-based, repeatable work, while irreversible or consequence-bearing actions stay under human accountability. Automation should compress effort without removing human judgment where the blast radius is largest.
Mapping the scenario
This company's goal is a lower mean time to fix across a million-plus-line codebase, so the bottleneck is the repetitive front end of the flow: sorting triaged vulnerabilities, ranking them, and opening and routing tickets. That is precisely the work option A assigns to AI — it triages discovered issues and creates tickets, producing a steady, consistent queue far faster than manual sorting. The closing step, merging software fixes into the codebase, changes production code and can itself introduce defects, so option A keeps that merge with a software engineer, preserving human review and accountability for what ships.
Why the other options fail the balance test
Option B inverts the balance: it spends scarce analyst time on the routine sorting work while handing the highest-risk action — merging code — to AI, which raises the risk profile the exam is testing (see objective 4.2, risks associated with AI). Option C is the fully manual baseline; it is safe but delivers no automation, so it does not meet the stated goal of reducing MTTR. Option D is full automation end to end; it maximizes speed but eliminates human oversight at the merge, which is exactly the trade-off the word "balanced" in the question is signaling.
Verdict
Option A is the correct answer: it automates the repetitive triage-and-ticketing work with AI and reserves the code merge for a software engineer, balancing speed with control.
Exam Strategy
When a question asks for the most "balanced" or "appropriate" AI strategy, rank the listed actions by risk: read-only, repetitive analysis work (triage, ticketing) is safe to automate, while irreversible actions that change production (merging code, deploying, deleting data) should stay human. Eliminate any option that automates the highest-risk action first, then eliminate options with no automation at all when a speed or efficiency goal is stated. This risk-tiering technique transfers directly to other AI-assisted security automation questions.
Frequently Asked Questions
Why is it safer for AI to triage vulnerabilities than to merge code fixes?
How does automating triage reduce mean time to fix (MTTR)?
Why is full end-to-end automation (option D) not the balanced answer?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
TonytheTiger 👍 1 Answered AAnswer A: provides the best balance between AI automation and human oversight in the vulnerability management process.
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.