The correct option is State the style requirements directly in the Copilot Chat prompt so responses follow those rules.

Copilot Chat responds to explicit instructions in your prompt, so telling it which naming conventions, formatting rules, and examples to follow is the most direct way to shape its output. When you include clear style guidance at the beginning of the conversation and reinforce it as needed, the assistant will tailor its Python snippets to match those rules for the duration of the chat.

Add a lint step in Cloud Build and expect Copilot Chat to adopt the enforced style automatically is incorrect because linting and formatting in CI run after the code is generated. They improve code quality in the pipeline but they do not influence how the assistant composes suggestions during the conversation.

Use an .editorconfig file so Copilot Chat automatically conforms to editor formatting rules is incorrect because EditorConfig guides how your editor formats files and it does not reliably control how Copilot Chat structures or names code in its responses.

Place a .copilot-config file in the repository to apply style preferences to every chat is incorrect because Copilot Chat does not recognize such a file to enforce style rules across chats. The supported and reliable approach is to state the requirements in the prompt.

Full AWS Practitioner Certification Question