Free Microsoft GH-300 Practice Exam with Questions & Answers | Set: 2

For GitHub Copilot Business and Enterprise, prompts and suggestions are retained for 28 days to provide context and improve the service. User engagement data, which includes usage patterns and interactions, is kept for two years. This data retention policy is designed to balance service improvement with user privacy.

“While Copilot can suggest refactoring changes, the code may not always follow best practices or be fully optimized. Developers must review and validate suggestions.”

This confirms that limitations exist in optimization and best practices, making option A correct.

“By default, suggestions matching public code are allowed, but you can choose to block public code matches. This setting can be enabled to reduce the risk of intellectual property infringement.”

This shows that enabling “Blocking public code matches” is the configuration required to protect against IP issues.

GitHub Copilot Enterprise assists in code reviews by generating summaries of pull requests and answering questions about the changes made.

“GitHub Copilot may sometimes suggest deprecated code, APIs, or patterns if these appear in its training data. Users are responsible for reviewing and updating the suggestions.”

This confirms that Copilot does not automatically update or reject deprecated features, but may still suggest them if they were part of training.

“Copilot Enterprise provides inline code suggestions and Copilot Chat in all commercially supported IDEs. Additional features, such as pull request summaries and knowledge bases, are available in GitHub.com.”

This confirms that inline suggestions and Chat are the features consistently available in IDEs.

GitHub Copilot primarily impacts the software development process by increasing productivity through automating repetitive coding tasks.

GitHub Copilot Chat combines its training data, code from user repositories, and external sources like Bing to generate comprehensive and relevant responses to coding questions.

Role prompting involves explicitly stating your role or the persona you want GitHub Copilot to adopt within your prompt. This helps Copilot provide more contextually relevant and accurate suggestions. By defining your role (e.g., " As a senior software engineer, " " As a technical writer " ), you guide Copilot to tailor its responses to align with the expertise and perspective associated with that role. This improves the quality and relevance of the generated code and explanations.