How can you differentiate Code Scanning alerts from Secret Scanning alerts in the UI?

• A. They originate from the same scanning process and are shown under the same section.
• B. Code Scanning alerts originate from CodeQL queries; Secret Scanning alerts come from secret detection in code or history; they appear under different sections in Security.
• C. They are both shown under the 'Code Scanning' tab only.
• D. Secret Scanning alerts never appear in the UI.

Answer: (B)

Code scanning and secret scanning come from different scanning processes and are surfaced in separate parts of the Security UI. Code scanning alerts come from CodeQL analysis runs, while secret scanning alerts come from detecting secrets in code or in history. Because they originate from distinct checks, GitHub places them in different sections under Security—code scanning alerts in the Code scanning area and secret scanning alerts in the Secrets/Secret scanning area. This separation helps you triage by type and know which tool flagged the issue. The other options imply they share the same section, or that secret alerts never appear, which isn’t accurate.