What is the purpose of code scanning alerts triage, and what steps are typical?

• A. To adjust code formatting.
• B. To prioritize and assign alerts for remediation; steps include verifying, reproducing, assigning, remediating, and closing.
• C. To generate new dependencies automatically.
• D. To remove deprecated code without review.

Answer: (B)

Code scanning alerts triage is about turning noisy findings into a manageable workflow by prioritizing, assigning, and validating issues so they can be remediated efficiently. The typical steps include verifying the alert to rule out false positives, reproducing or confirming the issue in the code, assigning it to the right developer or team, implementing or guiding remediation, and then closing the alert once the fix is in place and verified. This process helps focus attention on the most impactful issues and tracks progress from discovery to resolution. The other options don’t fit because adjusting code formatting, automatically generating dependencies, or removing deprecated code without review are separate activities and not what triage is designed to do.