The correct option is Install and enable the GitHub Copilot extension in a supported IDE such as Visual Studio Code or a JetBrains IDE and start coding.

This is correct because Copilot delivers suggestions inside your editor once the extension or plugin is installed and you are signed in with your GitHub account. After you enable it in the IDE, Copilot provides real time code completions and suggestions as you type without any repository level configuration.

Create a GitHub Actions workflow that provisions Copilot for each repository is incorrect because Actions workflows do not provision Copilot and there is nothing to automate per repository for editor suggestions.

Toggle a setting in the repository to enable Copilot on that repo is incorrect because Copilot access comes from your account subscription or organizational seat assignment and editor suggestions are not controlled by a per repository switch.

Wait for Copilot to automatically add suggestions to issues and pull requests is incorrect because Copilot suggestions appear while you code in the IDE and it does not automatically post content to issues or pull requests for a personal subscription.

Full AWS Practitioner Certification Question