The correct option is Copilot can surface notices about insecure patterns in generated code and it still allows the user to accept the suggestion.

In both VS Code and JetBrains IDEs, Copilot includes security vulnerability filtering that highlights potentially risky patterns found in a suggestion. The editor can display an icon or message that explains the concern and may hint at safer alternatives. These warnings are advisory and the developer can still accept the completion or revise it based on the context.

Security prompts in Copilot are always enabled and users cannot disable them in the editor settings is incorrect because Copilot behavior in the editor is configurable and users can manage Copilot features and prompts through IDE settings.

Copilot natively connects to Google Cloud Security Command Center to raise inline vulnerability alerts as you type in the IDE is incorrect because Copilot does not integrate with Google Cloud Security Command Center for inline alerts. GitHub provides its own security tooling such as code scanning which is separate from Copilot’s in-IDE suggestions.

Copilot has built in scanning that blocks any suggestion with a possible vulnerability before it appears is incorrect because Copilot does not block suggestions on detection of risky patterns. It flags them so the developer can review and decide whether to accept or modify the code.

Full AWS Practitioner Certification Question