The correct option is Directing GitHub Copilot to adopt a specific professional persona within the prompt to shape its output.

Assigning a role like cloud security analyst guides the model to prioritize risk identification, secure defaults, and compliance minded reasoning when reviewing Terraform. This approach narrows the context and criteria that Copilot uses so the suggestions and explanations align with the requested expertise.

This technique is a core prompt engineering pattern because role or persona instructions influence both the depth and the focus of the analysis. It helps the model surface security relevant checks and provide justifications that match how a specialist would review infrastructure as code.

Instructing GitHub Copilot to use a friendly or formal tone in its replies is incorrect because tone only changes style and voice. It does not provide the domain specific perspective needed for security focused Terraform reviews.

Asking GitHub Copilot to explain the purpose of a suggested change in the code is incorrect because explanation improves clarity but it does not direct the model to use cloud security analyst criteria when forming suggestions.

Configuring IAM roles in Google Cloud to limit user permissions before prompting is incorrect because access controls in the cloud environment do not shape how Copilot generates code review suggestions within the editor.

Full AWS Practitioner Certification Question