What are the potential risks associated with relying heavily on code generated from GitHub Copilot? (Each correct answer presents part of the solution. Choose two.)

The correct answer is A. GitHub Copilot may introduce security vulnerabilities by suggesting code with known exploits. C. GitHub Copilot's suggestions may not always reflect best practices or the latest coding standards. Two genuine risks stand out: (A) Copilot is trained on public code, which includes code with known security flaws. It can reproduce vulnerable patterns such as SQL injection sinks, hardcoded credentials, or insecure cryptographic usage - developers must review suggestions…

Use GitHub Copilot responsibly

Question

Options

AGitHub Copilot may introduce security vulnerabilities by suggesting code with known exploits.
BGitHub Copilot may decrease developer velocity by requiring too much time in prompt
CGitHub Copilot's suggestions may not always reflect best practices or the latest coding standards.
DGitHub Copilot may increase development lead time by providing irrelevant suggestions.

How the community answered

(48 responses)

A
81% (39)
B
6% (3)
D
13% (6)

Explanation

Two genuine risks stand out: (A) Copilot is trained on public code, which includes code with known security flaws. It can reproduce vulnerable patterns such as SQL injection sinks, hardcoded credentials, or insecure cryptographic usage - developers must review suggestions carefully. (C) Copilot reflects the statistical distribution of its training data; popular-but-outdated patterns, deprecated APIs, or non-idiomatic code can surface as suggestions, meaning output may lag behind current best practices or language/framework standards. Options B and D are incorrect: Copilot is specifically designed to increase developer velocity and reduce lead time, not decrease them.

Topics

#Copilot risks#Security vulnerabilities#Code quality#Best practices

Community Discussion

No community discussion yet for this question.

Full GH-300 Practice