Which statement about CodeQL scope is accurate?

• A. Changing the scope has no effect on results.
• B. Wider scope reduces the chance of detecting issues.
• C. Narrowing the scope only affects performance, not results.
• D. Narrowing or widening the scope changes which languages and paths are analyzed, affecting coverage.

Answer: (D)

CodeQL scope defines what is analyzed: which languages are included and which files or paths are part of the analysis. When you narrow or widen that scope, you’re changing the set of code that the queries run against. Widening the scope includes more languages and directories, so CodeQL examines more of the codebase and can detect issues in areas that were previously ignored. Narrowing the scope removes parts of the code from analysis, which can cause some issues to be missed but can improve performance and focus. Because scope directly determines which languages and paths are analyzed, it automatically affects coverage and the results you get. The other statements don’t hold up: scope changes do affect results; broader scope does not inherently reduce detection; narrowing can affect results beyond performance since it limits what is analyzed.